Curriculum
How Systems Analysis Studio unfolds
A three-day path designed for mixed product and engineering groups. Each day ends with an artifact you can take back to your backlog — not another slide deck that dies in email.
Day 1
See the system
Boundary sketches, actor maps, and a shared glossary so the cohort stops talking past each other.
Day 2
Pressure-test the story
Trace dependencies, surface failure modes, and rewrite one live initiative with evidence tags.
Day 3
Hand off cleanly
Produce a ship-ready analysis note, peer critique it, and lock a reusable template for your team.
Private team runs can reorder exercises around one live initiative. Open cohorts use shared scenarios so strangers can critique safely.