The Concrete Knew What to Do Next: resilient business systems

For a long time, researchers thought the small white chunks inside ancient Roman concrete were there because it hadn’t been mixed properly. That made sense. If concrete looks uneven, you assume somebody messed it up.

But those chunks may have been there on purpose and this relates to resilient business systems.

Researchers at MIT found evidence that the Romans used a process called hot mixing. The white pieces are lime. When the concrete cracks and water gets in, the lime reacts with it. Calcium moves into the damaged area, hardens, and helps fill the crack. It doesn’t make the concrete indestructible. A wall can’t rebuild itself after half of it falls down. But with smaller cracks, part of the repair is already inside the material.

The concrete knows what to do next.

We spend a lot of time trying to build a business or system that never cracks. We make rules, create processes, and buy tools that are supposed to keep everything running the way we planned.

There’s nothing wrong with that. Preventing a problem is usually easier than fixing one.

Still, something always happens.

Someone leaves. A tool stops working. A step gets missed. The person who understands the process isn’t available. The week gets busy, and the normal routine falls apart. Most systems work when everything goes right. That isn’t much of a test. The real test is what happens next.

Does everyone stop and try to figure out who knows what? Does a small issue sit unnoticed until it becomes a large one? Does the whole thing depend on one person remembering how it works? Or is there already some kind of repair built in?

That might mean someone else knows the job. There might be extra time in the schedule, money set aside, or a backup that’s ready to use. Maybe the problem becomes visible early enough that it can be fixed before it spreads.

All of that can look unnecessary when things are going well. That’s why it’s usually the first thing to get removed.

We tend to confuse strength with rigidity. We think a strong system should never move, change, or fall behind.

But something that can’t bend usually doesn’t handle pressure very well.

A durable system isn’t one that never has problems. It’s one that can take a hit without turning every problem into an emergency. Somebody can step in. The routine can restart. The missing information can be found. There’s a way back.

Roman concrete still cracked. Water still got inside. Time still worked against it. It lasted because the crack didn’t automatically become the end of the structure. Part of the repair was already there.If your system only works when everything goes right, it doesn’t really work yet. It just hasn’t been tested.

FAQ section

What makes a business system resilient?

A resilient system can keep functioning when a person, tool, or normal process becomes unavailable. It has backups, shared knowledge, enough margin to absorb a problem, and a clear way to restart.

Why do strong systems need backups?

Backups can look unnecessary when everything is working. Their value appears when something breaks. They stop one failure from turning into a much larger interruption.

Can every business problem be prevented?

No. Good planning can prevent many avoidable problems, but every system eventually gets tested. The more useful goal is to catch problems early and have a response ready.