Module 05 · 12 min
Complexity Is Exponential
And human brains are wired for straight lines
Why conventional risk registers systematically underestimate complex change, and what the exponential nature of complexity means for how you plan.
The clue in the cases
Every case in Module 4 shares a structure: small problems interacting. Interaction is multiplication, not addition. Add a stakeholder group and you do not add one relationship; you add one relationship with every other group. That is why complexity is exponential.
We do not think exponentially
“The greatest shortcoming of the human race is our inability to understand the exponential function. We live in a world that can change exponentially, but we have brains hardwired to plot things out linearly.”
We saw it collectively during the early weeks of the COVID-19 pandemic, when doubling times were public knowledge and still consistently under-read. We see it in compound interest, in population and resource curves, and in the way technology adoption S-curves catch incumbents out.
“If you ask me what is the worst thing in the world, I will say it is compound interest.”
What is wrong with the risk register
The standard approach: list the risks, estimate likelihood X, estimate impact Y, multiply X by Y. Then build a table of thirty, sixty, ninety risk factors and score them all.
“When the risks you anticipated happen, they become issues. When the risks you didn't anticipate happen, you become a former project manager.”
- A register scores risks individually; failure comes from their combination.
- It grows without limit, and past a certain size nobody reads it.
- It gives a comforting appearance of control while the interaction effects go unmeasured.
- It says nothing about whether this organisation can cope with this project.
Tipping points
“As complexity increases, the cost of managing the complexity increases at an exponential rate until the system finally collapses.”
Complex projects are vulnerable to tipping points: conditions that, once crossed, cause system behaviour to change radically. Terminal 5 crossed one at around 6am. LAS crossed one within an hour of go-live. TSB crossed one during the cutover weekend. Before the tipping point, everything looks recoverable. After it, nothing does.
Key takeaways
- complexity multiplies; it does not add.
- Human estimation is linear, so complexity is habitually underestimated at business-case stage.
- Risk registers measure items, not interactions — which is where failure actually lives.
Take it back to work
- How many separate risks are on your register, and when did the board last discuss how two of them would interact?