Peter Principle

The Peter Principle explains why organizations often end up with mediocre managers. A great engineer gets promoted to tech lead but struggles in the role, and now the company has lost a great engineer.

For a healthy organization, it’s essential to mitigate this. Not every senior engineer should become a manager; some might advance as staff or principal engineers instead. New managers need training to be competent in their new role.

The Peter Principle warns that promotion systems can create mediocrity at higher levels if not designed carefully.

In a development team, Alice is the best programmer. Management appoints her team manager since she’s the most experienced. But she has no experience or desire for people management. As a result, the team struggles. She either micromanages or misses essential management tasks, all while coding less (her main strength). Alice has reached her “level of incompetence” and might remain in that role indefinitely.

Consider a QA engineer fantastic at finding bugs who gets promoted to QA Lead, a role involving paperwork and strategy. If those aren’t their strengths, the QA process might decline.

Many tech organizations now use individual contributor (IC) career tracks to combat this, allowing great engineers to remain engineers with raises and titles rather than forcing them into management to advance. The principle also encourages rotations or acting in leadership roles to ensure competence before permanent assignments.

The Peter Principle was described in the book “The Peter Principle” by Laurence J. Peter in 1969. It was meant as a humorous piece of sociology and business insight.

Scott Adams’ Dilbert Principle later riffed on it, cynically inverting the idea by suggesting companies promote incompetent people to get them out of the workflow. Both highlight absurdities in corporate culture.