Celebrating Your Org’s “Hero” Employee Is a Leadership Failure, Not a Culture Win.

There was a little spot up the road from the office where I worked in my early thirties. Late on a Friday, a few of us from the executive team would end up there, and somebody would get a drink bought for them.

Nobody ever said why. Everybody knew.

The drink went to whoever had won the week. The last email of the night. The last text. The Saturday reply. The Sunday reply. It was a contest none of us would have admitted we were running, and all of us were running it.

I'd love to tell you I was the wise one at the end of the table, quietly worried about sustainability. I was not. I wanted that drink.

I've thought about that table a lot in the years since. Not because anything dramatic happened there. Nothing did. It was a round of drinks between friends who were tired and proud of each other. But if you had asked me back then to describe our culture, I would have pointed to that table as proof of how healthy it was. We worked hard. We loved each other. We celebrated each other. What else is culture supposed to be?

It took me years to see what that drink was actually rewarding.

The best team I ever had

That team was the most gifted group of people I have ever worked with, and I still mean that. There were stretches where it felt like a sports movie, the kind where a ragtag group finds its rhythm and starts doing things nobody thought it could. Everybody had a superpower. Somehow we added up to more than the sum of our parts. We weren't one hero on a journey. We were all on it together.

In about 18 months, we went from serving 19 clients a year to serving more than a thousand.

Numbers like that do something to a team. They make every sacrifice feel justified. When you're serving more than fifty times as many people as you were a year and a half earlier, nobody stops to ask whether the pace is sustainable. Asking almost feels ungrateful. The results are right there, and the results say keep going.

So we kept going. Seven days a week, 365 days a year. We were teetering on full blown workaholism, and we wore it like a badge.

What we weren't doing was building systems. We were the system. Every bit of work ran through our hands, over and over again. From the outside, it looked like a well oiled machine. A team so tuned to each other that we could finish each other's sentences. From the inside, the whole thing ran on memory and late nights. Nothing was written down, because nothing had to be. We were always there.

You could feel it creaking. You could feel the seams fraying. We kept pushing anyway, because pushing was what got celebrated.

About two years in, one of us finally snapped and left.

It turned out the person who had made themselves irreplaceable was, in a lot of ways, actually irreplaceable. The work had been tuned to that person and to us as a team. Whoever came in next couldn't jump in fast enough, because there was nothing to jump into. No playbook. No process. Just a hole shaped like someone who wasn't there anymore.

Within a year, that work was producing half as much. The year after that, it was down 75 percent. More people left. New people came in. None of them could just slot in, because there was nothing to slot into.

In a culture like ours, the instinct when a hero leaves is to work even harder to fill the hole. It's the only move the culture knows. It's also the move that guarantees the next hero burns out too.

The belief nobody questions

Every nonprofit has a hero. The person answering texts at 9pm. The one who covered three roles during the last leadership gap and never complained. The one the Executive Director introduces at the gala with a little catch in her voice.

We give that person an award. We tell their story in the annual report. We buy them the drink.

And it feels exactly right. The nonprofit world runs on a quiet belief that sacrifice is the truest proof of commitment. We tell stories about founders who emptied their savings to keep the doors open, and about staff who drove across the state at midnight because a family needed them. Those stories are real, and some of them are beautiful. Over time, though, they teach us something we never meant to teach. They teach us that the way you show you care is by giving more of yourself than anyone could reasonably ask.

So when someone does exactly that, week after week, we celebrate them. It looks like the thing a mission driven culture is supposed to produce.

I want to say it plainly. That celebration is not a culture win. It is a leadership failure dressed up as gratitude.

What is a hero employee actually telling you?

My co founder Andy Graham said something on our podcast that I haven't been able to shake:

Sit with the last part. The process leaves with them.

Software engineers have a darkly funny name for this. They call it the bus factor: how many people on your team would have to get hit by a bus before a project grinds to a halt. A bus factor of one is the scariest number in the building. It means everything depends on a single person showing up tomorrow.

Most nonprofits have a bus factor of one in more places than they'd like to admit. And most of them have spent years celebrating the very person who makes it one.

Here's the mechanism, and once you see it, it's hard to unsee. When you celebrate the hero, you're telling everyone watching that being needed is the highest form of value in your organization. That being the person nobody else can replace is the prize.

So the one person whose knowledge would protect your mission if it were written down has every reason never to write it down. Documenting the work doesn't make them more valuable. It makes them replaceable. And you just showed the whole room that replaceable is not what gets the drink.

Andy has another line I love: documented doesn't mean rigid, it means someone besides you can run it. That's the whole point of a system. It isn't there to control your best people. It's there so your mission doesn't fall apart the week one of them gets sick, gets tired, or gets a better offer.

That is why this is a nonprofit leadership problem and not a personnel problem. Nobody on our team ever decided that late night emails were the measure of a person. We never voted on it. But we were the leaders, and leaders don't get to stand outside the culture and act surprised by it. What we celebrated became the job description. Our organization didn't stumble into having heroes. We manufactured them, and then we applauded.

The part of the story we skip

If you've ever read Joseph Campbell, you know the shape of the hero's journey. The hero leaves home, faces trials, wins something hard, and comes back. That last stage is the one everyone forgets, and it's the whole point. The hero returns carrying something that changes the village. Campbell called it the boon. The adventure only matters because it doesn't stay with the hero.

Our hero stories skip the return.

The hero in your organization goes out and wins the hard thing, over and over. But what they learned never comes home to the village. It stays in their head, their inbox, their muscle memory. Nobody else can do what they do, because nobody else was ever given what they know.

So when the hero leaves, the boon leaves too. The village is right where it was before the journey started, only now it's tired and short one person.

Why heart and skill aren't enough for a nonprofit leadership team

Here's what still gets me about that season. We weren't short on heart. We weren't short on skill. On paper, we had the exact combination every nonprofit leader is chasing.

In Built for Impact, we map teams on a simple matrix with passion on one axis and expertise on the other. High on both is the target, what we call Impact Culture. That's where we thought we lived. Honestly, for a while, we did.

But heart and skill with nothing underneath them don't stay put. When everything depends on a few people outworking each other, the skill stays and the heart drains out. That corner of the matrix has a name too: Burnover. It describes talented people who still know exactly how to do the job and no longer have anything left to do it with.

That's what a hero culture produces, eventually. Not a team of heroes. A team of very capable, very tired people, each one a single bus away from the whole thing stalling.

So who is your hero right now?

You probably already have a name in your head. Maybe it's a program director. Maybe it's your operations person. Maybe, if you're honest, it's you.

Ask yourself what happens the day they leave. Not if, when. What walks out the door with them? Which processes live only in their head? If they disappeared for a month, who would even know where to start?

Then look hard at what you celebrate, because your team is watching that more closely than anything you put on a values poster. The answer isn't to stop thanking people who work hard. It's to change what earns the applause.

Celebrate the person who wrote the process down so someone else could run it. Celebrate the person who trained their own replacement and then got promoted instead of stuck. Celebrate the team that hit its goal on a normal week, without anyone sending a single email after dinner. Celebrate the person who went home at five while the work still got done.

That's the hero worth having. The one who came back from the journey and handed the village everything they found. The one who made themselves a little less necessary.

I think about that Friday table differently now. The drink was never the problem. The question was who we bought it for.