彼得原理
层级组织中的人，往往会晋升到自己不再胜任的层级。
显示原始英文内容
Peter Principle
In a hierarchy, every employee tends to rise to their level of incompetence.
Takeaways
- People get promoted based on success in their current role until they reach a position where they are no longer competent.
- A great developer promoted to manager might perform poorly, losing a good developer and gaining a bad manager.
- Organizations should offer dual career paths (technical vs. managerial) to prevent this stagnation.
Overview
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.
Examples
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.
Origins
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.
核心含义
在当前岗位表现好，不代表已经具备下一个岗位所需的能力。工程师、技术负责人和管理者面对的工作性质可能完全不同，如果晋升只奖励当前绩效，组织可能把人推向不擅长的位置。
晋升应评估目标岗位的能力，并提供试任、辅导和反馈，而不是把晋升当作唯一奖励。
实践例子
一名代码能力很强的开发者被直接任命为团队经理，却缺少冲突处理、授权和反馈能力。问题不在于他曾经是优秀开发者，而在于组织没有验证新岗位的能力要求。
来源与边界
Laurence J. Peter 在 1969 年提出这一讽刺性原理。它不是说所有晋升都会失败，而是提醒组织设计更丰富的职业路径和评价方式。