For much of my career, I’ve been someone people knew they could count on, and I’ve watched others become that person too.
There’s a certain amount of pride that comes with it. You know people trust you and that your contribution matters. Over time, being the person everyone relies on can even become part of your identity. You’re not just someone who solves problems. You become the person who solves problems.
But I’ve also seen what happens on the inside. The person everyone depends on can appreciate being valued while quietly wishing everyone didn’t depend on them quite so much. When being needed has become part of your identity, it isn’t always easy to let go of that role either. Responsibilities accumulate over the years. You answer questions someone else should know how to answer and solve problems that should no longer require your personal involvement. Eventually, you can become so good at carrying the load that few people stop to ask whether you should still be carrying it.
I’ve come to believe that leaders need to pay attention when this happens. An employee everyone considers indispensable may be an exceptional employee, but that person may also be telling you something about the organization itself.
How Competence Masks Weak Systems
Strong employees are very good at compensating for weak systems.
They remember what was never documented. They understand the history behind decisions. They know which client prefers a phone call instead of an email and which internal process doesn’t work quite the way the written procedure says it does. When staffing is short, they step into another role. When responsibility isn’t clear, they take ownership because someone has to.
I’ve seen this throughout my career, from engineering and project delivery organizations to nonprofit work. The environment may be different, but the dynamic is remarkably similar.
In an engineering firm, it may be the project manager who continues performing technical production because there’s no one else available, or the department leader who still carries a full project workload because the next level of leadership hasn’t been developed. Workloads change. People leave. Hiring takes longer than expected. Budgets are constrained. Smaller organizations, in particular, may not always have the luxury of having the ideal person available for every role.
There’s nothing inherently wrong with people stretching during those periods. Organizations need flexibility. The risk comes when a temporary solution gradually becomes the operating model.
Because these employees are capable, the organization continues functioning. Their performance can actually make structural weaknesses harder to see. Leadership sees that the work was completed without necessarily seeing the extra hours required to complete it. Leadership sees that the problem was resolved without recognizing that only one person in the organization knew how to resolve it.
Over time, competence can mask problems with staffing, training, delegation, documentation, or role clarity. The organization appears stronger than the system supporting it actually is.
The Vacation Test: Can Work Continue Without a Key Employee?
I use a simple question to think about this kind of organizational dependency: What happens when a key employee takes two weeks of vacation and truly disconnects?
Can someone else locate the information needed to continue the work? Does another person understand the client or project history? Can decisions move forward without waiting for that employee to return? Are responsibilities clear enough that people know who owns what? Has enough knowledge been transferred that the organization can continue operating?
A strong system allows you to answer yes to those questions.
That doesn’t mean every employee is interchangeable. Experience matters. Relationships matter. Institutional knowledge matters. There will always be people whose judgment and expertise are particularly valuable. Their absence, however, shouldn’t bring the organization, a department, or a project to a standstill.
The Vacation Test gives leaders a simple way to look for organizational dependency before it becomes a crisis. If normal work can’t continue while a key employee takes a real vacation, leadership should examine where knowledge, authority, relationships, or responsibilities have become too concentrated.
The answer isn’t simply to find another person who can carry the same load. It’s to build enough structure around the work that no one person has to.
When High Performance Hides Organizational Weakness
High performers often don’t allow things to fail. They catch mistakes before the client sees them. They stay longer when the work requires it. They answer questions that technically belong to someone else. They solve problems because they know how, and because letting the problem continue often creates even more work.
From an execution standpoint, that behavior can look like success. From an organizational standpoint, leaders need to understand what it took to produce that success.
A deadline met because someone repeatedly worked nights and weekends is different from a deadline met by a properly staffed team with a reliable process. A client relationship maintained almost entirely by one individual is different from a client relationship supported by the organization. A procedure that works only because one experienced employee knows when to work around it may need to be reconsidered.
This doesn’t mean leaders should discourage initiative or create rigid systems that prevent talented people from using judgment. I’ve seen organizations go too far in that direction as well. Processes can become so cumbersome that employees spend more time navigating the system than doing the work.
Practical systems should make it easier for good people to perform well. They create clarity, transfer knowledge, define responsibility, and reduce unnecessary dependence on individual heroics. When those systems stop working, leadership should expect employees to challenge them and should be willing to adjust.
There’s another side to this that leaders shouldn’t overlook. When someone has spent years being the person everyone depends on, building a stronger system may require that employee to let go of some things too. Sharing knowledge, developing other people, delegating decisions, and allowing someone else to become capable can feel uncomfortable when being the person everyone goes to has become part of your professional identity.
That transition needs leadership. The goal isn’t to diminish the high performer’s value. It’s to use that experience to strengthen the organization around them.
Build Organizations That Don’t Depend on Heroics
The strongest organizations I’ve seen still have exceptional people. They still have employees who step forward when something goes wrong, who know more than their job descriptions require, and who are willing to stretch when the situation calls for it.
What they don’t do is build normal operations around extraordinary effort.
Leadership has to notice when the same people are repeatedly absorbing gaps in staffing, accountability, or capability. Systems should capture enough knowledge and create enough structure that work can continue without depending on one person’s memory or availability. Execution should be evaluated not only by whether the work was completed, but by whether the way it was completed can be sustained.
That’s where Leadership, Systems, and Execution work together. Good leadership recognizes the dependency. Good systems reduce it. Sustainable execution is the result.
Great employees should strengthen an organization. They shouldn’t have to become the organization.