The launch looked strong.
The proposition was clear. The audience response was positive. The early numbers supported the preferred story. Leadership approved scale.
Then one assumption moved.
A supplier failed. A platform changed its rules. A joke escaped its intended context. Demand exceeded support capacity. A founder became the story. A regulator asked the question no one had put in the deck.
The strategy did not slowly underperform.
It broke where it had always been thin.
Most evaluation systems reward visible strength
Teams are trained to identify advantages: differentiation, market demand, cultural relevance, founder credibility, growth rate, channel efficiency, customer enthusiasm.
Risks are usually added later in a smaller font.
That structure treats downside as a caveat to the main argument. Fragility requires a different posture. It asks whether the system contains independent failure forces that cannot be inferred from the strength score.
A bridge is not safe because ninety-nine percent of it is strong.
The weak joint gets a vote.
Fragility is often nonlinear
Large projects repeatedly demonstrate why averages can be misleading. Bent Flyvbjerg and colleagues have documented fat-tailed cost and schedule outcomes across infrastructure and information-technology projects: most projects may remain near the center, while a meaningful minority produce extreme overruns capable of dominating the portfolio result.[1]
In one study of 1,355 public-sector IT projects, roughly one in six became a “black swan” with cost overruns above 25 percent and schedule overruns above 50 percent. Longer projects carried materially higher risk.[2]
The exact rate varies by domain and dataset. The structural lesson is stable: failure is not always a slightly worse version of success. Some systems contain thresholds after which the damage accelerates.
Fragility lives near those thresholds.
Strong signals can conceal brittle dependencies
A business can have strong demand and fragile unit economics.
A campaign can have cultural energy and fragile brand permission.
A founder can have extraordinary credibility and create a single point of reputational failure.
A strategy can be internally coherent and depend on one untested distribution partner.
These are not contradictions to be resolved through an average. They are interacting conditions.
High Amplification Energy can increase Fragility by exposing the idea to more scrutiny. High Intrinsic Strength can still fail under poor timing. Strong execution in one channel can create dependence that becomes dangerous when the channel changes.
The question is not whether the idea is strong or fragile.
It can be both.
Failure has a location
The Challenger disaster remains a severe example of what happens when known technical concerns, organizational pressure, communication structures, and launch timing converge. The Rogers Commission found that the decision process was flawed and that the history of O-ring performance had not been adequately represented in the launch decision.[3]
The lesson is not that every business decision resembles a spaceflight.
The lesson is that catastrophic outcomes often have an address before they have a date.
Someone knows the component is unreliable in cold conditions. Someone knows customer support is already overloaded. Someone knows the brand claim depends on behavior the organization does not practice. Someone knows the forecast assumes a conversion rate no prior cohort achieved.
Fragility becomes dangerous when the knowledge is distributed and the decision is centralized.
- For any meaningful strategy, identify:
- 1. The single assumptions carrying disproportionate weight.
- 2. The conditions under which performance changes nonlinearly.
- 3. The dependencies the organization cannot directly control.
- 4. The contradiction most likely to become visible at scale.
- 5. The earliest observable signal of degradation.
- 6. The response available before the system crosses the threshold.
- Do not bury this in a generic risk register.
- Name where the idea breaks.
Evidence notes
[1] Flyvbjerg, Bruzelius, and Rothengatter, Megaprojects and Risk; Flyvbjerg and Budzier, “Why Your IT Project May Be Riskier Than You Think,” Harvard Business Review, 2011; subsequent large-sample project research.
[2] Flyvbjerg and Budzier’s analysis of 1,471 IT projects is commonly cited for extreme overrun risk; related public-sector analyses have examined 1,355 projects and the effect of duration on risk. Exact samples and thresholds differ by publication.
[3] Presidential Commission on the Space Shuttle Challenger Accident, 1986. The report examined technical failure and serious deficiencies in the launch decision process.
Cross-reference
See Integrity Multiplier, Asymmetric Upside Is Not Optimism, and the Reality Stack article A Score Is Not a Prediction Until Reality Has Had a Vote.