I keep seeing the same pattern in companies: the best engineers get promoted out of the work they’re brilliant at, then everyone wonders why leadership gets worse and technical depth fades. This article is about that broken system, the symptoms it creates, and what better companies do instead.
Why Companies Keep Turning Great Engineers Into Bad Managers
Many companies manufacture mediocre managers by design.
Not because they are full of fools, not because engineers are secretly bad with people, and not because management is unimportant. They do it because their career system sends a blunt message: if you want more money, more status, more influence, and a future in this company, stop doing the work you’re excellent at and start managing people.
That may sound normal. In a shocking number of companies, it is normal. It is also a broken incentive system.
You’ve probably seen the pattern. A strong engineer grows into a senior engineer. Then they hit the invisible ceiling. The next “real” step is team lead. Then line manager. Then department head. Suddenly the only respectable way up is away from the craft. So the company promotes a great engineer into management.
Six months later, the team has lost one of its strongest hands-on contributors. The new manager is overloaded, still half-thinking like an engineer, still tempted to jump into details, still learning a job that actually requires a very different skill set. The team feels more watched, less helped. The former engineer feels stretched, frustrated, and oddly less effective. Everybody notices symptoms. Few people question the career system that created them.
That is the problem, and it is more than anecdotal. A major study published in the Quarterly Journal of Economics analyzed promotion data from 131 firms and found evidence consistent with the Peter Principle: companies often promoted people because they were top performers in their current role, even when other available signals would have been better predictors of how well they would perform as managers. In plain English, many organizations reward performance in the old job when choosing people for a very different new one. Source
That should make executives uncomfortable, because this is not just unfair to engineers. It is expensive organizational design.
The real damage is not just one bad promotion
When companies make management the only serious path upward, they usually create three problems at once. First, they plateau their experts. People who want to deepen their craft, raise their influence, and earn more eventually discover that the system has little imagination. “Senior” is tolerated. Beyond that, the subtext becomes: now go manage people like a grown-up.
Second, they fill leadership roles with people chosen for the wrong reasons. Being excellent at software engineering does not automatically make someone good at coaching, setting direction, handling conflict, creating clarity, building trust, or developing others.
Third, they confuse status with supervision. The company quietly teaches everyone that “real success” means having direct reports. That is cultural poison. It devalues deep expertise precisely when modern companies claim to depend on it.
There is strong evidence that career ceilings are not harmless. A 2022 meta-analysis covering 126 independent samples and 44,032 participants found that subjective career plateaus were associated with worse outcomes such as lower job satisfaction and organizational commitment, and higher turnover intentions. So when people feel stuck, that feeling does not stay politely in their heads. It leaks into motivation, attachment, and performance. Source
This is one reason so many teams feel odd even when nobody can point to a dramatic failure. The system is producing low-grade organizational damage all the time.
The Peter Principle: Great people are promoted until they reach a position they suck at
The lazy assumption behind the whole thing
The hidden assumption is simple: if someone is great at the work, the next logical step is to have them manage people who do that work.
That assumption is tidy. It is also deeply flawed. The move from engineer to manager is not a small upgrade of the same job. It is a different job.
This is where a lot of organizations fool themselves. They do not say, “We have carefully assessed whether this person is actually suited for leading people.” They say, “This person is excellent, ambitious, respected, and due for advancement.”
This is a lazy way to choose whom to promote. It rewards the wrong thing and then acts surprised when the result is a poor fit.
This is also where some of the micromanagement pain often comes from. Not because every former engineer becomes controlling, but because people promoted out of craft roles often end up in an awkward in-between state: no longer supposed to do the work, still strongly identified with the work, and now responsible for others doing the work. That is fertile ground for over-involvement, second-guessing, and “help” that feels a lot like interference.
I’m not claiming this is a fixed rule. But when companies force craft experts into people leadership as the price of advancement, they create a role mismatch, and role mismatch tends to produce exactly these kinds of ugly symptoms.
Most people do not even want the prize you are dangling
Here is another part many companies still refuse to face: plenty of individual contributors do not actually want to become managers.
In a Visier survey of 1,000 U.S. individual contributors, only 38% said they were interested in becoming a people manager at their current organization, while 62% preferred to remain individual contributors. The most common reasons included the expected stress, longer hours, and a simple lack of interest in managing people. Source
That should be a loud signal. When the system says, “Management is how careers work here,” but the majority of strong contributors do not even want that path, the company is not motivating people. It is cornering them.
Some will leave. Some will accept reluctantly. Some will fake enthusiasm because they want the pay raise or the status. None of those are signs of a healthy system.
And manager quality matters far too much to gamble like this
If management roles were minor, this would still be annoying but survivable. They are not minor.
Gallup reports that managers account for at least 70% of the variance in employee engagement across teams or business units. Whatever one thinks about engagement language, the underlying point is hard to dismiss: manager quality has an outsized impact on how people experience work and how teams function. Source
So when companies treat management as the default reward for top performers, they are not just being clumsy with career design. They are gambling with one of the most consequential roles in the organization. The old pattern is absurd: the company takes people it cannot afford to lose in their craft, moves them into a role it cannot afford to fill carelessly, and then acts surprised when both sides suffer.
The symptoms agile coaches and scrum masters keep seeing
This is one reason so many transformation efforts stall in strange ways. Agile coaches and scrum masters often work on the surface symptoms: team leads who cannot let go, managers who still want decisions routed through them, strong experts disappearing into coordination roles, leadership titles treated as the only meaningful recognition, technical communities weakened because the best people moved upward and outward, and frustrated senior specialists who feel stalled, underused, or quietly pushed toward management.
These are often treated as personal issues. A manager needs more coaching. An engineer needs to “broaden.” A lead needs to delegate more. Sometimes that is true. But often the deeper issue is structural: the company has built a career system that rewards moving away from direct value creation and toward supervision, whether or not that is the best fit.
That matters because you cannot coach your way out of a compensation architecture. You cannot workshop your way out of status signals. And you cannot make people trust a system that keeps saying, “The way to succeed here is to stop being what made you valuable.”
The way out is not complicated. The will to do it is.
The solution is not mysterious. Create real parallel career paths.
Not fake ones. Not cosmetic ones. Not a technical ladder with inflated titles, tiny pay differences, and no actual influence while the management ladder still carries all the prestige, budget control, and strategic voice.
A real dual-track system means an engineer, architect, staff engineer, principal, fellow, distinguished engineer, or domain expert can continue growing in compensation, visibility, accountability, and strategic influence without being forced into people management.
That is not theory. Plenty of organizations already do versions of it. Microsoft has long described an individual contributor path in engineering that allows people to remain ICs and still progress all the way to Distinguished Engineer, explicitly parallel to the management path. Wise publicly shares an engineering career map with two tracks: the Individual Contributor track and the Engineering Lead track. SHRM likewise describes dual career ladders as a way to let highly skilled employees advance without being forced into supervisory or managerial roles. Microsoft · Wise · SHRM
The broader organizational pattern matters too. WTW reports that high-performing organizations are 21% more likely to enable career progression for individual contributors as well as managers. At the same time, only 36% of organizations have formally defined and communicated career paths, and only 45% enable more diverse career movement such as progression for individual contributors. In other words, better organizations are more likely to do this well, and most organizations still have not. Source
That is a sharp contrast. Many companies still act as if parallel paths are exotic. The evidence suggests the laggards are the exotic ones.
But let’s not romanticize dual tracks either
A dual career path is not automatically good just because someone drew two ladders on a slide.
A lot of companies botch this. They create a technical track that looks respectable on paper but is obviously second class in practice. The titles sound fancy, but the pay stalls sooner, the influence is fuzzy, the criteria are vague, and the strategic decisions still belong to managers. Then the company congratulates itself for being modern while everyone can see which ladder really counts.
That does not solve the problem. It just disguises it.
A real technical or domain path has to include at least four things: real pay progression, real status, real influence, and real clarity. If management is still where the serious money lives, the message is unchanged. If titles on the technical path are treated like consolation prizes, people will read the hierarchy correctly. If senior experts do not have a voice in architecture, technical direction, product decisions, risk, quality, and long-term capability, the path is hollow. If nobody understands what growth looks like on each path, the system will turn arbitrary and political.
Anything less is theater.
This is not anti-management. It is anti-stupidity.
A bad reading of this argument would be that management does not matter. That would be nonsense.
Management matters enormously. Good leaders create safety, clarity, alignment, and conditions for people to thrive. The point is not to devalue management. The point is to stop using it as the universal reward for ambition.
The other bad reading would be that engineers should never become managers. Also nonsense. Some engineers become excellent leaders. Some are exceptional at translating complexity, developing people, setting direction, and creating strong systems around teams. They should absolutely have that path available.
The mistake is not that engineers sometimes move into management. The mistake is that in many organizations they are pushed there by design.
That is what needs fixing.
If you want fewer bad managers, stop manufacturing them
Here is the uncomfortable truth behind a lot of org charts: companies often do not have a leadership pipeline problem. They have a career architecture problem.
They built a system where the only credible symbol of growth is managing people. Then they act surprised when experts abandon their craft, reluctant managers accept roles they never really wanted, and teams end up led by people chosen mainly because they were strong at something else.
If that sounds familiar in your company, stop diagnosing only the personalities involved. Look at the incentives. Look at what gets rewarded. Look at what counts as prestige. Look at whether your best specialists can actually rise without leaving the work.
Because if the only way to advance is to stop doing what you are best at, your company is not developing talent. It is wasting it.
FAQ
Why do companies keep promoting engineers into management?
Because many organizations still tie pay, status, and influence mainly to people leadership rather than expert contribution. Research on promotions across 131 firms found evidence consistent with the Peter Principle: companies often reward strong current job performance even when it is a weak basis for predicting managerial success. Source
Is there evidence that career ceilings hurt motivation?
Yes. A 2022 meta-analysis across 126 independent samples found that subjective career plateaus were associated with lower job satisfaction, lower organizational commitment, and higher turnover intentions. Source
Do most individual contributors even want to become managers?
Not necessarily. In Visier’s survey of 1,000 U.S. individual contributors, 62% preferred to remain individual contributors and only 38% wanted to become people managers at their current organization. Source
Why is getting management promotions wrong such a big deal?
Because manager quality has a disproportionate effect on team experience and results. Gallup reports that managers account for at least 70% of the variance in employee engagement across teams or business units. Source
What is a better alternative?
A real dual-track system: parallel career paths where technical or domain experts can grow in pay, status, scope, and influence without being forced into people management. Public examples include Microsoft’s IC path to Distinguished Engineer and Wise’s published two-track engineering map. Microsoft · Wise
Subscribe to The Agile Compass
Weekly articles, special offers, and a chance to interact with me via email. No spam. Unsubscribe anytime.
Weekly articles
The Agile Compass delivers fresh insights each week.
No spam
Unsubscribe anytime. We only send valuable content.
-f58c1330.jpg)
