The project pack arrived showing a team that had performed by every conventional measure. On time. Within budget. Every dependency tracked.
Three months later, the environment shifted. A major stakeholder restructured. A key supplier withdrew. A regulatory requirement changed. The team that had looked unbeatable was struggling to find its footing in conditions its structure was never designed for.
What the project manager was discovering had a structural source.
In 2012, Nassim Nicholas Taleb introduced the idea of antifragility to describe systems that do more than withstand stress. The fragile breaks under pressure. Systems built to endure absorb it without changing. The antifragile becomes stronger because of it. Most organisations, and most delivery teams within them, are built for the middle category when sustained volatility demands the third.
The evidence is consistent. The Standish Group’s 2020 CHAOS report found that only 31 per cent of projects were delivered successfully, with 50 per cent challenged and 19 per cent failing outright. A Bain & Company analysis from 2024 found that 88 per cent of business transformations failed to achieve their original ambitions. In both cases, the failure driver was rarely the competence of individual team members. It was the inability of the team’s structure to adapt when the environment shifted.
The window to architect antifragility opens before the disruption arrives. Most teams discover their structure on the day it fails.
Where efficiency becomes brittleness
Most project teams are built for efficiency. Resources are scheduled close to maximum load. Processes are designed to minimise slack. Reporting is calibrated to the original brief.
In stable conditions, these choices produce performance. In volatile ones, they produce brittleness. A team running at maximum load has no buffer. A process with no slack cannot accommodate scope change without breaking something else. A reporting structure calibrated to the original brief cannot signal that the brief is wrong.
The team that looks optimal on a dashboard is often the team least capable of responding when the conditions that produced the dashboard change.
Three structural conditions for antifragility
Antifragility is built into the team’s structure, or it is not built at all.
Deliberate slack. Antifragile teams carry reserved capacity that is not allocated by default. This is the structural equivalent of the redundancy that allows kelp forests to regenerate after storm disturbance. The scaffolding that looks unnecessary in calm conditions is precisely what makes regeneration possible when conditions change. Teams without slack cannot absorb disruption. They can only defer it.
Distributed decision authority. A team that must escalate every decision to a governance layer meeting quarterly cannot move at the speed change requires. Antifragile teams have pre-agreed authority to make defined categories of decision without escalation. The structural clarity is about what can be decided at what level, and what triggers prompt escalation upward.
Stress as diagnostic data. Fragile teams treat disruption as a problem to contain. Antifragile teams treat it as information about the gap between current capability and current environmental demand. The distinction is structural. Does the team convert disruption into a capability review, or only into a risk log?
What the PM who builds this looks like
A project manager building antifragile teams does something most project management frameworks do not explicitly require. They manage upward as much as they manage across.
Antifragile team design cannot be achieved underneath a governance structure where every scope change requires a committee with a six-week meeting cycle. The PM who recognises this is identifying a structural constraint that no volume of team retrospectives will remove. The response is to name it at the level that can change it. That level is the governance above the team.
Questions for your next project review
Put these on the agenda before the next project phase begins.
Antifragility is an architecture decision. The teams that grow stronger under pressure are the teams most structurally prepared to use pressure as the data it is.
Stuart J. Green is the founder of Blue-Green Advisors and author of The Regenerate Leap. He advises boards and leadership teams on operating model design and the governance of structural change. He developed the Operating Model Fitness Index, a scored diagnostic of structural fitness for CEOs and boards navigating transformation.
