For managers and team leads
Your company bought AI licences. Almost nobody’s work actually changed.
Redesign one real workflow on your team, and learn where AI stops before it costs you.
- Duration
- 5 weeks
- Commitment
- 100 min live+ 30 min pre-work+ 60 min applied
- Next cohort
- Nov 3, 2026
- Format
- Live online · onsite
What this asks of you
100 minutes live each week at a fixed time, plus about 30 minutes of preparation beforehand. The preparation is not optional reading — it produces a short piece of work you submit, and the session opens on what people submitted. Between sessions you apply it to your own workflow, which takes about 60 minutes. That is 3.2 hours a week in total, and we would rather you knew that now than after you paid. Cohorts are deliberately small so that is possible; seats for each date are shown below.
This is for you if
- You lead a team and there is real work you could hand over
- Your organisation has AI tools and almost nobody has changed how they work
- You need to decide what your team should stop doing by hand
- You will be asked to justify the change with a number
This is not for you if
- Engineers looking to build AI products — this is about managing work, not shipping models
- Anyone wanting a tool tour. We use your real workflows, not a demo dataset
- Teams with no sanctioned AI tool at all — get access first, then take this
What you will be able to do
By the end of the programme, without supervision.
- Map a recurring team workflow and decide, step by step, what to keep, augment, automate or delete
- Write a delegation brief an AI can actually execute — and recognise when the brief is the problem
- Name exactly where AI stops being reliable in your own job, and prove it with a counter-example
- Design a verification check proportionate to what it costs you to be wrong
- Set team norms for disclosure, data handling and human review that people will actually follow
- Re-baseline what a recurring deliverable should take, and defend the new number to your own manager
Week by week
Foundations and the FRAME method
How the model actually works and why it fabricates. Context as the product. The four incidents every manager should be able to name: Mata v. Avianca, Moffatt v. Air Canada, the Samsung leak, and the Arup deepfake.
Workflow teardown
Take one recurring team process and map it step by step. Mark each step keep, augment, automate or delete — and justify every automate against what failure would look like and who would see it.
The manager’s daily surface
Delegation briefs, meeting compression, status roll-ups that survive scrutiny, and feedback prep where the model argues the other side. Where a practitioner guest is available, they take the feedback segment.
Managing a team through it
The part no other programme teaches. Gains skew to novices and are near zero for your best people, so one flat productivity expectation punishes exactly the wrong staff. Plus adoption theatre, shadow AI, and re-baselining estimates.
Capstone
Present your redesigned workflow to the cohort and defend it against a rubric: problem selection, frontier judgement, verification design, measurement, and risk handling.
Booster one
Reinforcement at the interval the evidence supports, not when it suits a sales calendar. What decayed, what stuck, what broke in practice.
Booster two
Behaviour-level check: is the redesigned workflow still running, and is the measured gain still there?
What you keep
Dates and pricing
Regional pricing. Pick the cohort in your timezone.
Nov 3, 2026 – Dec 1, 2026
Weekly, 12:00 Toronto time
12 of 12 seats remaining
The founding rate is an exchange, not a discount: we ask for a written testimonial and permission to publish one measured result.
Join the waitlistNov 5, 2026 – Dec 3, 2026
Weekly, 19:00 Karachi time
15 of 15 seats remaining
The founding rate is an exchange, not a discount: we ask for a written testimonial and permission to publish one measured result.
Join the waitlistTraining a whole team?
A private cohort runs the same curriculum against your team’s own workflows and data, online or onsite, with a documented training record.
In-house trainingCommon questions
Do I need to be technical?
No. There is no code in this programme. If you can write a brief for a new hire, you have the prerequisite.
We already pay for ChatGPT and Copilot. Why would we pay for this?
Because the licences are the part that already worked. In the largest field study available, only about 40% of people given Copilot used it regularly after six months. This programme is about changing how work is done, not about which button to press.
What if I miss a session?
Sessions are recorded and the applied work is asynchronous. But the cohort and the schedule are most of what you are paying for — if you expect to miss more than one, take the next cohort instead.
Will I get a certificate?
You get a certificate only if you pass the capstone against a published rubric. An attendance certificate would not mean anything, so we do not issue one.
Can my employer be invoiced?
Yes. Ask on the waitlist form and we will send an invoice with purchase-order details.
Next cohort starts Nov 3, 2026
Small cohorts, because the applied work needs real attention.
See dates and pricing