You Don't Have a Hero Problem. You Have a System That Needs One.
- Melody Hazen
- May 4
- 6 min read
Updated: 3 days ago
Corporate Munchausen Syndrome – the pattern where an organization unconsciously rewards rescue over prevention – isn't something your org talks about every day, but I bet you feel it.
A hero inevitably arrives to solve the crisis. That's not a coincidence. There's a pattern in organizations that nobody talks about because it doesn't look like a problem. It looks like a person who delivers.
It doesn't show up in engagement scores. It won't surface in a postmortem. And the person or team at the center of it is praised at town halls and in the next performance review.
And the consequences of it are costing you.
What it looks like
In this scenario, your org is mid-transformation. The IT modernization program has been running for eight months. The team has done the hard work – stakeholder alignment, architecture decisions, a phased migration plan that finally has executive buy-in.
Then there's “Marcus”.
Marcus has been in the room for every meeting. He's asked good questions, raised legitimate concerns, and pushed back consistently on the timeline, the vendor choice, the integration approach. His resistance never tips into obstruction. It's more like persistent, low-grade friction at every step.
The program stalls and the accumulated weight of unresolved concerns, re-opened decisions, and eroded momentum creates a crisis point. Now, a critical integration is at risk and leadership is watching.
Marcus steps in. He knows this system better than anyone (he's been here twelve years). He works the weekend. He finds the fix. The integration holds. The program moves forward.
Marcus gets the recognition. The program gets its win. And the dependency on Marcus and the pattern that produced the crisis continues untouched.
The critical distinction
Here's what makes this pattern difficult to address – Marcus isn't a saboteur. He's not manufacturing crises deliberately. He's not strategically withholding effort to maximize his moment. Likely, he's not conscious of the pattern at all. He has real concerns and his caution and rescue are genuine.
The hero isn't the problem. They're a symptom. The disease is what the org has been teaching people about what gets rewarded.
What's not genuine is the system's read of what just happened.
The organization experienced this as: problem, hero, resolution.
What actually happened was: accumulated friction, predictable crisis, localized fix that resolved nothing structurally.
The dependency didn't decrease. The reinvention didn't advance. The team that spent eight months building something better watched it get bypassed for a faster version of what already existed.
Why the system produces "heroes"
Organizations don't set out to create Corporate Munchausen patterns. They create them accidentally, through years of incentivizing the wrong moment in the problem lifecycle.
Think about what gets celebrated in your org. The launch that almost didn't happen. The client that almost walked. The system that almost went down. The story the org tells itself is always the same: crisis, intervention, resolution. The hero arrives just in time.
What doesn't get celebrated – or even seen – is the work that happened six months earlier. The architect who redesigned the system so it wouldn't fail. The program lead who had difficult conversations before it became a crisis. The team member who challenged a policy that hadn't been questioned in years, pushed through the uncomfortable decisions, and stayed on board through the ambiguity to build something that didn't need saving.
That work is hard in a specific way. It doesn't come with a clear win condition. There's no moment where the crisis resolves and everyone exhales. It requires people to challenge how things have always been done, bridge gaps between what policy says and what reality demands, and ask the questions that demand critical thinking.
The real win is invisible because nothing went wrong. People learn the behavior that gets noticed is rescue. The behavior that gets ignored is prevention.
Over time, the org selects for rescuers. It doesn't do this on purpose, but through a thousand small moments of recognition, attention, and reward that accumulate into a culture. The hero arrives after the crisis. That's not a coincidence. Your org taught it.
What it costs
The obvious cost is inefficiency. Reinvention programs take longer. Transformation initiatives stall and restart. Solutions that could have been elegant become duct-taped because the innovative version got too complicated to defend and the fast version saved the day.
The less visible cost is the tone it sets and what that tone tells your culture about what actually matters here.
The practitioners who say yes early, who commit to the reinvention, who do the unglamorous work of building something that doesn't break – they're watching. They see what gets championed. They see what's called out in the debrief. Over time, it is clear the org doesn't want what it says it wants. It says it wants transformation. It rewards rescue.
The talent drain this creates is subtle. The best architects and program leads don't quit loudly – they disengage, stop volunteering their best thinking, or leave for organizations where upstream work gets seen. Meanwhile, the dependency deepens.
The org becomes structurally reliant on its rescuers. Not because those people are indispensable. Because change is harder than rescue, and the system learned which one to choose.
The inefficiency is visible. The structural damage runs deeper. The real cost is to your operating model.
When rescue becomes the dominant pattern, you can't change how work gets done. Every reinvention initiative runs into the same ceiling and the people most invested in the new model keep getting bypassed by the people most fluent in the old one. The org says it's transforming. The operating model says otherwise.
This pattern is playing out in real time across AI implementation programs. Orgs that can’t move past piloting may not be failing because the technology is hard, but because the system keeps rewarding the teams who make the old way work again.
What to do about it
Performance management is not the answer. You won't fix it with a new competency framework or a values refresh. The pattern is structural, so the intervention has to be structural.
It starts with leadership. Specifically, the people who control what gets celebrated, resourced, and retold. The hero pattern persists because leaders allow it to.
Every time a rescue gets the spotlight and the upstream work goes unacknowledged, leadership is casting a vote for the culture they say they don't want.
The fix lives in the room where leaders decide whether to be transparent about why the shortcut was taken (not HR). Not just celebrating the win but naming the real trade-off. We chose the fast fix because we couldn't risk the client. We took the workaround because the budget didn't support the right answer this time. Those decisions aren't failures. Hidden, they become ones.
Next, you can:
Make prevention visible. If retrospectives only capture what went wrong and who fixed it, you're running a crisis ledger. Start auditing what didn't happen – the risks mitigated early, the decisions that held, the programs that didn't need a Marcus moment. Name those contributions explicitly, in the same rooms and with the same weight as the rescues.
Audit what your recognition signals. Pull the last twelve months of formal recognition in your organization – awards, shoutouts, performance narratives. What problem lifecycle moment do they predominantly celebrate?
Reward early commitment, not just “rescue” delivery. The team members who got on board in month one need to be as visible in the outcome narrative as the person who saved it in month eight. If they're not, it’ll be clear to your org exactly what gets valued.
None of this requires villainizing the heroes in your org. They are not the problem. The problem is the system that needed them to be the hero and never asked why.
Give it a name – and change it
Corporate Munchausen Syndrome persists because it looks like success. The crisis resolved. The program moved forward. The hero delivered.
What was actually built is an organization that needs crises to produce its best moments. One that can't see the work that happens before things go wrong. One that is unintentionally training its people in exactly the wrong lesson.
The question isn't whether you have a “Marcus”. You do. The question is what has your org been teaching everyone watching about what it takes to matter here.
The system is yours. So is the fix.
Comments