Analysis Paralysis — Clocks, Clouds and the Cost of Waiting for Certainty
Commission more analysis, hold another meeting, run a thousand simulations. Then watch the clock, because not deciding is also a decision.
Open simulation →Try this first
Suggested exploration: about 8 minutes.
Read the opening room description, type look, then explore an available exit.
What to look for: Each location reveals only part of the system; progress depends on discovering connections.
What this simulation shows
Experienced members of an organisation often move through it without noticing the shortcuts, assumptions and informal rules they have learned. A newcomer does not have that hidden map. They experience the system as a series of questions: where should I go, who can help, what is really happening, and which clue should I trust?
This short text adventure makes that experience playable. You begin with only partial information and have to explore, ask questions, collect evidence and decide when you understand enough to act.
How to use it
Use the command line or the quick-action buttons to look around, move between locations, talk to people, examine clues and build your case. Try to reach the right conclusion, but pay attention to how much of the system is visible only through other people’s knowledge and behaviour.
CEEFAX FOR SCHOOLS — PAGE 700
◉ ACORN SCHOOL COMPUTER — CORRIDOR B TERMINAL
What to take away
The simulation is deliberately small, but the mechanism is familiar in larger organisations. A new starter is not simply missing information; they are revealing the information the system assumes everyone already knows. The most useful response is often to improve the system rather than criticise the person trying to navigate it.
How to use this simulation
Change one input at a time, run the model, and compare the result with the starting state. Then repeat the experiment with a different constraint or strategy so you can see which relationships drive the outcome.
What to look for
Look for trade-offs, thresholds, feedback loops, and points where a locally attractive decision produces a worse system-wide result. The simulation is intended to make the article's idea observable, not to predict a real operation.
Limitations
This is a deliberately simplified model. It omits the data quality, exceptions, human judgement, and operational constraints of a live system, so treat its behaviour as an illustration of a mechanism rather than as a planning recommendation.
Read the related article
Read: The Smallest Member of the Organisation Knows the Least →
Explore the complete Systems Thinking for Product Managers series