Start with a task that has a reviewable output
Select a bounded activity such as organising approved meeting notes, drafting a status summary from verified inputs or suggesting questions for a requirements review. Define the expected output and how a person will check it.
A broad request to “manage the project” leaves unclear which decisions the system may influence or which actions it may take. Start with a workflow whose boundary is explicit: prepare a draft, retain its source references and send it to the responsible reviewer.
Choose the task based on a recurring need. Establish how the team currently performs it so the pilot can be evaluated against an actual baseline rather than enthusiasm for the tool.
Agree what information the workflow may use
Confirm that the tool and its configuration are approved for the information involved. Project material can contain customer details, commercial discussions and confidential delivery plans. Ask the responsible organisational owners to establish the permitted inputs and access boundaries.
Use only the information needed for the task. If representative examples can support the initial evaluation, they provide a way to examine the workflow before introducing sensitive live material. Keep access and retention decisions with the roles authorised to make them.
Make the source set visible to the reviewer. A summary based on one meeting should not be presented as a complete view of the project.
Verify claims against their source
Generative AI can produce plausible but incorrect statements. NIST’s Generative AI Profile discusses this risk as confabulation. That makes source verification particularly relevant when generated text contains commitments, decisions or dates.
Require the reviewer to check whether each action was actually agreed, whether its owner is correct and whether a proposed date has been mistaken for a confirmed deadline. Keep unresolved questions visible in the draft.
The tool drafts a decision log from approved notes. The project manager checks each proposed decision against those notes, confirms ambiguous ownership with the participants and publishes the reviewed record. The draft does not assign work or notify stakeholders automatically.
Evaluate the workflow including the review effort
Compare the time and effort required to prepare, review and correct the output. A fast first draft may still create substantial verification work. Record the types of error that matter to the task, such as omitted caveats, inaccurate owners or unsupported commitments.
Use varied examples, including incomplete notes and conflicting inputs. Decide in advance which failures require the team to pause or narrow the workflow. A pilot that works only on unusually clean material has not yet demonstrated suitability for everyday use.
- Usefulness: does the output help complete the intended task?
- Accuracy: can material claims be verified?
- Effort: what preparation and correction are required?
- Ownership: who approves the result and handles errors?
Expand through explicit decisions
Document the workflow, its limits and the evidence from the pilot before broadening its use. Assign an owner to review changes in the tool, the source material and the way people rely on its output.
Automation that publishes, changes records or triggers actions needs its own assessment of authority, review and recovery. Success with drafting does not establish that those additional actions should be automated.
Use the change-control approach to make each expansion reviewable. Adoption becomes accountable when the team can explain what the workflow does, how it is checked and who remains responsible for the decisions it informs.