A workflow starts with the result
First define what needs to be done and who will use the result.
An advanced workflow does not start with a long prompt, but with an observable outcome. Describe the decision or usage moment, the target audience, and the characteristics the end product must meet. This prevents an impressive text from turning out to be unusable.
Distinguish between the result and the activity. 'Analyze customer feedback' is an activity; 'deliver a decision memo with the three most substantiated improvement priorities, evidence, and open questions' is a result. Only add process steps when they improve control, safety, or quality.
Before you begin: you can already write a clear prompt, refine an answer and check an important claim. Practise here with invented data. The examples provide all the input you need; you do not need a paid subscription or a connected business environment to practise the method on paper or in an ordinary chat. Some product features do depend on your account.
- Result before activity
- Audience and intended use
- Two to five success criteria
- Explicit stop or approval moment
Terms in plain language
- Workflow
- An agreed sequence of steps from input to a checked result.
- Acceptance criterion
- An observable requirement used to assess whether the result is usable.
Work: a management memo must identify the decisions to be made. Study: a study sheet must reveal misconceptions. Personal use: a comparison must stay within your budget and preferences.
Result: [final product]. User: [audience]. It is useful if it meets: [criteria]. Ask no more than three questions about missing essential information, then propose a workflow. Do not create the final product yet.Rewrite one recurring task as a result, specifying the audience, intended use and three success criteria.