Words I like: “The wind extinguishes a fragile candle and energizes an antifragile bonfire.” – Nassim Taleb
On March 31, 2026, at 4:23 AM, a routine software update at Anthropic accidentally bundled a debug file that exposed the entire source code of Claude Code, their $2.5 Billion flagship product. That same morning, a completely separate supply-chain attack injected malware into a code library that Claude Code depended on.
Within hours, competitors had a detailed blueprint of what took Anthropic years to build, and thousands of developers who updated that morning may have unknowingly installed a trojan.
Two crises. Same morning. Zero warning.
Most CEOs facing that morning would have reached for crisis plans. Most of their systems are not built to survive chaos but to perform in its absence.
Nassim Taleb called this the hidden fragility inside most “efficient” organizations.
Here’s how to see it, name it, and fix it.

1) Know Where You Stand
Every system falls into 1 of 3 categories:
- Fragile: breaks under stress
- Robust: survives unchanged
- Antifragile: gets stronger from stress.
Most CEOs think their company is robust, while it’s probably fragile. Just because it hasn’t been tested hard enough yet.
This naive optimization is the belief that the best systems are the most efficient, resilient, streamlined ones. It is the managerial equivalent of removing the spare tire from your car to save weight.
Your immune system isn’t resilient. It’s antifragile; it needs pathogens to grow stronger. Your bones respond to mechanical stress by becoming denser. Your muscles require small, controlled damage to develop. The organism that avoids all stress becomes fragile because nothing ever challenges it.
Which one are you most often:
- Fragile? Hates disorder. It has everything to lose and nothing to gain from volatility.
- Robust? Indifferent to disorder. It absorbs the shock and returns unchanged. Better than fragile, but not enough for a world accelerating toward unpredictability.
- Antifragile? Actively benefits from disorder. Like the Hydra, cut off one head, two grow back. It feeds on the storm.
Pro Tip: In your next leadership meeting, ask: “If our biggest assumption is wrong tomorrow, what breaks first?” That answer is your most fragile system.

2) Build Redundancy, Not Efficiency
Once you’ve identified your most fragile system, the instinct is to patch it. Tighten it. Make it more efficient. Don’t.
The power move is to redesign your system around it. Yes, you are trading efficiency for redundancy.
In the 2021 chip shortage crisis, Toyota kept building while GM scrambled, because it had been buffering inventory for years before. And during COVID, Amazon’s “inefficient” multi-carrier, multi-warehouse network absorbed a 186% surge in demand without breaking. Efficiency looks great on a spreadsheet.
But an antifragile system does something stranger and more powerful: it uses the shock to become better than it was before the shock arrived. “How do we design a system that the shock makes stronger?” is a principle to live by.
To understand how, you need a map. A map to build redundancy instead of useless efficiency.
Pro Tip: This week, list every critical process in your business that depends on one person, one vendor, or one system. Each item on that list is a fragility you need to redesign.

3) Let Small Things Fail On Purpose
Most CEOs treat failure like a fire to put out. Antifragile CEOs treat it like a vaccine: a small, controlled dose that builds immunity to the real thing.
Netflix understood this better than anyone. In 2011, after migrating their entire streaming platform to the cloud, their engineers faced a problem: with hundreds of interconnected services, any single server failure could cascade into a full outage for millions of viewers. Their solution was not to prevent failure. It was to cause it deliberately.
They built a tool called Chaos Monkey. It runs continuously within Netflix’s live production systems, randomly shutting down servers during business hours, forcing every engineer to design their services to survive such outages. If a service can’t handle a random termination, Chaos Monkey finds that weakness before a real crisis does.
The results speak for themselves. When Amazon Web Services rebooted 10% of its servers in October 2014, Netflix kept streaming while other companies scrambled. Their systems had already been “vaccinated” against that exact type of failure hundreds of times.
You don’t need to be a tech company to create your own Chaos Monkey. Simply allocate a failure budget.
Dedicate a small amount of time, money, or capacity each month to running controlled experiments designed to stress-test your assumptions. What happens if your top salesperson is unavailable for 7 days? What if your primary vendor misses a payment deadline? What if your biggest client leaves? Run the scenario before reality runs it for you.
The philosophy behind it is straightforward: if you aren’t breaking things on purpose, you’re letting them break by accident. And accidents don’t come with learning budgets or graceful recovery windows.
Pro Tip: Pick one critical process this month and simulate its failure. Take your best person off it for a week. Reroute your lead source. Delay a key deliverable intentionally. Document what breaks, what holds, and what you learn. Each Chaos Monkey experiment will reveal more about your company’s true resilience.

4) Decentralize Decision-Making
Small failures remain small only if the people closest to them have the authority to respond immediately. This is why centralization is the enemy of redundancy. It creates a single point of failure that can bring the whole organization down.
The people at the top are usually too far from the information to make a fast decision.
The economist Friedrich Hayek called this the knowledge problem: no central authority ever has all the information it would need to make perfect decisions, because most of the relevant knowledge is local, it lives in the heads of the people closest to the work.
At Amazon, they solve this with the “two-pizza rule.” If you need more than two pizzas to feed a meeting, the team is too large. Small teams create local authority, which means clear ownership and faster response.
At Malloy Industries, we use the RACI (Responsible + Accountable + Consulted + Informed) model to distribute responsibilities. With every new project, we reorganize roles so everyone knows their role, and decision-making authority stays with the one Accountable person instead of waiting for approval from Tina or me. We design our projects, so I’m only consulted, or ideally informed, about each project.

5) Barbell Strategy
Distributed decisions fix how you respond. But antifragility also requires how you bet.
Most CEOs seek the middle: moderate risk, moderate return, moderate exposure.
The barbell strategy does the opposite: combine two extremes. Keep 90% of your resources in safe, stable, reliable revenue. Deploy the remaining 10% in high-upside, low-cost experiments where the worst case is small and the best case is transformational.
This is how Amazon built AWS, now its most profitable division by margin. It began as an internal infrastructure project, an experiment born from Bezos’s frustration with his own engineering teams.
Netflix’s entire existence is a barbell story. DVD rental was the stable core. Streaming was the experimental bet. When streaming succeeded, it became the new core, and original content became the next bet. Each pivot preserved optionality by not killing the existing business before the new one was proven.
Before any major strategic commitment, ask: if this turns out to be wrong, can we recover? If the answer is no, you’ve installed fragility at the strategic level.
Pro Tip: Look at your last five major decisions and ask how many of them were reversible. That ratio tells you more about your organization’s resilience than any metric on your dashboard.
The Black Swan In The Room
That March 31st morning at Anthropic, the question was whether the system was built to feed on chaos or get destroyed by it.
The world is not becoming more predictable. Every signal points the other way: geopolitical instability, AI disruption, and supply chain madness. The next Black Swan isn’t a question of if but of when, and whether your system absorbs it or collapses under it.
Build in redundancy. Break small things before large ones break for you. Push decisions down to where the real knowledge lives. And keep your options open with the barbell strategy.
You don’t need to become indestructible. You need to build the kind of systems that the next shock makes stronger.
Be the fire.
P.S. Whenever you’re ready, here’s how we can help:
- If your business is one departure, one vendor failure, or one bad quarter away from a real problem, that’s not a strategy gap. It’s a systems gap. A Fractional COO can build the redundancy and decision-making structure your company needs to feed on chaos instead of collapsing under it. Talk to our Team to find out if we’re a fit.
- Not sure where your biggest fragility lives or how to build an antifragile business? That’s exactly what our free 30-minute Scalability Audit uncovers. In 30 minutes, we pinpoint your biggest constraint and show you how fractional leadership can fix it.
