The Hero Trap is the pattern by which the leadership behaviors that made you successful at one scale become the thing constraining your organization at the next one.
The problem this solves
The paradox goes like this. The more problems you solve personally, the more dependent your company becomes on you. The more dependent it becomes, the more fragile it gets. And the more fragile it gets, the harder it becomes to stop being the one who solves everything.
If you have found yourself working harder as your team gets larger, if growth keeps demanding more of you rather than less, you are already in it.
The reason this is so hard to see is that it feels like success. The company is performing. People value you. Nobody in the building is telling you to stop. (More common than a lot of us want to admit.)
How the trap works
You built the pattern because it worked. In the early days you did know more than anyone else. Your judgment was better than the alternatives. Being the center was efficiency, not ego.
Then the company grew. You cannot possibly know everything happening across it now. Other people have expertise you lack. The information needed for good decisions lives in dozens of heads rather than one. And the pattern persists anyway, because it is familiar and because the organization has been designed around it. People learned to wait. Systems route decisions upward. Your judgment became the standard everything else gets measured against.
The trap operates through four mechanisms.
Decision bottlenecks. Decisions queue for your attention. The company moves only as fast as you can process, so choices that could take days take weeks while competing for the same scarce resource.
Capability atrophy. When people defer to your judgment, they stop exercising their own. Over time the organization becomes less able to function without you, and not because the people are less talented. They have been trained out of using their talent.
Information filtering. Information traveling toward a central decision-maker gets softened at every step. Bad news gets rounded down. Uncertainty gets hidden. What reaches you may bear limited resemblance to what is happening.
Succession fragility. When the company is designed around one specific person, handing it over destabilizes it. The next leader either tries to replicate you, which they cannot do because they are not you, or redesigns the whole system, which is disruptive and risky.
Here is the part that stings. The hero does not only fail to manage complexity. The hero generates it. Every fix that bypassed the normal process, every exception approved because it was faster, every decision made because explaining it would have taken too long. Each one created a dependency only you can manage, and nobody documented it because it lives in your head.
Why this is harder now than it was for the generation before
Three forces have converged, and they compound each other.
Success patterns working against you. Your education taught you to be the smartest person in the room. Your early career rewarded you for solving what others could not. Individual capacity grows in a straight line. Organizational complexity does not.
BANI conditions. Futurist Jamais Cascio describes the current environment as Brittle, Anxious, Nonlinear, and Incomprehensible, replacing the older VUCA language. Planning and control were the right training for a world where change arrived quarterly. Change arrives daily now, and it calls for sensing and adapting rather than forecasting.
Systems complexity explosion. Five people have ten possible relationships. Fifty people have 1,225. Every new tool, process, or partner multiplies the combinations. Consider what a single customer complaint sets off now compared to a generation ago. One call to one person checking one system has become social monitoring, ticket triage, a chargeback dispute, a sentiment alert, an account health score, and a renewal risk flag. One complaint, a dozen systems, eight teams, dozens of places it can break.
Success patterns make you resist change exactly when BANI conditions demand it. Complexity overwhelms individual capacity exactly when the old approach hits its ceiling. And every heroic save that works reinforces the pattern keeping you stuck.
Working harder does not get you out. That is trying to outrun a flood by running faster.
How to tell if you are in it
Five questions:
- When problems arise, do people bring them to you automatically?
- Do you feel most valuable when you are solving something urgent yourself?
- Are you busier than you were six months ago, despite the team being bigger?
- Do problems you have already solved keep coming back?
- If you were unreachable for a week, would things slow down noticeably?
Three or more yeses and you are in it. That is not a character verdict. It is a description of how your organization is currently designed.
I worked with a leader for five years who knew all of this already.
He had read the books. He could use the words. In a calm quarter he was as thoughtful about this as anyone I have advised. And then pressure would hit, financial or otherwise, and he would take over. Not gradually. He would just be running things again, making the calls, and everyone around him would step back into place because they knew the pattern too.
His senior leadership team had eight or nine seats. Over those five years, thirteen people moved through them. When I left, three of the original group were still there.
He is a good man and it is a good business. Awareness was not the problem. He could see it happening while it happened.
I could not help him stop. That one still bothers me.
What people get wrong about this
It is not a competence problem. Nothing here says you are bad at your job. The opposite, usually. The trap only catches people whose personal capability was good enough to build something on. That is what makes it so hard to argue yourself out of.
Working harder is the wrong lever, and so is caring less. The way out is not becoming a better hero and it is not disengagement. It is redesigning what routes to you in the first place.
The forces are not only a threat. The same complexity that breaks a leader trying to hold it all in their head becomes an advantage once you design systems that navigate it without you. The company that builds those systems handles what its competitors cannot, and not because its people are smarter. Its architecture is better.
Getting out takes longer than reading about it. Understanding the pattern and having released it are different things, and the gap between them is usually measured in quarters. Easier said than done.
The way out
The exit is an identity shift, from solving problems personally to designing systems that solve them. That progression runs Controller, Builder, Architect, and it is the subject of a companion piece here.
The short version: Controller says “I solve.” Builder says “I show how I solve.” Architect says “I design systems that solve.” The goal is not abandoning Controller. It is being able to choose.
Design beats default.
Where to go next
Start with the assessment. Five questions, two minutes, free. It surfaces which identity you default to when pressure hits, which is usually not the one you would have guessed. Take the Hero Trap Assessment
If you already know the answer and want to talk about what to do next, I work with CEOs and leadership teams on growth that does not depend on any one person. Get in touch
The Hero Trap is the subject of The Hero Trap (Berrett-Koehler, October 2026), the first book in the Performance Operating System series.
Bill Flynn is the founder of Catalyst Growth Advisors and a member of Marshall Goldsmith’s 100 Coaches.