Published at: 2026-05-14T21:03:46+05:30
2026-03-19 — Black swan events — You can’t predict shocks; you can design for convexity
Thesis
Black swan events are not just “rare surprises.” They are the moments when hidden fragility gets priced in all at once. Because you cannot reliably forecast the timing or shape of these shocks, the practical goal is not prediction. It is convexity: structuring your startup, career, and decisions so that downside is bounded while upside remains open. In a world of fat tails, the best strategy is to build systems that survive volatility and occasionally benefit from it.
Context
Nassim Nicholas Taleb popularized the term “black swan” to describe events that (1) sit outside regular expectations, (2) carry extreme impact, and (3) become explainable only after the fact, once our brains rush to create a neat story. The label matters because most modern planning quietly assumes the opposite: that the future will be a smooth extension of the past, that deviations are small, and that probabilities can be estimated from history.
That assumption works in “thin-tailed” worlds where variation is limited and averages are meaningful: manufacturing defect rates, many biological measures, even the time it takes to drive to an office on a normal day. But technology, finance, geopolitics, and entrepreneurship are “fat-tailed.” Here, a small number of outliers account for most outcomes. A single platform shift, regulation change, or security incident can dominate everything that came before it.
In fat-tailed domains, the hazard is not uncertainty in the middle. It is the extremes. Most teams respond by demanding better forecasting. But forecasting is often the wrong tool. The correct tool is design.
Key ideas
1. Stop asking “What will happen?” and start asking “Where am I fragile?”
A useful reframing is to treat black swans as a stress test for your model of reality. If an event “no one could have predicted” ruins you, the problem is rarely that you failed to predict. The problem is that your system required prediction to survive.
That is what fragility is: dependence on a narrow range of expected conditions. Fragile systems perform well in the baseline scenario and collapse when the world deviates.
In startups, fragility often looks like:
A single distribution channel.
A single customer that constitutes most revenue.
A single integration or platform policy.
A single fundraising path that must occur on a tight timeline.
A security posture optimized for “normal times,” with no real incident muscle.
When someone says, “We have a plan,” the important question is: What assumptions must remain true for this plan to work? If the list is long, you are not planning. You are praying.
2. In fat tails, “risk” is not variance; it is ruin
Most business risk metrics are built for small fluctuations: quarter-to-quarter volatility, expected error bars, scenario trees with polite outcomes. In fat-tailed reality, the primary risk is ruin: an irreversible failure state.
Ruin is different from loss. You can recover from loss. You cannot recover from zero.
This is why “efficient” systems are often brittle.
If you run with two weeks of cash and assume the next raise will close, you are efficient.
If you run with twelve months of runway and assume your next raise might not happen, you are resilient.
Efficiency is a local maximum. Survival is a global constraint.
3. Convexity beats prediction
Convexity is a property of outcomes: when volatility increases, you benefit more from the upside than you suffer from the downside.
A simple mental model:
Concave bets: Small consistent gains, catastrophic tail risk.
Convex bets: Limited losses, open-ended gains.
Most modern organizations accidentally build concavity:
Leverage (financial or operational) to boost steady-state performance.
Tight coupling (everything depends on everything).
Single points of failure.
Convexity is the opposite:
Bounded downside.
Optionality.
Redundancy.
Loose coupling.
You do not need to “know what the black swan will be” if you are positioned so that shocks do not kill you and sometimes create opportunity.
4. The venture power law is a friendly black swan
Entrepreneurship is a fat-tailed game on purpose. In venture capital, the distribution of returns is power-law-like: a few outlier wins can dominate a fund’s total outcome. That is not a bug. It is the system.
This matters for founders because it changes what “good strategy” means.
In a normal business, you optimize for steady compounding and minimize variance.
In a venture business, you often accept local inefficiencies to preserve the possibility of an outlier outcome.
The dangerous mistake is to combine power-law ambition with fragile finances. You can pursue a big outcome, but you must do it with a structure that does not require perfect conditions.
5. Resilience is not a deck; it is a set of habits
A resilience plan that lives in a document is not resilience. Resilience is operational muscle.
Organizations build resilience the way athletes build fitness: through repeated exposure, reflection, and adaptation. The Harvard Business Review framing emphasizes routines, simple rules, and the capacity to improvise under stress. When a crisis hits, teams do not rise to the occasion. They fall to the level of their training.
So your goal is to build:
Scripted routines for the first 60 minutes of chaos.
Decision checklists for high-stakes choices.
Debriefs that extract lessons quickly and change behavior.
6. Counterintuitively, redundancy is a growth strategy
Redundancy sounds like wasted cost until the day it becomes your moat.
Examples:
Two distribution channels rather than one.
Multiple suppliers, or at least pre-qualified backups.
Multiple people who can run payroll, handle incident response, and ship core features.
Multiple product lines, as long as they are not tightly coupled.
In calm periods, redundancy looks like inefficiency. In turbulent periods, redundancy looks like wisdom.
The key is to make redundancy selective rather than universal. You do not need backups for everything. You need backups for what would end you.
7. If you want antifragility, you need small stressors now
“Antifragility” is often described as beyond resilience: the ability to improve because of stress rather than merely withstand it. The practical way to approximate antifragility is not inspirational language. It is repeated, small stress exposure that produces learning.
In a startup:
Ship small, reversible changes.
Run chaos drills for systems.
Simulate outages.
Practice comms in high-pressure moments.
Run frequent customer feedback loops.
The goal is to avoid “one big test” administered by reality.
Counterarguments
“Black swans are unpredictable, so preparation is pointless.”
If you interpret “unpredictable” as “unmanageable,” you will do nothing. But unpredictability only limits forecasting. It does not limit positioning.
You cannot predict which supplier will fail, but you can avoid having only one supplier.
You cannot predict whether capital markets will freeze, but you can avoid a runway that assumes perpetual liquidity.
You cannot predict the next category shift, but you can avoid building a product that depends on one platform’s goodwill.
Preparation is not predicting the event. It is reducing the chance of ruin and keeping options open.
“Redundancy and buffers slow you down. Startups must move fast.”
Speed matters, but speed without survival is theatre.
Buffers do not have to mean bureaucracy. The highest-leverage buffers are often simple:
A clear incident runbook.
A minimum runway policy.
A cap on customer concentration.
A disciplined approach to security basics.
These do not slow you down. They prevent a single bad day from undoing years of work.
Takeaways
Black swans expose fragility. The right response is design, not prediction.
In fat-tailed domains, the primary risk is ruin, not volatility.
Convexity is the practical goal: bounded downside with open-ended upside.
The venture power law is a reminder that outliers drive outcomes; structure your company to survive long enough to meet them.
Build resilience as operational muscle: routines, checklists, debriefs, and drills.
Use selective redundancy for anything that can end you.
Pursue antifragility through small, repeated stressors and fast learning loops.
Ask, continuously: “What assumptions must stay true for us to live?” Then shrink that list.
Sources
POLITICO — “The Incredible, World-Altering ‘Black Swan’ Events That Could Upend Life in 2025” https://www.politico.com/news/magazine/2025/01/03/15-unpredictable-scenarios-for-2025-00196309
Allianz Commercial — “Business Black Swans” https://commercial.allianz.com/news-and-insights/reports/business-black-swans.html
Harvard Business Review — “Building Organizational Resilience” (Suarez & Montes) https://hbr.org/2020/11/building-organizational-resilience
MIT Sloan Executive Education — “How to build organizational resilience” https://executive.mit.edu/How-to-build-organizational-resilience.html
CNBC — “VCs use this ‘power law’ to decide whether to invest in startups” https://www.cnbc.com/2025/07/21/vcs-use-this-power-law-to-identify-massive-winners-to-invest-in.html
Wikipedia — “Black swan theory” (definition summary and references) https://en.wikipedia.org/wiki/Black_swan_theory
Yahoo Finance — “'Black Swan' author Nassim Taleb says brace for software bankruptcies …” https://finance.yahoo.com/news/black-swan-author-nassim-taleb-162028755.html
Thesis
Black swan events are not just “rare surprises.” They are the moments when hidden fragility gets priced in all at once. Because you cannot reliably forecast the timing or shape of these shocks, the practical goal is not prediction. It is convexity: structuring your startup, career, and decisions so that downside is bounded while upside remains open. In a world of fat tails, the best strategy is to build systems that survive volatility and occasionally benefit from it.
Context
Nassim Nicholas Taleb popularized the term “black swan” to describe events that (1) sit outside regular expectations, (2) carry extreme impact, and (3) become explainable only after the fact, once our brains rush to create a neat story. The label matters because most modern planning quietly assumes the opposite: that the future will be a smooth extension of the past, that deviations are small, and that probabilities can be estimated from history.
That assumption works in “thin-tailed” worlds where variation is limited and averages are meaningful: manufacturing defect rates, many biological measures, even the time it takes to drive to an office on a normal day. But technology, finance, geopolitics, and entrepreneurship are “fat-tailed.” Here, a small number of outliers account for most outcomes. A single platform shift, regulation change, or security incident can dominate everything that came before it.
In fat-tailed domains, the hazard is not uncertainty in the middle. It is the extremes. Most teams respond by demanding better forecasting. But forecasting is often the wrong tool. The correct tool is design.
Key ideas
1. Stop asking “What will happen?” and start asking “Where am I fragile?”
A useful reframing is to treat black swans as a stress test for your model of reality. If an event “no one could have predicted” ruins you, the problem is rarely that you failed to predict. The problem is that your system required prediction to survive.
That is what fragility is: dependence on a narrow range of expected conditions. Fragile systems perform well in the baseline scenario and collapse when the world deviates.
In startups, fragility often looks like:
A single distribution channel.
A single customer that constitutes most revenue.
A single integration or platform policy.
A single fundraising path that must occur on a tight timeline.
A security posture optimized for “normal times,” with no real incident muscle.
When someone says, “We have a plan,” the important question is: What assumptions must remain true for this plan to work? If the list is long, you are not planning. You are praying.
2. In fat tails, “risk” is not variance; it is ruin
Most business risk metrics are built for small fluctuations: quarter-to-quarter volatility, expected error bars, scenario trees with polite outcomes. In fat-tailed reality, the primary risk is ruin: an irreversible failure state.
Ruin is different from loss. You can recover from loss. You cannot recover from zero.
This is why “efficient” systems are often brittle.
If you run with two weeks of cash and assume the next raise will close, you are efficient.
If you run with twelve months of runway and assume your next raise might not happen, you are resilient.
Efficiency is a local maximum. Survival is a global constraint.
3. Convexity beats prediction
Convexity is a property of outcomes: when volatility increases, you benefit more from the upside than you suffer from the downside.
A simple mental model:
Concave bets: Small consistent gains, catastrophic tail risk.
Convex bets: Limited losses, open-ended gains.
Most modern organizations accidentally build concavity:
Leverage (financial or operational) to boost steady-state performance.
Tight coupling (everything depends on everything).
Single points of failure.
Convexity is the opposite:
Bounded downside.
Optionality.
Redundancy.
Loose coupling.
You do not need to “know what the black swan will be” if you are positioned so that shocks do not kill you and sometimes create opportunity.
4. The venture power law is a friendly black swan
Entrepreneurship is a fat-tailed game on purpose. In venture capital, the distribution of returns is power-law-like: a few outlier wins can dominate a fund’s total outcome. That is not a bug. It is the system.
This matters for founders because it changes what “good strategy” means.
In a normal business, you optimize for steady compounding and minimize variance.
In a venture business, you often accept local inefficiencies to preserve the possibility of an outlier outcome.
The dangerous mistake is to combine power-law ambition with fragile finances. You can pursue a big outcome, but you must do it with a structure that does not require perfect conditions.
5. Resilience is not a deck; it is a set of habits
A resilience plan that lives in a document is not resilience. Resilience is operational muscle.
Organizations build resilience the way athletes build fitness: through repeated exposure, reflection, and adaptation. The Harvard Business Review framing emphasizes routines, simple rules, and the capacity to improvise under stress. When a crisis hits, teams do not rise to the occasion. They fall to the level of their training.
So your goal is to build:
Scripted routines for the first 60 minutes of chaos.
Decision checklists for high-stakes choices.
Debriefs that extract lessons quickly and change behavior.
6. Counterintuitively, redundancy is a growth strategy
Redundancy sounds like wasted cost until the day it becomes your moat.
Examples:
Two distribution channels rather than one.
Multiple suppliers, or at least pre-qualified backups.
Multiple people who can run payroll, handle incident response, and ship core features.
Multiple product lines, as long as they are not tightly coupled.
In calm periods, redundancy looks like inefficiency. In turbulent periods, redundancy looks like wisdom.
The key is to make redundancy selective rather than universal. You do not need backups for everything. You need backups for what would end you.
7. If you want antifragility, you need small stressors now
“Antifragility” is often described as beyond resilience: the ability to improve because of stress rather than merely withstand it. The practical way to approximate antifragility is not inspirational language. It is repeated, small stress exposure that produces learning.
In a startup:
Ship small, reversible changes.
Run chaos drills for systems.
Simulate outages.
Practice comms in high-pressure moments.
Run frequent customer feedback loops.
The goal is to avoid “one big test” administered by reality.
Counterarguments
“Black swans are unpredictable, so preparation is pointless.”
If you interpret “unpredictable” as “unmanageable,” you will do nothing. But unpredictability only limits forecasting. It does not limit positioning.
You cannot predict which supplier will fail, but you can avoid having only one supplier.
You cannot predict whether capital markets will freeze, but you can avoid a runway that assumes perpetual liquidity.
You cannot predict the next category shift, but you can avoid building a product that depends on one platform’s goodwill.
Preparation is not predicting the event. It is reducing the chance of ruin and keeping options open.
“Redundancy and buffers slow you down. Startups must move fast.”
Speed matters, but speed without survival is theatre.
Buffers do not have to mean bureaucracy. The highest-leverage buffers are often simple:
A clear incident runbook.
A minimum runway policy.
A cap on customer concentration.
A disciplined approach to security basics.
These do not slow you down. They prevent a single bad day from undoing years of work.
Takeaways
Black swans expose fragility. The right response is design, not prediction.
In fat-tailed domains, the primary risk is ruin, not volatility.
Convexity is the practical goal: bounded downside with open-ended upside.
The venture power law is a reminder that outliers drive outcomes; structure your company to survive long enough to meet them.
Build resilience as operational muscle: routines, checklists, debriefs, and drills.
Use selective redundancy for anything that can end you.
Pursue antifragility through small, repeated stressors and fast learning loops.
Ask, continuously: “What assumptions must stay true for us to live?” Then shrink that list.
Sources
POLITICO — “The Incredible, World-Altering ‘Black Swan’ Events That Could Upend Life in 2025” https://www.politico.com/news/magazine/2025/01/03/15-unpredictable-scenarios-for-2025-00196309
Allianz Commercial — “Business Black Swans” https://commercial.allianz.com/news-and-insights/reports/business-black-swans.html
Harvard Business Review — “Building Organizational Resilience” (Suarez & Montes) https://hbr.org/2020/11/building-organizational-resilience
MIT Sloan Executive Education — “How to build organizational resilience” https://executive.mit.edu/How-to-build-organizational-resilience.html
CNBC — “VCs use this ‘power law’ to decide whether to invest in startups” https://www.cnbc.com/2025/07/21/vcs-use-this-power-law-to-identify-massive-winners-to-invest-in.html
Wikipedia — “Black swan theory” (definition summary and references) https://en.wikipedia.org/wiki/Black_swan_theory
Yahoo Finance — “'Black Swan' author Nassim Taleb says brace for software bankruptcies …” https://finance.yahoo.com/news/black-swan-author-nassim-taleb-162028755.html