| Task | Starting material | Human check |
|---|---|---|
| Internal knowledge | Approved team documents | Identify an owner and update date |
| Onboarding | Invented process checklist | Check access and responsibilities |
| Workflow experiment | Repeated task | Define failure and maintenance criteria |
What could a practical exercise look like?
Select an invented weekly reporting task, map its inputs and prepare an assisted draft. Define who checks it, what failure looks like and when to stop the experiment. Include ownership and maintenance in the decision to continue.
What working document could the team keep?
A bounded experiment brief, review criteria and a named ownership requirement.
What needs particular care?
A fast prototype is not a production commitment. Review access, data, operating costs and ownership before rollout. No investor or ecosystem introduction is included unless explicitly agreed.
What should you prepare before the session?
Bring one representative task and explain who performs it, which sources are available and who reviews the result. Agree the tools and documents authorised for the exercise before sharing anything. The final programme, trainer, dates and quotation are defined during scoping.
