What will your team work on?
A proposed sequence, adapted to your tools, experience and available time.
Check access first
Test the video call, approved AI account and sample documents. Keep a backup exercise if a participant cannot access a tool.
Keep the exercise focused
Work on one task at a time. Alternate a short demonstration with individual practice and a review of different outputs.
Make the work visible
Use a shared worksheet to record the input, instructions and checking steps. Discuss differences rather than watching one person type.
Try again between sessions
Give participants a small approved task to repeat in their own context. Use the next session to examine what worked and what broke.
What does practice look like?
A shared practice log
Each participant summarises the same fictional document. Compare omissions in pairs, then agree a review checklist the whole team can use.
A teaching example. It does not describe a completed client engagement.
| Work product | What makes it usable |
|---|---|
| Source material | Approved inputs, with the useful context retained. |
| Reusable instructions | A clear task, constraints and expected output format. |
| Review checklist | The checks a colleague must perform before using the result. |
| Next experiment | An owner, an example and criteria for deciding whether to continue. |
What should you bring?
Bring a concrete question, a representative example and the rules your team already follows. The purpose of preparation is to spend the session practising, with the right accounts, permissions and source material in place.
- A task that someone on the team does regularly.
- An approved AI tool, or a decision about which environment to use.
- A sample that can be shared safely, preferably stripped of sensitive data.
- A reviewer who knows what a good result should look like.
The final proposal sets the duration, group size, trainer, scope and fee. Tool subscriptions and any follow-up are specified separately.
