Insight

Nobody Thanks You for the Escalation That Didn't Happen

Organizations are extremely good at noticing rescue and almost incapable of noticing prevention.

The person who works through a weekend to recover a failing launch is visible, thanked, and occasionally promoted. The person whose boundary was drawn well enough that the launch never wobbled has produced nothing anyone can point at. Their reward is that nothing happened, which is indistinguishable from having had an easy quarter.

I have watched this play out often enough to think it is structural rather than cultural. It is not that leaders prefer heroics. It is that heroics are events and conditions are not, and organizations run on events — they are what fills a status report, a retrospective, a recognition award.

The consequence is quiet and expensive. Cultivating conditions is slower than intervening, and it pays out in absences: a meeting that stops being scheduled, a decision that no longer travels, a wait nobody experiences because it never forms. All of that is capacity returned to creating value, and none of it will appear on a slide.

So an organization that celebrates rescue will, over time, produce more situations requiring rescue. Not because anyone engineers them. Because the people who prevent them learn what gets noticed, and reasonable people spend their effort where it is seen.

The correction is not a new award category. It is keeping a private list of the things that stopped happening, and reading it before deciding whether a quarter of structural work achieved anything.

An organization capable of valuing an absence has already solved most of what this paper describes. Very few are, and it is worth being honest that this is the hardest thing in it to actually do.