You Were Great at Your Job. Then You Got Promoted
You were good at your job. Really good. And the company noticed. You knew the work, and you solved problems. Nobody had to keep telling you what to…
What do you do when the person you can’t afford to lose wants the one job you can’t afford to give them?
Most experienced managers have run into some version of this employee. They’re exceptional, perhaps the best you’ve ever managed. They know the operation inside and out, and they solve problems nobody else can. They show up when you need them, take ownership of difficult assignments, and deliver results, time after time. When something goes wrong, they’re the first person you call. If you could clone them, you would.
But there’s another side to this employee. They prefer working alone. They don’t always get along with their coworkers, and they have little patience for people who can’t keep up. They get frustrated when others don’t immediately grasp something that seems obvious to them. They aren’t bad people. They’re simply much better at doing the work than at working with the people doing it.
So you’ve learned to manage around those traits. You give them assignments they can handle independently. You give them flexibility and autonomy, recognize their contributions, and pay them accordingly. You even gave them their own office. They assumed it was because they were so good at their job. You knew it was partly because everyone, including them, worked better with a little distance.
For years, the arrangement worked. Then they decided they wanted to become a manager.
Look at it from the employee’s side. They’ve worked hard, delivered exceptional results, and solved problems no one else could. They’ve watched people with less experience and lower output move into management. Along the way they’ve received raises, recognition, special assignments, and increasingly impressive titles. So why shouldn’t they be promoted? In their mind, management is the natural next step, and you can understand why they see it that way.
The problem is that you see something they don’t. You know how valuable they are where they are. You also know that the very traits that make them exceptional in that role could become serious liabilities once they’re responsible for other people.
The employee who loses patience when someone makes a mistake would now have to coach people through their mistakes. The person who prefers working alone would have to build a team. The person who solves every problem personally would have to let others solve problems, even when those people take longer or go about the work differently.
You can already picture the problems. They can’t. And now you have a decision to make.
One thing I’ve learned about management is that you’re never managing only today’s work. You’re constantly watching the people doing that work and thinking about where they might fit tomorrow. In that sense, good management is a lot like a long game of chess.
You watch people develop, and you hand them responsibilities that stretch them. Sometimes you assign a task because it needs to get done. Other times you assign it because you want to learn something about the person doing it. How do they approach a problem? Do they ask questions? Do they involve others? What happens when they hit something they don’t understand? How do they react when someone else makes a mistake? Do they help coworkers grow, or do they take over and finish the job themselves? You’re watching how they handle pressure, responsibility, conflict, and uncertainty.
Over time, patterns emerge. You learn who can lead, who can organize, who can teach, who can crack complicated technical problems, and who works best on their own. You start to see opportunities for people that they may not yet see for themselves. Then you guide them, giving them new responsibilities and exposing them to different situations so they grow toward roles where their strengths add the most value. Not every assignment is a test, but almost every assignment teaches you something. You’re thinking several moves ahead.
The exceptional employee in our story may be brilliant at seeing the next move. They know what needs to happen and how to make it happen. Management, though, requires seeing how that move affects the entire board. Can they recognize potential in someone who doesn’t think the way they do? Can they develop an employee who struggles with something that comes naturally to them? Can they accept a solution that isn’t the one they would have chosen? Can they make decisions that benefit the organization even when those decisions make their own job harder? Those are different abilities.
And this is where it gets complicated. You may have spent years giving this employee opportunities, watching how they responded, and learning where their strengths lie. They may have spent those same years believing every opportunity was another step toward management.
You’re both looking at the same history and reaching completely different conclusions.
I can already hear the objections. Send them to management training. Give them a mentor. Let them take a leadership class. How do you know they can’t manage if you’ve never let them try?
Those are fair questions, and sometimes those are exactly the right answers. But there’s a distinction that often gets overlooked: someone who simply hasn’t learned how to manage is different from someone who has consistently shown behaviors that raise serious questions about whether they should manage others.
Training can teach management techniques. It can teach someone how to delegate, run performance reviews, communicate expectations, and handle difficult conversations. What it can’t guarantee is that the person will develop the patience, judgment, self-awareness, and willingness to actually apply those lessons.
That doesn’t mean people can’t change. It doesn’t mean experienced managers are always right about their employees. And it certainly doesn’t mean anyone should be denied an opportunity because they don’t fit a traditional picture of leadership.
But experience matters. When you’ve managed people for years, especially in demanding environments where mistakes have immediate consequences, you learn to recognize patterns in behavior. You’ve watched people work through hard situations and seen how they respond when things go wrong. You’ve seen how they treat coworkers when they’re frustrated, how they handle disagreements, and whether they help others succeed. Some people call that instinct. I think it’s experience recognizing patterns, and those observations should count for something.
Could you be wrong about this employee? Absolutely. Could training and mentoring change the outcome? Possibly. But another question deserves equal weight:
How much risk should an organization place on an entire team to give one employee the chance to prove they can manage it?
The decision doesn’t affect only the person being promoted. It affects everyone who would report to them, and those employees deserve a chance to succeed, too.
In 1969, Laurence J. Peter and Raymond Hull popularized the idea that people in a hierarchy tend to rise to their level of incompetence. It’s known as the Peter Principle. Most experienced managers have heard of it, and some have lived through it.
This is exactly the kind of situation where an experienced manager can see the Peter Principle coming. The employee hasn’t reached their level of incompetence yet, and you’re trying to make sure they never have to. Management isn’t a more important version of the employee’s current job. It’s a different job altogether. Sometimes the very skills that make someone exceptional in one role are the ones that make the move to another role so difficult. The person who insists on perfection may struggle to develop people who are still learning. The person who works fastest alone may struggle to build collaboration. The person who always knows the answer may struggle to let someone else find it.
You can recognize the warning signs and foresee the consequences. But recognizing a problem doesn’t necessarily tell you how to solve it.
You gave them a raise. They appreciated it, but they still wanted to be a manager. You gave them a more impressive title, and that helped for a while. You gave them more responsibility, more independence, and more recognition. You even built working arrangements that let them perform at their best. None of it changed what they wanted.
That’s because, to them, management represents something those other rewards don’t. It means advancement. It means recognition. It’s proof that the organization counts them among its most valuable people.
And perhaps the organization helped create that expectation. Think about how closely we tie career advancement to supervising others. We promote people into roles where they manage ever-larger teams, and we give managers higher titles, more authority, and often higher pay. Without meaning to, we teach employees that the ultimate sign of professional success is having people report to them.
So perhaps this employee isn’t being unreasonable. Perhaps they’re simply responding to the career structure we built. But understanding why they want the position doesn’t make giving it to them the right decision.
You’re now facing several options, and none of them is especially attractive.
You can promote the employee and hope your assessment is wrong. Maybe they’ll surprise you and grow into the role. Maybe training and mentoring will bring out abilities you haven’t seen. Or maybe they’ll damage the team, drive away good people, and struggle in a position they were never suited for, and you’ll have lost your best individual contributor in the process.
You can refuse the promotion, but then you risk losing the employee entirely. Someone who has been invaluable to your operation may start to feel unappreciated, overlooked, or treated unfairly.
You can keep offering raises, titles, special assignments, and other recognition. But you’ve already tried that.
Or you can have the conversation you’ve been avoiding: the one where you explain to an exceptional employee that being exceptional at their job doesn’t automatically qualify them to manage other people.
How do you have that conversation? How do you tell someone they’re among the best employees you’ve ever managed, yet you don’t believe putting them in charge of others is the right call? How do you explain why someone who produces less might actually make a better manager? And perhaps most important, how do you keep that exceptional employee motivated once the conversation is over?
I don’t have a perfect answer. Over more than 30 years in manufacturing, working my way from line mechanic to executive management, I’ve learned that some of the hardest management decisions don’t come with a solution that makes everyone happy. Sometimes you’re choosing between competing responsibilities: your responsibility to the organization, your responsibility to the people who would report to this employee, and your responsibility to an exceptional individual who has given you years of outstanding work. All three matter, and sometimes they point in different directions.
I suspect thousands of managers have faced this exact situation. You have an employee you can’t afford to lose and a management position you can’t afford to give them. You’ve recognized their accomplishments, rewarded their performance, and tried to create opportunities that fit their strengths. Yet the one thing they want is the one thing you believe would be a mistake. You can’t keep avoiding the conversation, and you can’t guarantee how it will turn out.
So I’m asking the managers who have actually faced this situation: What did you do?
Did you promote them and hope for the best? Did you refuse the promotion and risk losing them? Did you find another path that satisfied everyone? Or did you lose a great employee because you wouldn’t give them the position they wanted?
And here’s the question I’m most interested in:
Looking back, would you make the same decision again?