آدمِ کلیدی بودن، همیشه خبر خوبی نیست

For some time, I have been thinking about a familiar sentence: “If I am not here, this work stops.” It is usually said with pride, as if it proves someone’s importance, commitment, or experience. Sometimes it genuinely does. One person’s presence can make a major difference at a critical moment. But the more I look at that sentence, the less I can see it as only good news.

When one person untangles problems, remembers histories, and knows who needs to be involved in each situation, that is valuable. The problem begins when all of that remains only in that person’s mind. Then their value is gradually confused with everyone else’s dependence on them—a dependence that is heavy for that person and risky for the whole organization.

In sales, this situation is more familiar than we may want to admit. One person knows what a customer said before, what frustrated them, what promise they heard, and which sensitivity should not be overlooked. When the customer calls, others look for that one person before answering. Not necessarily because they are incapable of responding, but because the context for a useful response is unavailable to them.

In many small and mid-sized businesses one comes to know closely, this pattern repeats in a familiar shape: a meeting is held, everyone is present, yet the real discussion barely moves until one particular person arrives, because only they know why a previous agreement was closed the way it was, or why a certain customer needs extra caution. The rest are not idle; the key to the explanation simply sits with someone else.

Sales is not merely a customer name and the value of an order. Much of it lives in details that have never been captured in an accessible file or conversation: why a decision was delayed, the history behind a misunderstanding, a condition raised during a call, or an impression formed from the other person’s tone. When those details remain in one person’s memory, sales becomes tied to their constant presence.

In that situation, the key person usually works more than others, answers more questions, and moves more often between scattered issues. From the outside, this volume of requests may look like trust. From the inside, it can feel like a queue that gets longer every day: questions that should not be repeated, decisions that should not wait, and tasks that stall during one person’s brief absence.

The pressure does not come only from the number of tasks. The harder part is the mental energy required to constantly reconstruct the past. The key person has to remember what happened, why a decision was made, and what needs to be explained to someone else. They are not only doing today’s work; they are repeatedly pulling the past out of memory so that today can move forward.

For a while, this role may feel rewarding. Being the person others turn to creates a sense of being needed. Solving a problem without much explanation can become part of our professional identity. But being needed is not the same as being irreplaceable. The first can signal impact; the second is often a sign of a bottleneck for which we have not yet built a path.

I separate these two things: a person having experience, and a team or organization having access to that experience only through that person. Individual experience is valuable, and documentation is not meant to make it less so. On the contrary, when part of it becomes transferable, that person is freed from answering repetitive questions and can spend time on issues that truly require their judgment and presence.

Making knowledge transferable does not mean writing a massive, unusable manual. Sometimes it begins with a short note: What history does this customer have? What must not be forgotten at this stage? If this decision changes, who needs to know? What is still not final? Knowledge recorded in a usable form does not have to be complete in order to be useful.

Some information cannot, by nature, be transferred in a few written lines. A decision may depend on context, judgment, and sensitivity that become clear only through conversation. But that is not a reason to leave everything hidden in one person’s mind. Time can still be set aside to review cases, explain the reasoning behind decisions, and gradually bring others along.

In my view, a good starting point is not to ask, “How do I remove myself?” A more precise question is: “Which parts of my work depend on me only because they have not yet been turned into a shared language?” The answer may be a simple piece of information. It may be a decision criterion. Or it may be a relationship whose path and history nobody knows except us.

That question can be uncomfortable because it challenges part of the image we have built of our own value. If others can move some tasks forward without us, do we become less important? I think the opposite is true. Lasting value is not only solving a problem once; it is creating conditions in which the problem does not have to be solved from zero, with total dependence on one person, every time.

In sales teams, this change can begin in very ordinary places. After an important conversation, record the main point. Make the real status of a sales opportunity clear, rather than only its most optimistic version. Keep a promise made to a customer somewhere others can see it too. Name the owner of the next step, and do not let the path of handover remain purely verbal.

These may seem like small actions, but over time they reduce the cost of searching and guessing. Colleagues are less likely to have to ask from the beginning what happened, and customers are less likely to repeat their story to different people. Most importantly, the quality of the response becomes less dependent on one person’s memory, mood, or momentary availability.

Of course, documentation can become another burden when it is done only to check a box. Notes nobody consults, forms that are merely completed, and information recorded too late do not create trust. The goal is not to produce paperwork or data. The goal is for the next person to take the right next step with as little guessing as possible and with full respect for the history of the work.

That is why it may be better to begin by looking at costly moments instead of trying to record everything. Which questions are repeated constantly? Where do customers have to explain themselves again? Which decisions are delayed simply because one person is unavailable? In which parts of the work does handing over a case create anxiety? These are usually the places where individual memory has taken the place of a shared path.

Being a key person is not always a conscious choice. Work may have grown quickly, the team may have changed, or the opportunity to build a system may have been missed. So this perspective is not meant to blame the person carrying a heavy load. Often, that person did their best in difficult conditions to keep work from stopping. The point is that we cannot keep treating the continuation of this situation as a sign of success forever.

Real growth may begin when someone can step away from a workflow for a few days with peace of mind, without everything becoming unclear or coming to a halt—not because they no longer have a role, but because their role has grown beyond exclusive memory. The same principle holds in a negotiation, a working relationship, or anywhere our knowledge is meant to reach others: when something stays only in our own mind, others cannot take an independent part in moving it forward.

That is why I think lasting value is not found in rescuing a moment; it is found in building something that remains dependable after us. If what we know, the decisions we make, and what we learn along the way find a path to exist outside our own minds, then our brief absence is no longer a threat; it becomes a sign of something we built that no longer depends on just one person.