We built a system for a crisis that never came

Years ago, in my pharmaceutical software days, a client asked us to build a crisis management system. Not for everyday problems - for the serious, unexpected events. The kind every organisation hopes never happen.

The brief was clear. When a crisis hits, three things disappear first: time, overview and consistency. Everyone answers the phone, everyone improvises, and suddenly an organisation speaks with twenty different voices about the same event.

So we built for that moment. Early warning, so signals could be raised before they became emergencies. Pre-approved response templates, ready to go - so whoever answered, the answer was consistent. One place to coordinate, instead of twenty inboxes.

The system went live. And then nothing happened.

No crisis. Not while I worked with it. I remember finding that almost disappointing as an engineer - we’d built this capability, and it just sat there.

It took me years to realise I had it backwards.

A crisis management system that never activates isn’t a failed investment. It’s the best possible outcome. The value was never in the activation - it was in the readiness. If the worst happened, the first hour had already been thought through. Nobody would have to design the response while standing in the fire.

Since then, I’ve noticed how much of good engineering works this way: its success looks like waste. Backups nobody restores. Redundancy that never takes over. Emergency procedures nobody activates. Documentation nobody reads - until the one day someone urgently needs it.

And that’s the difficult part. Not building these things, but defending them - in budgets, sprint plans and board meetings - when their value is hardest to see precisely because nothing has gone wrong.

Some of the most important systems I’ve built never did anything.

That was the point.