Prevention Is Thankless

Category: Incentives, metrics, and consequences Success often looks like nothing happened at all.

As the year 2000 approached, an enormous amount of work went into the so-called millennium bug. Systems that stored years as two digits were checked, patched, and tested at great expense — across banks, utilities, airlines, and governments. It was tedious, unglamorous work, and it largely succeeded.

When the date rolled over, almost nothing happened. Planes did not fall. The power stayed on. And within weeks a new story took hold: it had all been hype, a panic, money wasted on a problem that was never real.

The people who had spent two years preventing the disaster were now, in the public mind, the people who had cried wolf. The very absence of catastrophe — the thing they had worked for — was taken as proof that there had never been a danger. Had they done nothing and watched systems fail, they would have been blamed. Having done the work and produced a quiet, uneventful midnight, they were blamed anyway, for a different reason. There was no version of success that looked like success.

This is the signature of prevention. When it works, it produces nothing to see — and the same trap repeats wherever prevention lives. Take public health. A vaccination programme drives a disease down toward nothing. A generation grows up never seeing the illness, never burying a child from it, never sitting in a ward full of it. And out of that very success grows a quiet doubt: if nobody around here gets the disease, why are we still vaccinating against it? The protection becomes invisible precisely because it is working, and its invisibility becomes the argument for withdrawing it. Uptake softens, the buffer thins, and eventually — sometimes decades later — the disease returns to a population that had forgotten why it was ever afraid. The programme did not fail. It succeeded so completely that people stopped believing it was needed, which is the most thankless outcome of all: punished not despite working, but because of it.

The Principle

Prevention succeeds by making sure nothing happens — and “nothing happened” is invisible, unprovable, and easy to dismiss as having been unnecessary all along.

A disaster that occurs is concrete, attributable, and rewarded with attention and resources. A disaster that is prevented is a non-event. You cannot point to it, count it, or take a photograph of it. So the work that produced it competes, badly, against work that produces something you can see.

Why It Is Inevitable

We reward what we can observe, and prevention’s entire output is the absence of an event. There is no clean counterfactual: you can never prove what would have happened, so the preventer can never fully demonstrate their value. “Nothing went wrong” is indistinguishable, to an outside observer, from “there was never any risk.”

The incentives compound this. The person who visibly rescues a situation is celebrated; the person who quietly ensured the situation never arose is at best ignored and at worst suspected of having invented the threat to justify the budget. Over time, rational people learn the lesson: it is safer to be seen solving visible problems than to prevent invisible ones. Prevention gets starved precisely because it worked.

How It Shows Up

• The maintenance budget is the first thing cut, because nothing has gone wrong lately.
• Visible recovery — the all-nighter, the dramatic save — is praised more than the quiet competence that made the save unnecessary.
• After a long stretch of stability, the people responsible for that stability are seen as overstaffed or over-cautious.
• “We’ve never had a problem with that” used as the argument to stop doing the thing that prevented the problem.
• A protection works so well that the threat it guards against is forgotten — and the forgetting becomes the case for withdrawing the protection.
• Funding flows toward whatever failed most recently and loudly.

Why It Causes Damage

The damage is delayed and then sudden. When prevention is defunded because it succeeded, the protection quietly erodes — and because erosion is also invisible, no one notices until the thing it was preventing finally happens. At that point the failure is loud, expensive, and blamed on bad luck or unforeseeable circumstances, rather than on the slow withdrawal of the prevention that had been working all along.

This sets up a destructive cycle: prevention works, gets cut for being unnecessary, the disaster returns, money pours into dramatic recovery, the recovery is rewarded, and the cheap quiet work that would have stopped it is never rebuilt. The organisation pays full price for a lesson it already knew.

How To Counter It

The counters are mostly about making the invisible visible on purpose, and they are observable practices, not good intentions — you can walk into an organisation and check whether they are happening.

• Count and report prevented incidents and near-misses as wins, in their own line. A function that only ever reports failures is structurally invisible when it succeeds. Look for whether “what we stopped this quarter” appears anywhere in the reporting — if it doesn’t, prevention is already going unseen.
• Ask, before every cut justified by calm, whether the calm is the product of the spending. Make it a standing question, not an instinct. “Nothing has gone wrong with X lately” should trigger “is that because of what we spend on X?” — out loud, on the record, every time.
• Name a counterfactual owner. Someone whose job is to articulate what would happen if a given protection stopped, and to keep saying it during the long quiet when no one wants to hear it. Prevention has no natural advocate, because it has no incident to point to; give it one deliberately.
• Tell the story of the prevented disaster even though it has no dramatic ending — especially because it has no dramatic ending. Stability that is never narrated is stability that looks free.
• Treat a long calm followed by confidence that the calm was free as a warning sign in itself. The moment people start asking why you still pay for the thing that has kept them safe is the moment the protection is most at risk — and most needed.

What Good Looks Like

Organisations that can tell the difference between “this risk never existed” and “this risk was managed so well it became invisible” — and resource the second accordingly. Where prevented incidents are counted and reported, where someone is paid to keep the counterfactual alive through the quiet years, and where every cut justified by calm has to first answer whether the calm was bought. Where the people who keep the lights on are not punished for the fact that the lights stayed on.

The strongest signal that prevention is working is that there is nothing to report. The mistake — and it is the whole mistake — is reading nothing-to-report as nothing-to-do.

A Reflective Question

What in your organisation has run smoothly for so long that people have started to wonder why you still pay for it — and what would happen, and how loudly, the day you stopped?