If your thinking is built on distortion, effort won’t fix it. This series gives you the models to see what’s actually going on.


Previous · Part 12
Confidence vs Competence: The Dunning–Kruger Misalignment

Next · Part 14
The Information Load Ceiling: Why More Data Lowers Performance
This builds on Part 12: Confidence vs Competence: The Dunning–Kruger Misalignment
Continue with Part 14: The Information Load Ceiling: Why More Data Lowers Performance
The clean failure mode of “deserved” promotions
The Peter Principle isn’t just a cynical joke about workplaces. It’s a structural prediction: in systems that promote based on performance, people will rise until they reach a level at which they become incompetent.
Not because they suddenly forgot how to do their job.
Because competence doesn’t transfer perfectly across the next role up.
When a promotion changes the job’s core constraints, the game changes. The skill you were rewarded for becomes less relevant, and a different skill set—often political, managerial, or architectural—gets replaced into the spotlight.
Why rising creates a competence mismatch
Let’s make the mechanism explicit.
Most organizations reward outcomes in the current lane. But the next lane typically requires different inputs:
- In the current role, you optimize execution.
- In the promoted role, you optimize coordination.
- Then, later, you optimize strategy and resource allocation.
- Then you’re navigating incentives, attention, and authority rather than craft.
If the promotion process doesn’t measure the new success conditions, then “good performer” becomes a noisy proxy for “good in the next constraints.”
The Peter Principle is what happens when the proxy is treated as truth.
The quiet lie inside many promotion systems
Promotion criteria often carry an implicit bargain:
“We’ll move you upward if you do well.”
But the real bargain is more like:
“We’ll move you upward and hope the skills that worked last time also work next time.”
Hope is not a strategy.
And “ineffective” doesn’t have to mean incompetent in a moral sense. It can mean simply misaligned. They may do many things well. They just can’t do the few critical things that matter in the new role.
That’s why the failure can be so hard to diagnose. Performance reviews track what’s visible, not what’s causal.
Inefficiency that compounds, not just happens
One person being ineffective is bad.
A promotion pipeline that produces the mismatch repeatedly is worse—because the system starts to re-allocate authority according to the wrong signal.
Then you get second-order damage:
- Budgets get spent by people whose feedback loops are mis-calibrated.
- Teams get managed by managers whose incentive models are wrong.
- Decisions become slower or riskier because the decision-maker can’t reliably judge tradeoffs.
- Culture shifts to reward the skills that simulate competence rather than deliver it.
This is how “deserved promotions” can generate undeserved dysfunction.
Where the Principle shows up fastest
You’ll often see it in transitions like these:
1) From craft to coordination
A top engineer becomes a mediocre manager because they were rewarded for solving problems directly. Management rewards different behavior: delegation quality, prioritization, and communication throughput.
2) From output to judgment
A star salesperson becomes a flawed sales leader because the leader must shape the pipeline through judgment and coaching, not through personal execution.
3) From execution to ownership
A brilliant operator becomes ineffective when ownership requires systems thinking, conflict resolution, and long-horizon tradeoffs.
A useful reframing: “fit” is a measurable property
Here’s the hard but empowering shift: the Peter Principle isn’t inevitable fate. It’s a signal that role design and evaluation don’t match.
If you want fewer ineffective promotions, you don’t only “pick better people.” You make the new role’s success conditions testable before the promotion.
Because competence is not generic. It is conditional.
Diagram: the mismatch loop
Diagram: High performance in Role A leads to Promotion decision; Promotion decision leads to Move to Role B; Move to Role B leads to Success criteria in Role B differ; Success criteria in Role B differ leads to Selection error; Selection error leads to Person becomes ineffective in Role B; Person becomes ineffective in Role B leads to System learns the wrong pattern; System learns the wrong pattern leads to Promotion decision.
Diagram: High performance in Role A leads to Promotion decision; Promotion decision leads to Move to Role B; Move to Role B leads to Success criteria in Role B differ; Success criteria in Role B differ leads to Selection error; Selection error leads to Person becomes ineffective in Role B; Person becomes ineffective in Role B leads to System learns the wrong pattern; System learns the wrong pattern leads to Promotion decision.
Tabs: different ways to respond (without pretending it’s simple)
Start by auditing promotions: what specifically predicts success in the next role? If you can’t name it, you’re not selecting—you’re guessing.
The practical prevention kit (what to implement next)
You don’t need a perfect system. You need fewer catastrophic mismatches and faster correction when they happen.
Run this as a lightweight diagnostic
Ask three questions internally:
- What are the non-negotiable outputs of the promoted role?
- What evidence best predicts those outputs?
- How will we detect mismatch within 30–90 days?
If you can’t answer #2 and #3, you’re vulnerable to the Principle.
Copyable: a “Promotion Fit” scorecard
Candidate:
Current role performance indicators (contextual, not absolute):
Next-role success criteria (3–5 items):
1)
2)
3)
4)
5)
Evidence to look for (how we’ll measure it):
- During role trial:
- In interviews / simulations:
- Via stakeholder feedback:
Mismatch detection plan (30–90 days):
- Red flags:
- What would “good” look like:
- Decision at day 60 / day 90:
[ ] Proceed with promotion
[ ] Extend trial
[ ] Keep in current track / alternative role
Final takeaway
Treat the Peter Principle as a design warning: promotions are experiments with role-specific failure modes. If you make the next role’s success measurable before permanence, you keep rising from turning into drift.
If this resonates, see how to apply it to your own work with the interactive Dispatch agent.
Be first to like this dispatch



