Learn it → Apply it → Save as Skill
People get promoted for doing their current job well, not for how they'll do the next one. Push that process far enough in any hierarchy, and most roles end up filled by someone who has already reached the job they can't quite do. The fix isn't avoiding promotion. It's checking fit for the destination role before you make the call.
The Dr. Wallace’s Favorite Mental Models is designed to turn useful ways of thinking into reusable tools. Each model gives you a fast visual overview, deeper interactive learning, practical application exercises and an AI-ready Markdown skill you can save for future use.
Instead of merely reading about mental models, you can gradually build your own AI skills library: a collection of portable reasoning skills that can help ChatGPT, Claude, Grok and other AI assistants apply the mental models you value.
A hierarchy promotes people based on how well they perform in their current role. But the next role up often needs a different skill set entirely, managing people instead of doing the work yourself, for instance. Keep promoting on that basis and eventually most roles are filled by someone who has already reached what they can't quite do.
Important: the skills that earned the promotion don't automatically transfer to the very different skills the new role needs, coaching, delegating and prioritizing other people's work.
The model matters most when "who's ready for this promotion" and "who's really good in their current role" get treated as the same question.
Promoting a strong performer is a legitimate instinct. This model stops the jump from "great at the current job" straight to "ready for the next one."
Name what the current role actually requires, and what the target role actually requires.
List which skills genuinely transfer between the two roles and which don't.
Look for direct evidence of the destination skill, ideally through a small trial, not a hunch.
Promote when the evidence supports it. Build a real off-ramp when it doesn't, so declining isn't a demotion.
Open a use case to see what the model changes.
Check whether their strength is really about scope, organizing other people's work, delegating, setting priorities for others, rather than more of what made them individually productive. A trial project leading a small team is more informative than a track record alone.
Engineering management runs mostly on coaching, prioritization and unblocking others, not writing more code personally. Watch for a new manager who quietly keeps doing the old job instead of the new one.
Selling and coaching sellers draw on different skills. A large study of sales promotions found that promoting on individual sales results tends to predict weaker team performance after the promotion, not stronger.
Playing and teaching are not the same skill. Some of a sport's most successful coaches had unremarkable playing careers, and some of its greatest players never coached well.
Teaching a classroom and running a school, budgets, staffing, compliance, draw on different abilities. Consider a partial step first, like having them mentor other teachers on instruction.
An AI system, automation, or individual-contributor tool that handles a well-defined task reliably doesn't automatically handle a wider, less structured version of that task. Test it at the new scope before trusting it there, the same way you'd test a person.
This mirrors the pattern documented in a large study of sales promotions, not one specific company.
Expand for where the idea originated and what later research found when it was actually tested.
Laurence J. Peter coined it with Raymond Hull in their 1969 book "The Peter Principle: Why Things Always Go Wrong" (William Morrow and Company), built around the line: "In a hierarchy, every employee tends to rise to his level of incompetence." The authors intended it largely as satire, aimed at how organizations actually promote people.
For decades it was mostly enjoyed as a satirical observation. In 2018, economists Alan Benson, Danielle Li and Kelly Shue published a study, later appearing in The Quarterly Journal of Economics, analyzing more than 1,500 promotions to sales management across 214 firms and 156 million transactions. They found firms did favor top individual sellers for promotion, and those same promotions predicted weaker team sales afterward, empirical support for the pattern Peter and Hull described.
Cartoonist Scott Adams's related, more cynical idea: instead of competent people rising until they fail, organizations sometimes promote the least competent people into management on purpose, to get them out of the way of work that actually matters. It describes a subtly different, and arguably worse, failure mode than the one Peter and Hull originally described.
This pushes good performers upward regardless of fit, because there's no other way to recognize or pay them more.
Someone who was thriving and now struggles is more often in the wrong role than suddenly unmotivated.
Without a real off-ramp, both the person and the role stay stuck, since demotion usually reads as failure rather than a fit correction.
A strong performance review in the current job says little about a role with genuinely different requirements.
Not every promotion produces incompetence. When skills genuinely overlap, promoting on performance can work fine.
Deliberately promoting someone to get them out of the way, without evaluating them for the new role either, tends to produce worse outcomes than the ordinary version of this problem.
the role change preserves most of the core skill, a senior individual contributor leading a small team doing similar work, with direct evidence they've already coached or mentored others informally.
the stakes are low, the role has a short trial period built in, or the decision can be reversed cheaply and without stigma.
the promotion is hard to reverse, affects many people's day-to-day work, or the target role is meaningfully different from anything the candidate has done before.
This browser tool structures your thinking. It does not send your information anywhere or perform AI analysis.
Save as Skill converts the model into portable Markdown instructions that teach an AI when and how to evaluate a promotion for fit, what questions to ask, what evidence to seek, what mistakes to avoid and how to structure its analysis.
Save the skills you find useful and organize them into your own reusable library. The Markdown is intentionally model-neutral, so it can be used wherever an AI system accepts uploaded files, project knowledge, custom instructions or reusable text context. Platform capabilities differ, so this is a portable skill file rather than a claim of one-click installation.
No. It's a caution about the evaluation criteria, not a rule against promotion. The fix is testing for the destination role's real requirements, not freezing advancement altogether.
Economist Edward Lazear's 2000 analysis noted two possible explanations for an apparent post-promotion decline: reduced effort after the promotion, since there's no further rung to chase, or plain statistical regression, where an unusually strong pre-promotion run was partly luck and would have faded on its own. Real cases can involve some of both, which is why a single before-and-after comparison doesn't fully prove a skill mismatch by itself.
Dual-career ladders are the most common fix: a parallel "expert" or "principal" track that offers comparable pay and status without requiring someone to become a manager. It removes the incentive to chase a management role as the only way up.