Implementation guide / 5 minute read
Start with a result someone can check.
The most useful first workflow is often a familiar piece of work with a clear owner, an observable result and enough repetition to learn from.
1. Name the work in an ordinary sentence.
“Explain why completed orders are not ready to bill” is a workable starting point. “Use AI across operations” leaves the sources, outcome and review undefined. Write down the question or responsibility in language the team already uses.
2. Find the person who knows a good result.
Choose a reviewer who does the work today. Ask what they check, what exceptions matter and what would cause them to reject an answer. Their review becomes the first acceptance test.
3. List the minimum sources.
For a billing question, that might be a completed delivery, the relevant office note and linked invoice records. Identify who can authorize access and how to recognize a missing or stale record. More data is not automatically more useful context.
4. Write down the boundary.
An explanation, a prepared message and an external action have different consequences. Decide which result the first scope needs. Identify what must remain awaiting review and what to do when the information is incomplete.
5. Compare a first result with the existing process.
Use familiar examples, including an awkward exception. Keep a short record of mismatches: wrong source, missing record, misunderstood definition or an unclear output. Fix the cause before expanding the scope.
A small brief you can use
Write five lines: the recurring job; the person who reviews it; the sources involved; the result that would help; and the decision that remains with a person. That is enough to begin a useful conversation.