liveBook · Manning

Peter principle

As explained in Collaborative Software Design: How to facilitate domain modeling decisions

The Peter principle is the management pattern in which people are promoted until they occupy a position in which they are incompetent.

The Peter principle describes a management pattern in which people are promoted until they occupy positions where they are incompetent. In software, an excellent developer may become a team lead, technical lead, or engineering manager without having the different skills those roles require. section 6.2.2

Promotion changes the work

A developer promoted into leadership may struggle in the new role and become stuck there because further promotion is unlikely and demotion is difficult. Their explicit rank remains high, but their implicit rank falls; teammates may then dismiss their ideas, including a proposal for collaborative modeling, without fairly evaluating it. section 6.2.2

Use the pattern to examine how status and capability interact:

  • Discuss ranking within the team and how it affects whose input receives consideration. section 6.2.2
  • Separate the merits of an idea from assumptions about the person proposing it. section 6.2.2

How Collaborative Software Design: How to facilitate domain modeling decisions covers it

How deep it goes
Defines the pattern, traces a developer’s promotion into leadership, and stops short of prescribing a management remedy.
Examples
Uses a developer-to-team-lead progression and a proposed collaborative-modeling change as concrete examples.
What it assumes
Assumes familiarity with software-team roles and distinguishes explicit organizational rank from implicit team standing.
What you can do after
Practice discussing team ranking and evaluate ideas separately from the proposer’s perceived status.
How it connects
Connects promotions with implicit ranking, team leadership, collaborative modeling, software architecture, and team morale.

This explainer was generated by Manning's knowledge graph from the text of Collaborative Software Design: How to facilitate domain modeling decisions. The section links point to the parts of the book it draws on.