Of Course It Went Wrong

Category: Framing the whole Why these failures feel surprising but are rarely accidental.

---

Sit in enough post-mortems and you start to notice the same sentence, said in the same tired voice, by different people in different rooms about completely unrelated disasters.

“In hindsight, it was obvious.”

It is said about the project that overran by a year, the product nobody bought, the talented person who quit without warning, the outage that took down everything at once, the merger that destroyed more value than it created. Different industries, different decades, different scales — and the same shrug at the end. It was obvious. We should have seen it coming. Of course it went wrong.

Here is the thing that sentence is quietly admitting. If it was obvious in hindsight, then the information was there in foresight too. Nothing arrived from outside. No new fact appeared at the end that wasn’t available, somewhere, to someone, at the start. The failure was legible the whole time. People simply could not read it while it was happening, and could read it perfectly the moment it was over.

This book is about why that happens, and why it keeps happening, and why it will happen to you and the things you build no matter how clever or careful you are — unless you understand the machinery underneath it.

---

The claim this book is making

The claim is simple to state and uncomfortable to sit with: most organisational and human failures are not accidents. They are the predictable output of systems behaving exactly as they were built to behave.

That is a deliberately strong way to put it, so let me be precise about what I mean and what I don’t.

I do not mean that every disaster was foreseeable in its specifics. You could not have predicted the exact week, the exact trigger, the exact person who finally snapped or the exact server that finally fell over. Specifics are genuinely unpredictable; the world has too many moving parts.

I mean something narrower and far more useful. I mean that the conditions for the failure were not hidden. The pressures that produced it were structural, recurring, and visible to anyone who knew where to look. The trigger was random. The vulnerability was not. And the vulnerability is almost always the same small set of patterns, wearing different clothes, showing up again and again across organisations that have never met each other and would swear they have nothing in common.

When you can see the patterns, “of course it went wrong” stops being a shrug of resignation and becomes something much more like a diagnosis. The same three words, said two completely different ways. One is the sound of a person who has given up explaining. The other is the sound of a person who has finally understood. This book is an attempt to move you from the first to the second.

Why the failures feel like surprises

If the patterns are so visible, why does nobody see them coming? Because seeing them requires standing outside the system, and almost nobody gets to stand outside the system while they are inside it living their day.

Three things conspire to keep the patterns hidden in real time.

The cost is always paid later, and somewhere else. The decisions that cause failures are nearly always rational, defensible, even admirable on the day they are made. Deferring the awkward conversation is kind. Adding the extra check is prudent. Hitting the number this quarter is responsible. Each choice is locally sensible. The damage only appears when dozens of locally sensible choices accumulate into a globally insane situation — and by then the choices are long in the past, owned by no one in particular, and impossible to point at. The cause is distributed across time and people. The effect arrives all at once. Our minds are very good at connecting a single cause to a single effect, and very bad at connecting a slow drizzle of small causes to a sudden flood.

The system keeps working right up until it doesn’t. Most of the patterns in this book do their damage quietly. Trust decays without an alarm going off. Complexity grows without anyone deciding to add it. Prudence curdles into paralysis one cautious meeting at a time. Nothing breaks, so nothing looks broken. A system under accumulating internal stress and a system that is genuinely healthy look identical from the outside — they both function — right up until the moment they don’t. The absence of a visible problem is mistaken for the presence of health, which is exactly the mistake that lets the real problem grow undisturbed.

Everyone is too close, and too implicated. The people best placed to spot a pattern are usually the people standing inside it, shaped by the same incentives that produced it, often having made some of the small sensible decisions themselves. You cannot easily see the water you are swimming in, and you really cannot see it if pointing at the water would mean admitting your own hand helped pour it. So the patterns survive not because people are stupid — the people in these stories are usually clever, diligent, and well-meaning — but because the structure they are in makes the patterns nearly invisible from the inside and nearly irresistible to enact.

Put those three together and you get the central illusion this book exists to dismantle: that failures are anomalies. They are not anomalies. They are the baseline. They are what systems do when left to run on their default settings. The genuine anomaly — the thing that actually requires explanation — is when something goes right and keeps going right, which is a rare enough event that it gets its own companion book.

How to read what follows

The chapters after this one are not a story with a beginning and an end. They are a field guide. Each one isolates a single pattern — a specific, recurring way that organisations and the people in them defeat themselves — and takes it apart the same way every time, so you can learn to recognise it in the wild.

Each chapter opens with a short story, because patterns are easier to feel than to define. Then it states the principle plainly. Then it does the part that matters most: it explains why the pattern is inevitable — why it isn’t a sign that someone was lazy or stupid, but the natural result of ordinary people responding sensibly to the situation they are in. It shows you how the pattern looks when it is actually happening, so you can spot the early signs rather than only the wreckage. It explains why it causes damage and why that damage is so often misread. And then it offers ways to counter it — not cures, because there are no cures for these, but the kind of structural countermeasures that tilt the odds. It closes by describing what good looks like, and with a question worth sitting with.

A few honest warnings about how to use it.

There are no villains here. It is tempting, reading about failure, to go looking for the idiot or the bad actor who caused it. Resist that. The whole point of this book is that the failures happen without villains — that good, smart, careful people produce bad outcomes when the structure pushes them to. If your takeaway from any chapter is “I would never be that stupid,” you have read it backwards. The correct takeaway is “I can see exactly how I would have done the same.”

You will recognise yourself, and that’s the point. Some of these chapters will sting, because you will see a decision you are making right now, or a pattern your team is living inside, described in print. That recognition is the whole value of the book. The patterns only become manageable once you can name them, and you can only name them once you have felt the small jolt of seeing your own situation written down by someone who has never met you.

Naming a pattern is not the same as escaping it. Understanding why delay has a bias does not make you immune to delaying. These forces are not defeated by being understood; they are merely made visible. But visible is an enormous improvement on invisible. A pattern you can see is one you can argue with, design against, and catch a little earlier each time. That is the realistic prize on offer here — not perfection, but earlier sight.

Why “of course”

I kept the phrase in the title because it carries the exact double meaning the book is about.

Said one way — flat, exhausted, after the fact — “of course it went wrong” is the most defeated sentence in working life. It means: these things always go wrong, nothing could have been done, what did you expect. It is the sound of learned helplessness dressed up as worldliness.

Said the other way — alert, curious, slightly ahead of the event — the very same phrase becomes a kind of superpower. Of course it went wrong: given those incentives, that structure, that silence, that pressure, this outcome was always sitting there waiting. Once you can say it in this second voice, you are no longer surprised by failure, which means you are no longer paralysed by it, which means you can start to do something about it before it arrives rather than only explaining it afterwards.

The failures in this book are predictable. That sounds like bad news, and in a way it is — it means they are coming, for you, in some form, whatever you do. But predictable is also the most hopeful word available, because the only things you can prepare for are the things you can predict. Random misfortune you can only endure. Patterned failure you can see coming, name, and meet.

That is the entire bet of this book: that naming the patterns is the first and largest step toward not being quietly governed by them. Everything after this chapter is the patterns themselves.

So — of course it went wrong. Let’s find out exactly why, so that next time you can say it the other way.

A Reflective Question

Think of the last failure you watched up close — a project, a relationship, a decision that aged badly. If you are honest, on which day did the information that would have predicted it first become available to someone — and what was it about the situation that made that information impossible to act on at the time?