Workshops & team upskilling
Build skills your team can put to work.
Practical workshops, guided practice and team training around the work you actually do. Learn to evaluate AI tools, use Claude Code or Codex responsibly, design automations and review the results with confidence.
Agree the scope, access, timeline and price before committing.
The starting point
Your team has access to AI tools but needs the skills and shared practices to use them well.
Business teams adopting AI, engineering teams changing their development workflow, and leaders who need a shared understanding of what to automate and what to keep human.
Role-specific practice, reusable review checklists and a concrete adoption plan.
When another starting point may fit better
If the team needs a production system delivered, commission delivery or embedded support. Training helps people practise and adopt a skill; production delivery needs its own scope.
Choose what the team should be able to do.
Choose a starting point and inspect a sample of the decisions, review evidence and handover it involves.
A focused team workshop
Work through one task with synthetic or approved examples. Practice giving context, checking outputs and deciding when to escalate. The agenda follows your team's starting point.
A workshop practice card
An operations team practises reviewing an AI-generated callback brief.
- Practice task
- Compare a draft brief with a synthetic request and flag unsupported details.
- Deliberate difficulty
- The example leaves an owner or required field missing.
- Participant evidence
- Explain what is supported, what needs clarification and who handles the next action.
- Keep afterward
- A reusable review checklist and one agreed task for continued practice.
Participants explain their decisions using the source, rather than accepting a polished-looking draft.
A practical review habit and materials the team can use after the session.
Selected example: A focused team workshop.
Tangible outputs
Practice, review habits and a team adoption plan.
- A role-specific agenda and preparation checklist
- Hands-on exercises and reusable review checklists
- Team guidance on approved tools, data and permissions
- A skills/action review and recommendations for continued practice
How to judge the result
Participants should demonstrate the agreed task, explain how they checked the result and recognise when to ask for help. Attendance alone does not show that the skill is usable.
Scope and responsibilities to agree
Sessions are tailored after a readiness conversation; duration, group size and follow-up are scoped together. Tool subscriptions are separate unless specified. Workshops are not vendor certification and should not use unapproved confidential data.
Learn a task, practise it, then review the result.
- 01
Meet the team where they are
Assess roles, experience, approved tools and the decisions people need to make.
- 02
Learn by doing
Use a realistic exercise, deliberate failure cases and feedback. Teach people to inspect results, not just generate them.
- 03
Make the learning stick
Leave exercises, agreed practices and a named next action. Optional follow-up sessions support adoption.
For the first conversation
Bring a starting point, not a finished brief.
- Describe participants’ roles and current experience.
- Choose a task they should be able to practise after the session.
- Confirm approved tools and examples that can be used safely.
Use general or approved examples. We’ll agree any deeper access before reviewing private systems.
Free editable notes for your team. No email needed.
Before you commit
Your questions, answered.
Can nontechnical colleagues participate?
Yes. We design business-user, leadership and engineering tracks rather than assuming one agenda fits everyone.
Can you train our team on our own workflow?
Yes, subject to approved access and data. We can begin with synthetic examples and move to a controlled internal exercise.
Should we choose a workshop or an upskilling programme?
Choose a workshop for one bounded practice task and a shared introduction. Choose a programme for repeated practice, feedback and support adopting a habit. We scope the format around what participants should be able to demonstrate afterward.
What shapes the training price?
Participants' roles and experience, session preparation, the practice environment and follow-up shape the quote. The proposal names the agenda, group size, format, materials and review activity. Tool accounts and licences are separate unless included explicitly.
What should participants prepare?
Choose an approved task, arrange the agreed tool access and bring a general example of the work today. The preparation checklist explains any repository or account setup. Synthetic examples can be used where live information is unsuitable for practice.
Make progress before a bigger commitment
Take one useful step with your team.
Describe participants’ roles and current experience. This gives you something concrete to discuss, whether you work independently or bring us in.
Use the free planning guide ↗Prefer to prepare it yourself?
AI coding team playbook
Your team uses Claude Code or Codex without a shared review practice. Review an illustrative example and the requirements before choosing this starting point.
Explore the toolkit preview ↗Your next decision
What should your team be able to do with confidence?
Tell us who is learning, their starting point and one task the training should help them handle.
A specific task in mind?
Inspect a focused first engagement before enquiring.
The enquiry is free. Paid work starts after an agreed scope and proposal.