Slack's pivot from Glitch
How a failing game studio noticed it had built the wrong product — and shipped the right one to itself in the process.
read the case
// real-world PM cases · sourced + cited
The simulator teaches what to do under pressure. These cases teach what people actually did. Each one cites authoritative public records — government reports, founder interviews, peer-reviewed retrospectives — and walks through the decisions, the consequences, and the lessons.
How a failing game studio noticed it had built the wrong product — and shipped the right one to itself in the process.
read the case
How a flight director's risk-management discipline turned a near-fatal accident into NASA's most-studied recovery.
read the case
How a federal program that hit every milestone shipped a system that didn't work — and what the rescue team did to fix it.
read the case
How a program that delivered everything it promised, on time and on technical spec, still went bankrupt nine months after launch.
read the case
How cost-driven scope decisions on a derivative-airframe certification program compounded into two fatal accidents.
read the case
How reusing flight-proven software on a new vehicle, without re-validating it for the new flight envelope, destroyed a $370M rocket 37 seconds after liftoff.
read the case
How removing physical interlocks on the strength of software validation arguments produced six massive radiation overdoses, three of them fatal.
read the case
Why cases?
The simulator gives you reps on decisions. Cases give you receipts: what happened when somebody actually made the call. Both are required. Pretending you’d do better than the team that shipped Healthcare.gov is the cheap version of PM training; reading what they actually did and why is the durable one.