Stop Promoting Your Best People Into Jobs They'll Fail At
The promotion that ruins two roles
You have someone on your team who’s great at their job. They know the product cold. They solve the hardest problems. Customers ask for them by name. The team leans on them constantly.
So you promote them to manager.
Six months later, the team is struggling. The new manager is drowning in one-on-ones and skip-levels instead of doing the work they’re good at. They’re avoiding hard conversations with people who used to be their peers. The team’s best problem-solver is now spending their day approving PTO requests and sitting in leadership meetings where they have nothing to say.
You didn’t reward your best performer. You took them out of the role they were great at and put them in one they were never prepared for. Now you’ve lost your strongest IC and gained your weakest manager. Nobody won.
This happens constantly. And almost every leader has watched it play out.
The peer-to-boss problem
The most common version of this is the one that looks the safest. Someone grows up with the team. They’ve been there for years, they know everyone, they’re respected. When the manager role opens, they’re the obvious pick. They already have the relationships. The transition should be smooth.
It’s not. Because the job just fundamentally changed and the relationships didn’t.
I’ve seen this play out more than once. A strong individual contributor moves into management, but they grew up with the team. These are their people. They’ve been through tough projects together, covered for each other, built real friendships. And when some of those same people start underperforming, the new manager can’t make the call. They can’t sit across from someone they’ve eaten lunch with for four years and say “this isn’t good enough.”
So they don’t. Performance issues go unaddressed. Standards drift. The rest of the team — the ones actually performing — notice, and morale starts to slip. The new manager isn’t failing because they’re incompetent. They’re failing because the job requires them to be something different to people who still see them as a peer, and they can’t make that turn.
These situations rarely end well. The new manager either burns out, gets moved back, or eventually leaves — and in every case, the company lost someone who was excellent at their previous job. The promotion didn’t develop them. It set them up to fail. That’s the worst possible outcome for everyone involved.
The pyramid exists for a reason
In support especially, the team structure is a pyramid and it’s built that way on purpose. Ten tier-one agents. Four tier-two. Two tier-three. The ratios matter because the economics matter.
Tier-one handles the high-volume, lower-complexity work — password resets, basic troubleshooting, known issues with documented solutions. That work needs to get resolved cheaply. A dollar or two per ticket. When you start promoting everyone to tier two because they’ve “earned it” or because you don’t want to lose them, you’re now paying senior rates for junior work. Your cost per ticket goes through the roof and nobody downstream is doing the easy stuff anymore.
This isn’t just a support problem. It happens everywhere there’s a tiered structure — engineering, sales, consulting. The pyramid is a business model. When you promote people out of it without thinking about what happens to the layer they leave behind, you’re making an emotional decision with financial consequences. And that’s a leadership failure, even if it feels like you’re doing the right thing for the person.
The hard truth is that not every tier-one agent should become tier-two. Not every tier-two should become tier-three. Some people are exceptional at their level and that should be recognized and rewarded at that level — through compensation, through title, through scope — without forcing them up a ladder that doesn’t need more people on the next rung.
When the only path up is the wrong one
The bigger structural problem is that most organizations only offer one career path: up into management. If you want a raise, a title bump, more influence, or just the feeling that you’re progressing — the only door leads to managing people.
That’s a problem because not everyone should manage people. Some of your best technical talent has zero interest in performance reviews, team dynamics, or cross-functional leadership meetings. They want to go deeper, not wider. They want harder problems, not more direct reports. But if the org doesn’t have a senior IC track — staff engineer, principal architect, technical fellow, whatever the titles are — then management becomes the default and people take the promotion because there’s nowhere else to go.
What you end up with is a management layer full of people who didn’t want to be there and an IC bench that keeps losing its strongest players. The people who should be solving your hardest problems are now running standups and writing quarterly reviews. Meanwhile, the people who would have been great managers never got the shot because the promotion went to whoever was most technically impressive, which is a completely different skill set.
The succession planning connection
This ties directly back to succession planning. One of the biggest reasons leaders won’t let strong technical people move — whether it’s into management somewhere else, into a different function like engineering or DevOps, or even into a senior IC track that takes them out of the daily rotation — is that there’s no backup.
If your best tier-three engineer is the only person who understands a critical system, you can’t promote them. You can’t move them. You can’t even let them take two weeks off without risk. So they stay. And they stay. And eventually they either burn out, get frustrated, or leave on their own terms — which is the worst version of the outcome you were trying to avoid.
The fix isn’t to hoard your best people. The fix is to have someone coming up behind them. Cross-train. Document. Give someone else the hard problems early enough that they’re ready when the opportunity comes. If your succession plan for a critical role is “hope they don’t leave,” you don’t have a succession plan. You have a single point of failure that’s also a human being who wants to grow.
I’ve had leaders push back on moving someone out of their team. “We can’t afford to lose them.” And I get it — in the short term, it hurts. But the long-term cost of trapping someone in a role because you never developed a backup is worse. You lose them anyway, just later and with more damage.
What to do instead
Build an IC track that goes somewhere. If the only way to advance is management, you’ll keep pushing people into roles they shouldn’t be in. Create senior individual contributor paths with real progression — not dead-end titles, but roles with more scope, more influence, and more compensation that don’t require managing people.
Stop using technical skill as the primary criteria for management. The best coder is not automatically the best manager. Look for people who already do the informal leadership work — coaching peers, navigating conflict, thinking about the team’s problems and not just their own. Those instincts matter more than technical depth when the job shifts to leading people.
Be honest about the transition. Telling someone “management isn’t the right path for you” doesn’t have to be a death sentence. It can be a redirect: “You’re exceptional at this, and we want to invest in you going deeper here.” But that only works if “here” has somewhere to go. If the IC track dead-ends at the same level, you’re just delivering bad news with a nicer wrapper.
Invest in the peer-to-boss transition. If you do promote someone from within the team, don’t leave them to figure it out. The shift from peer to manager is one of the hardest transitions in leadership. They need coaching, clear expectations, and explicit permission to hold people accountable — even people they’re close to. Without that support, you’re handing someone a role and hoping the title alone will change the relationship. It won’t.
Plan for the move before you make it. This circles back to succession planning. Before you promote or move your best person, make sure the layer they’re leaving can absorb the loss. If it can’t, you’re not ready to make the move — and that’s a planning failure, not a reason to hold someone back forever.
The real cost
The Peter Principle — people rising to their level of incompetence — isn’t a theory in most organizations. It’s the operating model. We promote based on past performance in a different role, skip the development work that would prepare someone for the new one, and then act surprised when they struggle.
The cost isn’t just one bad manager. It’s the IC you lost. It’s the team that now has a leader who can’t lead. It’s the performers who watch dead weight go unaddressed because the new manager can’t have a hard conversation with a friend. It’s the next generation of ICs who see management as the only way up and take the promotion even though they don’t want it, because the alternative is standing still.
You can fix this. Build paths that don’t all lead to management. Promote for the skills the new role actually requires. Develop backups so you can move people without creating a crisis. And stop confusing “they’re great at this job” with “they’ll be great at a completely different one.”
Your best individual contributor might be exactly where they should be. The real leadership move is making sure that’s a place worth staying.
— Bruno