Stop Saving the Day

Every organization has one. The person everyone calls first. The one who somehow ends up in every decision, every fire drill, every "quick question" that turns into a forty-minute meeting. Staff love this person. They also can't function without this person, which is a problem nobody calls a problem until that person takes a week off.

Being the hero feels good, and that's exactly the trap. You solve the problem nobody else would or could solve. Everyone thanks you. For about ten minutes you're necessary in a way that feels great. Call it the "Hero High." It's a real dopamine hit, and like most dopamine hits, it's a lot easier to get hooked on than to give up.

We worked with a leader who personally approved every decision, every supply order, and every schedule change in the building. She wasn't a control freak by nature. She just felt that she wanted to know everything that was going on in her team because she was accountable for it. By October she was answering email at 9 p.m., wondering out loud why her assistant principal still asked permission to reorder paper towels.

At a parish we worked with, the office manager's whole day was "quick questions." Can Father approve this. Can Father look at this. Does Father know about this yet. Father wasn't trying to run everything himself. He'd just never told anyone they were allowed to decide things without him, so nobody did. The bottleneck wasn't his ego. It was the absence of any other option.

None of this is a character flaw. It usually starts as a good instinct, showing up, solving the problem, being available, and quietly turns into something else. Being needed for every decision stops being leadership maturity and starts being operational dependency. The leader isn't developing the team anymore. The leader is rescuing it, one decision at a time, and calling the rescue "support."

You can usually tell where you stand by your inbox. If every message opens with "can we meet" or "quick question," if you own the agenda for every team meeting, if you're the one raising every issue and also the one solving it, you're not understaffed. You're the bottleneck. And you built it yourself, with the best of intentions.

Moving from hero culture to a process that runs without you comes down to three things.

Name it first. Before anything changes, you have to actually consider that the thing you've been calling support might be causing a dependency or accountability problem. That's the hard part, and it's the only part that requires courage instead of paperwork. Being needed for every decision isn't leadership maturity. It's dependency with better PR. Once you can say that out loud about your own team, the rest is just mechanics.

Let autonomy be uncomfortable on purpose. Someone else doing it differently, slower, or slightly worse than you would have is not a crisis. It's the cost of having a team instead of a one-person operation wearing a staff directory. Write down how you actually do the thing so people aren't guessing, demonstrate it and hand over the documentation, and let the first few attempts land at "close enough" instead of perfect. Close enough is the price of eventually not being needed for everything. You might even be surprised that they do it differently, in a better and faster way than you would have.

Make accountability do the work autonomy can't. Autonomy without accountability turns into chaos, and chaos is the actual nightmare hiding underneath all that hero behavior, not the loss of control. Build clear expectations, a regular feedback loop, and enough visibility that you know how things are going without personally running them. That's what makes it safe to let go in the first place.

You'll know it's working before anyone says so.

• Staff make decisions without checking first, because they know what they're allowed to decide and trust they won't get ambushed for getting it wrong.
• Meeting agendas stop being written by one person, because more than one person is actually responsible for moving things forward.
• "Quick question" messages get rarer over time, because the answers are written down somewhere instead of living only in one person's head.
• The leader can take a real week off, and the building doesn't hold its breath the whole time, because the system was never propped up by one person to begin with.

None of this happens in one conversation. It happens the first time you let someone else's decision stand, even though you may have made the call differently yourself. Remove the cape. Empower your team with systems and processes.

Jill Wollmer

Founder, Pax Ordo Advisors · June 2026