The method has to survive us leaving

The meeting decides. Training transfers. Same kind of writing, your people: they name what the tool may draft, they keep a draft sendable, someone accepts the owner. They leave with a method they can use next week. Not a certificate.

01

What it may use

Twelve items. Published policy is green — that drafts the reply.

02

See a bad draft

The model writes a Thursday you would not send.

03

Fix the line

Return that line. Draft again from the policy.

04

They keep the method

The method, the owner, the next reply. Not a certificate.

The ten programmes
CodeProgrammeWho it is forLength
ST-150Everyday AI, SafelyAll staff who use AI toolsHalf day
EX-100Leadership SessionBoard, CEO, senior managementHalf day
LD-200The Efficiency ProgrammeFunction and P&L owners2 days + 90 days
MG-300Finding the WorkMiddle management, team leads1 day
PR-400The Method LabYour subject-matter experts2 days
EN-500Engineering StandardsEngineers, QA, IT security3 days
RC-600Governance and AssuranceRisk, compliance, audit, finance1 day
HR-700Workforce and ChangeHR, function heads, comms1 day
SM-100The Working SessionLeadership of smaller companies1 day
SM-200The MonthSmaller companies, with follow-up1 day + 3 clinics

Every course produces something you keep — a policy, a ranked plan, a tested method, a signed approval. Not a certificate.

The curriculum underneath the ten

Seven levels, three role pathways and eleven functional labs, with a design standard every lesson is built against — six elements, and a rule that a concept taught but never practised comes out of the programme. It is published in full so you can argue with it before you buy any of it.

Read the curriculum
Next step

Ninety minutes first. Training is a different day.

Name the work. We write whether it is worth doing. If yes, your people learn the method.

Book the ninety minutes