What’s really happening when the entire operation depends on what’s in your head—or your hero’s
There’s a phrase I hear a lot, always said half-jokingly, half-seriously, with that instantly recognizable mix of pride and exhaustion: “Without me, nothing gets done around here” or “As usual, I’m the one who has to sort out another problem, even though it’s not my job.”
And the worst part is that it’s usually true. Ask anyone at any company or on any post-sales team, and there will always be that person. That person knows why a customer made a particular request in a particular way, what they were promised during the sale, what breaks if you change a setting, and who needs to be notified when the usual thing happens. None of that is written down anywhere; it’s in their head, and the company runs because that head is available and everyone trusts it.
If you’ve read this far and recognized yourself, or someone on your team, this article is for you.
The cost the company doesn’t pay, but the employee does
You get a call on Friday afternoon because a customer is worried and you’re the only person who knows how to answer their question.
You get a message while you’re on vacation with that familiar opener: “Sorry to bother you, it’s just one quick thing.” And of course you reply, because you know perfectly well that if you don’t, the problem will grow. By the time you get back, it’ll be three times bigger, the customer will be angry, and someone internally will have improvised an answer they shouldn’t have given.
And you’re the last to shut down your computer, not because you still have your own work to do, but because you’ve spent all day solving everyone else’s problems and only started yours at four in the afternoon.
When you reach this point, you become a hero. But rather than repeat what people tend to say at work or in your personal life—“be careful,” “this isn’t sustainable,” “watch out for burnout”—today I want to offer another way to get off the hamster wheel.
The cost nobody told you about: your career
This other perspective hurts. You may learn it over time, but I’m bringing it to you today so you can do something about it:
The cost of being indispensable isn’t measured in lost Fridays; it’s measured in the roles you never reach.
The mechanics are simple, even if they’re hard to see when you’re busy putting out fires: for you to be promoted, someone has to be able to take over your role. That’s it. And if your role consists of being the only person who knows how things work, there’s no one who can take it over, so you stay where you are.
The difficult part is that no one will tell you that in so many words. Instead, during your review, with the best intentions in the world, they’ll say something that sounds like praise: “Right now, we can’t afford to move you out of that role.” And you leave that meeting thinking they’ve told you how good you are, that your job is secure and that they value your work.
But what about the promotion? What about the raise?While you get praise, the promotion goes to someone else who doesn’t work harder than you or do a better job, but whose work can be handed over or who has room to take on other responsibilities.
Something similar happens with pay, though it’s less obvious. You might get a performance raise because you solve a lot of problems and adapt to every policy change, every new CRM, and every process someone comes up with. But you’re doing the same thing you were doing six, twelve, and eighteen months ago, just with a heavier workload, and that doesn’t look like growth. You get the raise given to someone who meets expectations, not the one given to someone who has taken the next step.
And if you’re a CSM or CS Lead, it seems even more absurd, because your real value lies in your judgment: reading an account, seeing a cancellation coming three months ahead, knowing when a customer is ready to grow and when it’s better to say nothing.
But your judgment isn’t visible unless you put it in front of someone. It shows in an analysis of why accounts in a particular segment are churning, in a proposal for how renewals should be managed, or in a meeting where you persuade a customer to change a decision. And all of that takes uninterrupted hours and a clear head—exactly what you don’t have when your day disappears into solving everyone else’s problems.
So look at the cycle: people get promoted because they’re already doing the work of the next role, and you never get to do it because you’re busy holding your current one together.
And the cruelest part: the better you hold it together, the fewer reasons anyone has to move you out of it.
And let’s be clear, because this is easy to misunderstand: no one decided one day that you should be the bottleneck. It built up over time. You solved what needed solving and took ownership of it, and because it worked, no one had a reason to stop and examine it. What is up to you is whether you keep sustaining this situation.
Why documentation projects never get finished
And here’s something you’ve probably already experienced, so let’s put it on the table: documentation.
At some point, someone—usually in management—says you need to document the processes so things no longer depend on individuals, that everything needs to be written down to help the company scale and avoid “getting tangled up in the same things over and over.” And you’re involved.
In other words, they’re asking you to spend hours you don’t have writing down, in detail, the very knowledge that makes you necessary, without offering you anything in return. So progress is slow, the work stays half-finished, there’s always something more urgent, and eventually someone calls it resistance to change, as though it were a character flaw.
It isn’t.
That resistance isn’t laziness; it’s a perfectly reasonable response to an assignment that puts the burden of freeing you entirely on you.
And then it ends up working against you. If you don’t deliver your part—because there simply isn’t room for it in your day—the project stalls with your name next to it. Now you’re the one blocking the very thing the company wanted to do to stop depending on you.
At the follow-up meeting, everyone sees your unchecked box, never the reason it remains unchecked, and what used to look like your ability to solve problems starts to look like you’re slow.
So you end up logging on over the weekend to document things, because you know perfectly well that by ten on Monday you’ll be dealing with a new fire, writing a report for a customer, or preparing for a meeting with support about that account whose renewal is three weeks away.
The deal: you share the knowledge, the agent repeats it
The idea is an agent for your team or department that knows how things are done there and answers the questions people currently ask you: where a document is, what was done last time with a customer like this, what the implementation steps are, what criteria determine when to escalate something, who needs to be notified when a particular thing happens.
And before we go on, let’s be clear about what it does and doesn’t do. Because I know exactly what you’re thinking: this is the first step toward replacing you. It isn’t.
- It doesn’t take away your judgment. The difficult decisions—the ones that depend on context, the customer’s situation, or what was negotiated at the time—remain yours, because the agent doesn’t know those things and won’t.
- What it does take away is the repetition, which is where your day goes without anyone noticing: the same ten questions every week, asked by different people, interrupting you fifteen times and forcing you to mentally reconstruct something you’ve already explained four times that month.
One important point, because otherwise the project starts at the wrong end: an agent can’t read your mind. If what you know isn’t captured somewhere, it has nothing to draw on for answers, and the project is useless. As with any data project, this doesn’t start with buying a tool; it starts with getting what you already know out of your heads.
The good news is that sharing knowledge with a machine takes much less effort than documenting it for a manual, because you don’t have to write polished prose, create an index, wrestle with formatting, or get anyone’s approval. You can explain it the way you would to a new colleague, even by speaking it aloud.
How to stop being the hero—and stop relying on them
So far, I’ve written for the person holding everything together. But if you lead a team, you’re probably in both positions at once: you’re someone’s hero, and someone else is yours.
If you’re the one holding everything together—the hero—the first thing to think about is how you frame the issue. If you lead with how overwhelmed you are, the conversation will turn to redistributing tasks and promising to look into it.
Do the opposite: use data and speak the language of business.
- Measure. For one week, write down what people ask you—just the question, not the answer. In five days, you’ll have an exact list of what’s eating your time, and it usually surprises even the person keeping track.
- Translate it. Don’t go in saying, “I get interrupted a lot.” Show how many of those questions needed your judgment and how many came from someone looking for information that already existed. That second number turns your problem into a company problem.
- And ask for something specific. Don’t ask for help in the abstract, because that translates into hiring someone who’ll end up asking you questions. Ask for a defined block of time to share what you know and set up an agent for your department. Frame it in terms of what the company gains: operations that no longer depend on one person and the ability to bring new people on board without burning you out explaining the basics.
And say the other part, too, because it matters: you want to grow, and for that to happen, someone needs to be able to take over your role.
If the person holding everything together is your team’s hero, there are three things to keep in mind so all that knowledge doesn’t stay concentrated in one person:
- This is already costing you money, even if it doesn’t appear as a line item: a senior employee is spending half their day answering questions they already know the answers to; you can’t bring anyone new on board without taking up that person’s time to train them; and when they leave, you’ll pay the full cost of that learning all over again, with the added problem that your customers will notice before you do.
- As long as operations live in one person’s head, you can’t scale. You can’t open up a new segment, double your customer portfolio, or build a second team, because everything goes through the same person and all you achieve is a longer queue for them. And if you ever need to show how the business works, whether during a funding round or due diligence, operations depending on who happens to be available that day isn’t a minor detail. It’s a risk people will scrutinize.
- That person won’t ask you to change it. They’ve spent too long hearing that they’re indispensable to risk looking less necessary. So if you want it to happen, you have to open the door.
The good thing is that fixing this isn’t about budget. It’s about three decisions: who decides when the agent can’t answer, where all that knowledge lives, and who keeps it up to date.
Without those decisions, setting up the agent merely spreads the burden around, and six months from now you’ll have a new hero with a different name.
An exercise for this week
If you want to grow within the company, grab a notebook and a pen.
- Write down the role you’d like to have in two years.
- Write down the name of the person who would do your job if you were given that role tomorrow.
And if you lead a team or you’re the CEO, do the same exercise, but add another column. Write down the five people you depend on most and, next to each name, who would do their job if they were gone tomorrow. Not who would try or who would muddle through: who would do it.
The number of blanks in that second column is your real risk map, and it’s almost always much higher than the growth plan on your desk assumes.
And if your own name appears on that list, as it often does, start there. Because the most expensive hero in a small company is almost never the CSM: it’s the founder.
The hero problem isn’t solved by doing more or making yourself even more indispensable. It’s solved by getting the knowledge that currently lives only in your head out into the open and having someone—or something—take over the part you repeat every week.
And while you decide whether to start that conversation, I’ll leave you with the question I’d use to open it: who benefits from your being indispensable?
