Better briefing
Define the objective, context and quality standard before asking for an answer.
Make AI a shared capability.
Not an individual workaround.
Practical, role-specific learning for teams that want to use AI with greater confidence, consistency and judgement.
Discuss your teamBuild capability across your team.
Some people are experimenting. Others are not sure where to begin. The useful habits have not become shared habits. We bring the team together around the work they actually do, not a catalogue of tools.
For teams ready to move from individual experimentation to a considered, shared way of working.
Capability you can
put to work.
Sounder judgement
Check what matters. Know when to revise, reject or bring in a person.
Useful habits that travel
Document approaches another colleague can repeat without the original builder in the room.
A clear structure.
Room for your context.
We agree the specific work and its boundaries before we begin. Here is the method that shapes the engagement.
01Understand the work
Choose relevant tasks, establish the starting point and agree what a useful result looks like.
What stays with youA task map and a shared quality standard.
02Brief with context
Practise supplying the objective, sources, constraints and examples that the task actually needs.
What stays with youRole-specific briefing patterns.
03Evaluate before using
Compare outputs against an agreed rubric. Include difficult cases, not just a convincing demonstration.
What stays with youWorked examples and a practical review rubric.
04Fit the workflow
Clarify handoffs, approvals, storage and exceptions. Decide where the human judgement belongs.
What stays with youTwo workflow cards for agreed task families.
05Build the playbook
Turn useful experiments into clear, reusable instructions. Test whether someone else can follow them.
What stays with youA concise team playbook.
06Review and continue
Review the agreed evidence, record limitations and decide what happens over the next 30 days.
What stays with youA sponsor review and a continuation plan.
The work should leave
something behind.
Clear artefacts, shared understanding and a practical next step. Not a folder of slides that nobody opens again.
- A preparation session with your sponsor
- Exercises using approved or sanitised material
- Live, guided practice on relevant tasks
- Briefing patterns and a quality rubric
- Workflow cards and a shared team playbook
- A review of progress and sensible next steps
Before we begin.
Do we need a technical background?
No. We focus on work, context and judgement rather than coding. We agree the starting level before the programme begins.
Is this tied to one AI tool?
No. The method is about tasks and evaluation. Practical exercises use the systems your organisation permits and the tools relevant to the work.
Can we use our own documents?
Where your organisation approves their use. We agree suitable material in advance and use sanitised or illustrative examples when confidential information should not leave your environment.
How will we know whether it helped?
We agree a baseline and a few useful measures before delivery. Those might include task quality, review effort, or whether people can repeat a method independently. Attendance alone is not the outcome.
Do you guarantee a percentage improvement?
No. We report what the evidence supports, including limitations. A credible review matters more than an impressive-looking number.
A clear scope, from the start.
The six-week format is our starting point, not a one-size-fits-all commitment. Cohort size, task families, session length and follow-up support are agreed in the written proposal. Bespoke software development is a separate scope.
Start with your work.
Tell us who is involved, what matters and what you would like to make better.