Picture your best salesperson. She closes deals others can't, mentors junior reps informally, and consistently exceeds quota. The obvious next step? Promote her to sales manager. Six months later, her team is struggling, she's miserable, and you've lost both a great seller and gained a mediocre manager.

This isn't bad luck. It's a pattern so common that Laurence Peter named it in 1969: in any hierarchy, people tend to rise to their level of incompetence. The Peter Principle isn't a joke about bad managers. It's a structural problem in how we think about advancement, and it quietly undermines organizations everywhere.

The core assumption behind most promotion decisions is flawed: that excellence in your current role predicts excellence in the next one. We promote the best engineer to engineering manager, the top teacher to principal, the star analyst to team lead. Then we wonder why so many of them struggle.

The problem is that each level often requires fundamentally different skills. A great engineer solves technical problems through deep focus. An engineering manager solves people problems through delegation, coaching, and political navigation. These aren't just different skills—they sometimes work against each other. The instinct that made someone excellent at coding ('let me just fix it myself') becomes a liability in management.

Peter Drucker observed this decades ago: the skills that get you somewhere are rarely the skills that keep you there. Yet we keep using past performance as a proxy for future potential, even when the future role bears little resemblance to the past one. We're essentially rewarding people by giving them a job they may not want and aren't equipped for.

Takeaway

Past performance predicts future performance only when the work stays the same. Promotion changes the work—so it changes the equation entirely.

As you move up an organization, three things shift dramatically: what you do, how you create value, and what success looks like. Individual contributors create value through personal output. First-line managers create value through their team's output. Senior leaders create value through strategy and systems that shape teams they may never directly interact with.

Consider the time horizon alone. A frontline employee might think in days or weeks. A middle manager plans in quarters. An executive thinks in years. Each transition requires rewiring how you spend your attention, what counts as 'productive,' and how you measure progress. Many people who excel at short-cycle execution genuinely struggle to operate in longer time frames—and vice versa.

The classic framework here is Ram Charan's 'Leadership Pipeline,' which identifies six career passages, each demanding new skills and a different value system. The transitions aren't gradual; they're step-changes. Someone can be ready for one passage but stuck at another for years. Recognizing this helps both organizations and individuals understand that getting stuck isn't failure—it's information about fit.

Takeaway

Each level of leadership requires a different definition of 'doing your job well.' If you can't articulate that definition, you can't develop people for it.

If the ladder is broken, what replaces it? Forward-thinking companies are building career lattices—structures that offer advancement through expertise, not just management. A senior engineer can grow into a principal engineer or technical fellow without ever managing people. A great salesperson can become a master closer or strategic account lead instead of a sales manager.

Microsoft, Google, and many engineering-driven firms have formalized dual tracks where individual contributor paths reach the same compensation and prestige as management paths. This solves two problems at once: it stops forcing technical talent into roles they don't want, and it stops filling management with people who shouldn't be there. Everyone wins—including the customers served by people doing what they're actually good at.

Building this requires honest conversations about what each role actually involves. Try this: before promoting anyone, write down the three skills the new role demands that they haven't demonstrated yet. If you can't think of any, the 'promotion' might really be a title change. If you can think of many, you may be setting them up to fail. Either way, the exercise forces clarity.

Takeaway

Growth doesn't have to mean managing more people. Sometimes the most valuable advancement is going deeper, not higher.

The Peter Principle isn't inevitable—it's a design flaw. When we treat promotion as the only reward for excellence, we punish good performers with roles they didn't ask for and weren't built for.

Better organizations recognize that careers should look more like lattices than ladders, with multiple ways to grow, contribute, and be valued. The goal isn't to keep people in place. It's to match people to roles where their strengths actually matter.