When the System Needs a Hero

Good morning,

Let someone take a week off and watch what happens. Projects stall, people start asking where that person is, and the work that looked stable last Tuesday suddenly needs a phone check on Saturday.

I have seen that enough times to know the pattern. The same three people get pulled into every escalation. A fire gets put out and everyone moves on, then six months later the same fire is back. New hires wait because the process still lives in a head that is already in too many meetings.

Staying late felt like dedication. Being the one who knows the workaround felt like care. What it actually was is the operating system asking a person to be a load-bearing wall.

The cost is not the extra hour. It is strategy sliding to next quarter, context walking out if one person leaves, and hallway or after-meeting conversations carrying decisions the system cannot see.

The tells are ordinary:

The Same Three
They did not volunteer to become the single point of failure. Everyone else stopped asking questions and started going straight to them.

The Repeat Fire
The incident gets resolved, there is a sigh of relief, and six months later you are living it again because nobody kept the cause.

The Saturday Phone
They cannot disconnect, even when they are supposed to be off, because something breaks and the system still needs them to fix it.

The Fix: Stop building the week around heroes

Do not buy another platform to honor the people who are holding it together. Write how one heroic loop actually moves, name who owns it when that person is out, and put that where the team already looks. Your job this week is not more gratitude for the late nights. It is making one path that does not require a hero.

One thing you could do this morning...

Pick the person everyone says “just ask” about. Write one process they carry and where it should live if they are off Friday. Let the team use that path this week, and if it is slower than when they jump in, leave it.

Chet