Known Rot Problem

Leave a room unattended long enough and it doesn't stay neutral. It deteriorates. Dust settles. A single plant – given enough time and no one to prune it – will overtake the space entirely. We all understand this about physical spaces just look at any dystopian television series.

We don't apply it to companies.

Every organization I've worked in has had defects obvious to anyone looking clearly. Not hidden ones. Not subtle ones requiring investigation. Visible rot. The kind where you're three weeks in and already thinking: who designed this process? Or: why does that team report to that person?

The strange part isn't that the defects exist. The strange part is who sees them most clearly.

It is the people with the power to fix them.

Call it the Known Rot Problem: not that leaders go blind to what's broken, but that they see it clearly and don't move. I watched this happen at a company I joined as a senior leader. Within six weeks I could name three things limiting the organization. So could most of the people around me. I know this because I asked. Everyone had the same list. Nobody was doing anything about it. (God forbid the rot was inside your own team – or worse, your boss's. Then the list stayed very quiet indeed.)

When I pushed on why, the reasons were the same across the board.

Suggesting a fix meant owning the outcome. The person whose team was the problem had tenure, relationships, context you didn't have. And even when you did have standing, the act of naming something broken put you on the hook for two things: fixing it, and being wrong about it. The safest move was to let someone else go first.

So everyone waited.

A room left unattended doesn't need bad intentions to decay. It just needs inaction, which is almost always the rational short-term choice when the cost of acting falls on you alone. The question isn't whether your leaders are capable. The question is whether the conditions around them make action cheaper than inaction.

Most of the time, they don't.

Except the decay is never completely unchallenged. Every organization I have been in has had people fighting it – not from the top, but from the middle and the edges. They are the ones who catch the decision that would have cost three months to unwind, who hold the informal network together when the formal structure fails, who keep the list alive when everyone else has gone quiet. They often get called difficult. Too opinionated.

The problem is not their competence. It is their jurisdiction. They can slow the decay in the space they control. They cannot fix the conditions that produce it. That requires authority or influence they don't have – and so they absorb the cost of resistance without the power to resolve it. The organization quietly depends on them and quietly fails to protect them.

There is a real counter-argument here, and it deserves more than a dismissal. Forcing a fix without buy-in often creates a worse outcome: a team that complies without committing, resentment that outlasts the next reorg, an organization that treats every imposed change as temporary.

But there is a difference between building alignment and deferring without a limit. The leaders I've watched get stuck weren't the ones who wanted consensus. They were the ones who never set a threshold, no moment where they decided they had enough to move, and no moment where they decided to move anyway. The Known Rot sat on everyone's list. The list sat untouched. The room kept decaying while everyone refined their reasons for waiting.

Every organization I've described has a list. Most of them still have it. The leaders who cleared theirs didn't wait for better conditions or fuller alignment. They picked a point past which waiting became a choice they were no longer willing to make.

That is the only thing that separates them from the ones still waiting.