Every team that runs a project management simulation starts by making a plan. Most fall behind by round three. That's not a flaw in the exercise. It's the lesson — and most PM courses never get there.
The Problem with Plan-Centric Education
Project management education is, almost by necessity, built around planning. Students learn to create work breakdown structures, set baselines, sequence dependencies, allocate resources, and calculate critical paths. These are real skills. They matter. But they represent only one half of what project managers actually do.
The other half — monitoring reality against the baseline, recognising early that something has shifted, communicating that shift upward before it becomes a crisis, and re-baselining without catastrophising — is rarely taught explicitly, because it's hard to teach from a slide. It can only be practised under pressure. And most classroom environments don't create real pressure.
PMI's own research consistently finds that the majority of project failures aren't planning failures. The plan was adequate. What failed was the organisation's ability to adapt when circumstances changed (PMI, 2021). We teach the thing that's easier to teach and call it project management. The rest we leave to experience.
What Randomness Actually Teaches
The luck mechanic in Planets, our project management simulation, introduces configurable random events mid-simulation. These aren't edge cases invented to be dramatic. They're drawn from the kinds of disruptions real project teams face: a key resource becomes unavailable, scope expands without a corresponding budget adjustment, a dependency external to the team slips and pulls everything else with it.
The disruption arrives at a moment teams don't choose. They have a round in progress. They have commitments. They have a plan they were, until a moment ago, on track to deliver. Now they don't.
What happens next is where the learning is. Some teams freeze and keep executing the old plan, hoping the disruption resolves itself. Some overreact and rebuild the entire schedule from scratch, losing two rounds to re-planning when one would have done. The best teams do something harder: they assess the actual impact, communicate it clearly, adjust the minimum necessary parts of the plan, and get back to work. That's not a natural response. It's a trained one.
Seeing the Plan vs. Reality in Real Time
We've added a suite of charts specifically to support the randomness mechanic: Gantt, burndown, earned value, and fever chart. These aren't decorative — they're the tools that make the gap between plan and reality visible before it becomes unrecoverable.
When a team's burndown chart starts drifting upward, that's an early signal. If they catch it in round three, they have options. If they notice it in round five, they're choosing between bad and worse. Learning to read these signals — not as abstract data visualisations but as live diagnostic information — is one of the things this simulation is explicitly designed to develop.
Instructors control how disruptive the luck events are. A cohort of first-year undergraduates and a room full of working project managers don't need the same level of disruption. The mechanic is configurable precisely because teaching resilience is not a one-size exercise.
Resilience Is a Learnable Skill
This is the claim that tends to get resisted: that resilience — the ability to adapt under pressure without losing composure or direction — can actually be taught. It sounds like a personality trait. It isn't. It's a set of behaviours: noticing early, naming the problem accurately, communicating without dramatising, adjusting without discarding everything.
Those behaviours can be practised. A simulation is the only environment in which students can practise them without consequences — where the disruption is real enough to feel threatening but safe enough that "we got it wrong in round four" is a useful insight rather than a professional setback. That's what makes simulation-based learning irreplaceable for this kind of skill. No case study puts the clock on the wall.
Want to learn more about Planets and how the luck mechanic works?
Request a demo →
