Stop Hardening IT. Start Designing the Company.

Everyone is talking about AI in the technology stack. But AI is not the real starting point. The company is.

An antifragile company is not the one with the newest model. It is the one that gets stronger when demand spikes, a supplier fails, a rate shock hits, or a key employee leaves.

Those shocks do not arrive in the data center first. They arrive in pricing, inventory, customers, operations, and people.

In our upcoming book, Designed for Volatility, we argue that the work starts by removing what makes the company fragile before adding what makes it more sophisticated.

Skin in the game. The people making decisions should share in the consequences. Give local teams real authority, clear accountability, and the ability to stop a bad process before it spreads. Surface the problem early, before it becomes a larger failure.

Small units, not one giant system. Design the company so that one team, process, or business unit can fail without bringing down everything around it. A contained failure gives you information. A tightly coupled enterprise can turn one failure into many.

Protect the core. Experiment at the edges. Protect what must not fail—cash, trusted customers, critical operations, and compliance. At the same time, create small experiments that can grow when they work. Don't give every decision the same level of risk.

Turn disruption into opportunity. A company is designed for volatility when disruption creates opportunities it could not have captured on a calm day: a supplier that can reroute, a branch that becomes the hub, a team that absorbs the overflow and keeps the customer relationship.

Planned abandonment. Every quarter, kill a process, product, or meeting that survives simply because it is familiar. Fragility often hides in the things an organization refuses to stop doing.

IT can help. It cannot substitute for these choices.

If your key employees cannot halt a bad process, if incentives punish the person who surfaces the problem, or if flexibility disappears in the name of efficiency, you may have a polished company that is still fragile.

Don't build a company that merely survives the next shock. Build one that is better because it happened.