We’re publishing case studies as our pilot programs land in evidence. Each one is written the same way.
The team on day one
Shape, size, the AI work they were already doing - honestly, without the marketing gloss.
The program we ran
The specific shape - cohort rhythm, role splits, practicum choices, the parts we adjusted mid-flight.
What changed, measured
Assessment delta, evidence pack scope, time-to-document - with the numbers, not the vibes.
What we'd change next time
The edits we'd make if we ran the same program again - the part most write-ups leave out.
Discovery → cohort → evidence → retro
- 1
Discovery
A scoping call, a written brief, and a starting-line assessment so the delta is measurable.
- 2
Cohort
Live teaching, role-specific practicums, office-hours support - documented as it happens.
- 3
Evidence
The Article 4 pack: per-role literacy record plus the list of AI-assisted tasks shipped.
- 4
Retro
A written post-mortem - what landed, what did not, what we would change. Included in the publication.
“Case studies are teaching notes, not marketing testimonials. The parts that did not go to plan are the parts worth reading.”
AISO Learn editorial note
See where your team would land
Case studies are useful, but a 4-minute Scorecard tells you where your team stands. The next case study could be yours.