In The Room #31 – Every time you rescue a broken system, you hide the evidence it's broken.

In the room recently, a manager noticed something drifting toward failure. Not hers to fix, no clear owner nearby, and her instinct, the one that's made her reliable for years, was to step in and catch it. This time she didn't. She found out who actually owned it, told them what she'd seen, said when she'd step in if it still wasn't handled, and went home.

That's a small moment. It's also the exception. Most of the time, the most capable person in the room becomes the default owner of anything ambiguous, not because anyone assigned it to them, but because stepping in feels safer than watching it wobble. I've watched the same instinct show up in a completely different environment, different industry, same pattern. Competence quietly attracts ownership, until the system learns it doesn't need to sort out who's actually responsible, because someone capable will always catch it.

The part that's easy to miss

Here's the part that's easy to miss: every time you catch a failing system before anyone notices, you also hide the evidence that it was failing. Nobody finds out the ownership was unclear. Nobody discovers the process was broken. Nobody learns that someone else wasn't stepping up, because they never had to.

I've started calling this the False Calm Effect. A team can look functional, deadlines get met, nobody's complaining, and none of it tells you whether the system actually works, or whether one or two capable people are quietly absorbing everything that would otherwise prove it doesn't. False calm isn't the absence of a problem. It's the absence of evidence, because the evidence is being caught before anyone sees it.

This isn't a new problem, it's just rarely discussed outside safety and quality work. If someone keeps intervening before a fault gets the chance to show itself, nobody ever gets a true signal of where the system actually breaks.

This isn't permission to let things fail

To be clear, this isn't permission to let things fail. Before you step back from something, ask two things. Is this genuinely recoverable if it goes wrong, a missed deadline, some rework, an uncomfortable conversation, not anything safety-critical, contractual or client-facing? And will stepping back actually tell you something, who should have owned it, or will it just break with no one learning anything? If either answer is no, catch it. This only works where the cost is small and the lesson is real.

A tool for the moment you're tempted to step in

I've built those questions out into a short tool, the Rescue Reflex Check, to run through before you step in next time. It walks through ownership, role, consequence, capability, what gets lost if you rescue it, and what else you're choosing not to do instead, then asks one final, sharper question: if you disappeared for a month, who would have to own this?

Comment "RESCUE" to this week's post if you'd rather have it sent directly.

Enjoyed this? Get In The Room each week.
One leadership observation. Two minutes. Once a week.
Subscribe →