← All thoughts

Real-World Lessons · Customer Experience · Antifragile Design

A storm hit San Antonio earlier this year.

A storm hit San Antonio earlier this year.

Hundreds of thousands of customers lost power. Some waited days. This week the utility sat down and asked what broke.

That meeting is the work. Not the press statement. The work.

A company is an operating system. People. Cash. Customers. Suppliers. Process. Weather is not a special case. Weather is the test the system was always going to get.

The first lesson is not “buy more trucks.” It is via negativa. Remove what fails you under load. A circuit that opens and stays open. A restoration list that treats every outage as equal when some homes have no water and no air. A plan that assumes your own crews will always be enough. Those are the parts to cut.

Skin in the game is simple here. The people who design the restoration sequence should live with the same outage clock as the customer on the West Side. If the map is wrong, they feel it. If the message is late, they feel it. Distance from the consequence is how fragile systems stay polite and stay weak.

Modular beats one block. The grid is not one machine. It is many small pieces that should fail in isolation and come back in isolation. Equipment that can close a circuit again after a hit is that idea in hardware. Mutual aid is that idea in people. You do not build one giant crew that only exists for the worst day. You keep a safe core and you keep the right to call in small, trained units when the load spikes.

Customers before extra capacity. Extra generation that does not reach a dark house is inventory, not service. The purpose of the system is a working light, a working fridge, a working pump. Everything else is a means. If cash and headcount are going into yesterday’s projects while the last miles stay brittle, abandon those projects on purpose. Planned abandonment is how you free people and money for the work that still creates a customer under stress.

A system designed for volatility does not hope the next storm is smaller. It uses this one. It records what surprised it. It removes the single points. It keeps the core cheap and reliable. It places small bets on better field data, better neighborhood contact, better mutual aid. Then it waits for the next hit — and gets stronger because the last one was not wasted.

Today we're facing another large storm - let's see how the lessons were learned.

Originally posted on LinkedIn.
View the original post ↗

Share on LinkedIn
The book

Designed for Volatility

How Leaders Build Companies That Improve Through Disruption

Get the book
Fragility Diagnostic

See the fragility before the operating review pretends it is a surprise.

A written report on hidden fragility.

Take the Fragility Diagnostic