The Peter Principle
In 1969, Laurence Peter and Raymond Hull published “The Peter Principle,” a book that began as satire and ended up as one of the most accurate organizational observations ever committed to print. Here’s the principle, and it probably describes something happening to you right now. In a hierarchy, every employee tends to rise to their level of incompetence. You get promoted because you’re good at your current job. You get promoted again because you’re still performing well. You keep getting promoted until you reach a position you can’t do well, and then the promotions stop, because you’re no longer succeeding. You remain in the position you’re incompetent at, doing it badly, often for the rest of your career.
The satire was in the delivery. The observation was real. And what Peter and Hull didn’t fully explore, what this episode is about, is your psychological interior when you’ve been promoted into incompetence. Not the organizational chart. Your inner experience of being in a role where you don’t know what you’re doing, where the skills that made you successful have stopped being sufficient, where people are looking to you for answers you don’t have.
That experience is one of the most quietly devastating things that can happen to you as a high-performing man. And it’s, by definition, something that happens to the most successful men, because you can only be promoted beyond your competence if you were competent enough to be promoted in the first place.
Picture a man, call him Steven. He’d been the best sales manager in his division for six years, consistently a top performer, widely liked, genuinely gifted at developing his team and closing deals. His VP offered him the regional director role with genuine enthusiasm. Steven was the obvious choice. He was flattered and ambitious and he said yes immediately. Within eight months, he was convinced he’d made the worst decision of his life.
The skills that made him a great sales manager, the relationship building, the tactical problem-solving, the ability to read a client and close a room, were largely irrelevant to the regional director role. The regional director needed to think strategically across multiple markets simultaneously. He needed to manage managers rather than frontline salespeople. He needed to interface with finance and operations and marketing in ways that required entirely different mental models. And he needed to build organizational capacity rather than close individual deals. Steven could describe all of these requirements. He had no idea how to actually do them.
He spent fourteen months performing confidence he didn’t feel, making decisions he wasn’t sure about with a certainty he didn’t possess, avoiding the specific meetings and conversations where his lack of competence was most likely to be exposed. He gained twenty pounds. He started waking at 3am with a specific quality of dread he’d never experienced before. He drank more. He brought less of himself home. He told his wife things were going well.
This episode is about what Steven was going through. It’s about why this happens so reliably to capable men like you. And it’s about what I’m calling the Competence Acceleration Protocol, the specific, demanding work of actually closing the gap between where your skills are right now and where your role requires them to be.
Stay with me through this, because it’s going to ask something of you that most conversations about career advancement don’t. Most of what you’ve heard about getting promoted focuses on how to get there. This is about what happens after you arrive, when the getting-there skills stop being the skills that matter, and you’re left holding a title that assumes a competence you haven’t built yet. That gap is normal. It’s survivable. And it’s closable, if you do the actual work instead of the performance of the work. We’re going to walk through exactly how.
Why the Peter Principle Is Structural, Not a Character Flaw
Peter’s original observation was organizational and satirical. The deeper insight is developmental. Every new level of responsibility requires a genuinely different skill set from the one that produced success at your previous level. The skills of an individual contributor aren’t the skills of a manager. The skills of a manager aren’t the skills of an executive. The skills of an executive in one domain aren’t the skills of an executive in a different domain. These aren’t small differences. They’re often fundamental reorientations of how you think, what you prioritize, what success looks like, and what kind of work actually moves the needle for you.
What makes this hard is that the transition between levels rarely gets named clearly for you. Nobody tells you: congratulations on your promotion. Nobody says the skills that made you excellent at your previous job are now largely irrelevant. Nobody warns you that you need to build an almost entirely new skill set in the next twelve to eighteen months. Nobody warns you that during that period you will feel lost. You will make mistakes. You will be tempted to perform competence rather than build it. Nobody says that to you. They say congratulations, here’s your new office, here are your direct reports. And you go into the new role assuming your previous success is evidence of a readiness you don’t actually have yet.
Anders Ericsson and the Mechanics of Competence
Anders Ericsson spent his career studying expertise, specifically how human beings build the highest levels of competence in complex domains. His research, summarized in “Peak: Secrets from the New Science of Expertise,” produced one of the most important and least comfortable findings in all of performance psychology. There’s no such thing as natural talent as an explanation for high performance. What looks like talent is, on examination, always the product of a specific kind of practice Ericsson called “deliberate practice.”
Deliberate practice is not the same as practice. It isn’t putting in hours. It isn’t doing the thing you’re already good at, repeatedly, until it feels more comfortable. It’s working at the edge of your current capacity, receiving specific feedback on your performance, identifying the precise points of failure, and systematically addressing them through focused repetitive effort. It’s uncomfortable by definition. If it’s comfortable, you’re practicing within your existing competence, not at its edge. And it’s the only mechanism by which genuine competence at genuinely difficult skills actually gets built.
Here’s the relevance to your own situation. Closing the gap between where you are and where your role requires you to be requires deliberate practice on the specific skills the new level demands. Not general effort. Not harder work in the same direction. Targeted, uncomfortable, feedback-driven development on the precise competencies where your gap exists. Most men in Steven’s situation don’t do this. They either hide the gap or they work harder in the directions they’re already competent, which makes them very busy but doesn’t move the needle on the competencies they actually lack.
This is worth you sitting with for a second, because it explains a specific trap you may already be in. Busyness feels like progress. It produces the sensation of working hard, the visible evidence of long hours and full calendars, and it’s genuinely exhausting in a way that can be mistaken for meaningful effort. But if the busyness is concentrated in the domain where you’re already strong, it’s not closing your gap. It’s avoiding it, in the most respectable-looking way available to you. Ask yourself honestly this week: of the hours you spent working, how many were spent inside your existing competence, and how many were spent at its actual edge?
The honest answer tells you whether you’re developing or just performing effort.
The Engineer Who Became a Leader
Picture another composite, call her Patricia. Forty-one when she was named chief technology officer of a mid-sized software company. She’d spent fifteen years as a highly effective engineering leader, technically exceptional, with a track record of building and delivering complex systems on time. Her new role required something her previous role hadn’t. She needed to think about technology not as an engineering problem but as a business asset. She needed to make capital allocation decisions. She needed to build credibility with a board of directors who thought in business terms she hadn’t needed before. And she needed to lead an organization of four hundred people rather than a team of twenty.
She did something most men in her position don’t do. She named the gaps immediately, clearly, and to the right people.
“I know what I don’t know. Here are the three areas where my competence is most insufficient for this role right now, and here is my plan for developing it. I need your support and your honesty as I do this work.”
That’s what she told her CEO in her second week. The CEO, who’d promoted her precisely because he trusted her judgment, wasn’t alarmed by this. He was impressed by it.
She hired an executive coach with specific expertise in the financial and board relationship dimensions she most lacked. She enrolled in an accelerated finance program at a business school designed for technical executives making exactly her kind of transition. She built a relationship with the CFO that was explicitly developmental. She told him she was learning his language and asked him to tell her when she was thinking like an engineer when she needed to be thinking like a business strategist. She asked for feedback from the board after every presentation, initially through her CEO, then directly as the relationships developed.
Eighteen months in, Patricia had closed the most critical competence gaps. She hadn’t become equally good at everything the role required, she retained a technical depth most CTOs don’t have and used it as competitive advantage. But she’d developed enough fluency in the strategic and financial dimensions of the role to be genuinely effective, instead of merely occupying the position while hoping the gaps wouldn’t be noticed.
Notice the arithmetic of her timeline, because it matters for you too. Eighteen months sounds long when you’re staring down month one, and it sounds short when you look back on it from month twenty-four. Most competence gaps closable through deliberate work take somewhere between one and two years to fully close, not the six weeks your own impatience wants to demand of you, and not the indefinite drift that hoping quietly produces either. Give your own gap the actual timeline it needs. Neither rush it into a shortcut nor let it stretch into an excuse.
Notice what Patricia did that Steven didn’t, and that most men in his situation don’t do. She built the learning infrastructure instead of performing competence while the actual gap grew underneath her. The performance of competence is comfortable for you in the short term and catastrophic in the medium term. The acknowledgment of incompetence, paired with a genuine plan to address it, is uncomfortable for you in the short term and is the only path to genuine competence in the medium term. There is no other route available to you, no shortcut, and no amount of confidence that substitutes for the actual work of closing the gap.
Amy Edmondson and Psychological Safety
Amy Edmondson’s research on psychological safety is directly relevant to what you’re working through right now. Psychological safety is the team climate in which people feel safe to take interpersonal risks, including the risk of admitting ignorance and making mistakes. Edmondson’s central finding is that psychological safety isn’t just nice to have for team functioning. It’s the necessary condition for learning, and therefore for your own competence development.
In environments where admitting ignorance or making mistakes is unsafe, where it leads to ridicule, career consequence, or social punishment, you don’t admit ignorance. You don’t ask the questions you need to ask. You don’t take the learning risks that would close your competence gaps. You perform competence instead, and the gap persists or grows while the performance of it consumes enormous cognitive and emotional energy you could otherwise be directing at actual learning.
Edmondson’s research shows that the highest-performing teams aren’t the ones with the lowest error rates. They’re the ones with the highest error-reporting rates, the ones where people feel safe to surface mistakes and near-misses, which enables the learning that prevents the same mistakes from recurring. Psychological safety isn’t comfort. It’s the willingness to be seen not knowing, not for the purpose of being seen, but for the purpose of finding out.
You can build a version of this for yourself even without an organizational culture that fully provides it. Start small. Pick one meeting this week where you’d normally nod along rather than ask the question that would expose what you don’t know. Ask it anyway. Watch what actually happens. In most cases, you’ll find the room is far less punishing than the story in your head predicted. The fear of exposure is usually larger than the actual consequence of it, and the only way you find that out is by testing it deliberately, in a low-stakes setting, instead of waiting for the stakes to force the test on you.
For Steven, the environment he was in was psychologically unsafe in a specific way you might recognize in yourself: his own internalized expectations. He was his own worst psychological threat environment. His belief that he should already know how to do this role, that needing to learn it was evidence of the inadequacy his promotion had inadvertently revealed, kept him from building the learning infrastructure that would actually address the gap. He was performing competence primarily for himself, because admitting incompetence to himself felt existentially dangerous to him.
Carol Dweck and the Mindset Crisis
Carol Dweck’s research on fixed versus growth mindset adds an important psychological layer to what you’re going through. In a fixed mindset, intelligence and ability get understood as fixed traits. You have a certain amount of intelligence, a certain level of competence, and your performance is evidence of what you have. In a growth mindset, intelligence and ability get understood as developable. Your current performance is evidence of where you are right now, and effort, strategy, and good feedback can move that number for you.
If you’ve been promoted beyond your competence and you’re carrying a fixed mindset, you’re in a specific kind of hell. Every moment of incompetence in the new role becomes evidence, in your own mind and potentially in the minds of others, that you don’t actually have what it takes. That the promotion revealed something that should have been caught earlier. That the gap between where you are and where the role requires you to be isn’t a developmental gap but an identity gap, evidence of who you fundamentally are, rather than of where you currently sit in a learning curve.
This is the mindset that produces the performance of competence instead of the building of it. If incompetence is your identity, hiding it is existentially necessary. If incompetence is a temporary developmental position, addressing it directly is just good strategy.
Dweck’s research shows something important for you. Growth mindset under pressure, specifically the pressure of high-stakes performance where failure is visible and costly, is harder to maintain than growth mindset in lower-stakes contexts. The men who most need growth mindset are the ones for whom fixed mindset is most powerfully activated. Men who’ve achieved significant success. Men who’ve built their identity around being capable and effective. Men who face a new challenge that briefly makes them neither. These are exactly the men who face the Peter Principle most acutely. You might be one of them right now.
The Sales Manager Who Admitted He Was Lost
Back to Steven. Fourteen months into the regional director role, he hit bottom in a specific and concrete way. He gave a strategic presentation to his executive team that he knew was inadequate while giving it. He could see on their faces that they weren’t buying it. The follow-up questions were soft, the kind of soft questions you ask when you’ve privately already discounted the presenter, and he left the meeting feeling something he hadn’t felt professionally since his early twenties. Genuinely, undeniably incompetent.
That evening, for the first time in fourteen months, he told his wife the truth. Not the whole truth, the truncated, honest-enough version that came out between his first and second glass of whiskey.
“I don’t know if I can do this job. I think I might have gotten here too fast.”
His wife’s response wasn’t what he expected. She wasn’t alarmed. She was relieved.
“I’ve been watching you perform okay for over a year. It’s good to finally hear from the real you.”
Steven went to his VP the next morning. Not to resign. To be honest. He told him he needed help. The strategic planning dimension of the role was where he was most out of his depth. He needed either development resources, a mentor who’d done this successfully, or both. He couldn’t keep guessing at it and expecting good outcomes.
His VP’s response landed on him harder than he expected.
“I’ve been waiting for you to say that for eight months. What do you need?”
This is the moment in the story most men never reach, because the performance of competence prevents them from reaching it. The moment of honest acknowledgment, to yourself, to someone who can actually help, is the hinge point. Before it, everything is management of a growing gap. After it, the gap can actually be addressed.
Steven spent the next year in an intensive learning mode. He was matched with a VP-level mentor in strategic planning. He attended an executive education program. He rebuilt his team’s rhythm around review processes that gave him better information to work with. He asked more questions than he was used to asking. He was, for the first time in the role, genuinely trying to learn it rather than perform having already learned it. Two years after that conversation with his VP, he was producing regional results the role had never seen. The gap was real. It was closable. It was only closed by acknowledging it.
Angela Duckworth and the Grit Question
Angela Duckworth’s research on grit, the combination of passion and perseverance she found to be the best predictor of high achievement across domains, adds an important dimension to your own protocol. Duckworth found that grit, specifically sustained effort toward long-term goals despite obstacles and setbacks, was more predictive of success than measured intelligence, talent, or family background.
What Duckworth also found, and this is the part of her research that gets discussed less, is that grit isn’t uniformly applied. If you’re genuinely gritty about things you care about, you’re often not gritty at all about things you don’t. The passion component matters to you: sustained effort in the absence of genuine interest is a different psychological experience than sustained effort in service of something that genuinely matters to you.
This has a direct bearing on your own protocol. Maybe you’re in a role that doesn’t align with your genuine interests. Maybe you were promoted into a position that represents organizational logic rather than personal fit. If so, you face a different challenge than a man who’s in the right role but needs to develop specific competencies to perform it well. For you, the competence gap may be real, but it’s pointing at a more fundamental question: is this the role you actually want, and is the grittiness you’re being asked to develop in service of something you genuinely care about?
That question is worth you asking honestly before you invest heavily in the Competence Acceleration Protocol. The protocol is designed for men who are in the right role but not yet fully equipped for it. If you’re in the wrong role, you have a different problem. Closing competence gaps in service of a role that doesn’t align with your deeper values is a form of sophisticated self-abandonment. It looks like success from the outside. It feels hollow from the inside.
The Competence Acceleration Protocol
Here’s the protocol itself. Six phases, sequential, building on each other. Jumping to phase five without completing phases one through four produces sophisticated activity in the wrong direction for you.
- Honest gap mapping. Before you can close a competence gap, you have to know precisely where it is. Not the vague discomfort of “I don’t feel ready for this,” but the specific, nameable, concrete skills and knowledge domains where your current capacity is below what the role requires. Write them down. For each gap, be specific: not “I’m not strategic enough” but the actual missing framework or skill. The more specific your gap description, the more targetable your development work becomes.
- Get external input. Your own gap mapping is inevitably incomplete, because the gaps you can most clearly see are the ones you’re most aware of, and your most costly gaps are often the ones you’re least aware of. Get external input from your supervisor, from peers in comparable roles, from trusted professional advisors who can observe your performance from the outside. Ask specifically where they see your thinking or execution fall short. This requires the psychological safety we just discussed, the ability to receive this information without existential threat. Build that tolerance in yourself before you ask the question. Then ask it.
- Prioritize ruthlessly. You cannot close all your gaps simultaneously. Attempting to do so produces diffuse, unfocused development activity that closes none of them deeply. Identify the two or three competency gaps with the highest current impact on your role performance, and build your development plan around those specifically. The others go on a list for later. The prioritized ones get all of your development energy until they’re meaningfully closed.
- Build deliberate practice. For each prioritized gap, design a deliberate practice regime in Ericsson’s sense. Specific activities, at the edge of your current capacity, with feedback mechanisms that tell you how you’re doing. This isn’t reading books about the topic, reading builds knowledge, not competence. This is doing the thing, getting feedback on how you did it, identifying the specific points of failure, and systematically addressing them. If your gap is strategic thinking, find problems at the right complexity level and work through them with a mentor who can give you real feedback on your reasoning. If your gap is executive communication, give presentations to smaller audiences and ask for specific critique. Practice in context, with feedback, repeatedly.
- Build the support structure. You will not close a significant competence gap in isolation. You need a mentor who’s done what you’re trying to do and can tell you the difference between the reasoning of someone who understands the domain and the reasoning of someone who doesn’t. You need a peer group working through similar challenges who can provide the reality-check and emotional support the process demands. You need honest feedback channels in your organization that give you real-time information on how your development is showing up in your performance. Build all three deliberately. Don’t wait for them to appear on their own.
- Protect the learning mode. The most insidious enemy of your protocol is the pressure to perform competence before you have it. This pressure is real, it’s constant, and it will convince you repeatedly that the exposure risk of being seen not knowing is higher than it actually is. Protect your learning mode, the explicit, acknowledged, this-man-is-developing stance, for as long as it’s genuinely accurate. Most people are more forgiving of genuine development in progress than you expect them to be. What they’re not forgiving of is discovering the performance was fake and the gap was larger than they knew. Get ahead of that by staying honest about where you actually are.
What Happens When You Don’t Close the Gap
The organizational and personal consequences of not closing the competence gap are worth naming directly for you. Choosing performance over development indefinitely is a choice, even if it doesn’t feel like one, and it’s often made without full awareness of what’s actually at stake.
Organizationally, if you’re the un-developing executive, you become a bottleneck. Your team knows the gap better than you do. They route around you, manage you, and make decisions without the input they’re nominally supposed to be receiving from you. Your organization performs at a level that reflects your limitations rather than its potential. And eventually, through the natural processes of organizational selection, you get removed from the role, usually in a way that’s more damaging to your career and self-image than an earlier, acknowledged pivot would have been.
Personally, the cost is what Steven was experiencing. The chronic stress of performance anxiety. The gradual withdrawal from relationships that might expose you. The physical symptoms that accumulate when your nervous system runs a sustained low-grade threat response month after month. If you’re living in gap-performance mode, you’re not just underperforming at work. You’re damaging your health, your relationships, and your sense of yourself as a capable and honest man, because living the performance requires a persistent dishonesty that erodes your integrity in every direction it touches.
The alternative, acknowledged gap, genuine development, temporary visible vulnerability in service of actual competence, is available to you at every stage. It’s available on day one of a new role, when the gap is smallest and easiest to close. It’s available on month eight, when it’s grown but before it’s become catastrophic. It’s available even at the bottom, when the performance has finally failed and the gap is fully visible to everyone. At every stage, the developmental path is available to you. The question isn’t whether you can take it. It’s whether you’re willing to.
Notice which stage you’re actually in right now, because the honest answer changes how urgently you need to move. If you’re early, day one to month three, you have the most room and the least pressure, and this is the cheapest possible moment to start doing the real work instead of the performance of it. If you’re in the middle, month four to month twelve, the gap has probably started to show, in small ways, to the people around you, and the urgency has increased even if nobody has said anything to your face yet. If you’re past that, if the gap has already produced visible consequences, the path is still open to you, but you no longer have the luxury of moving slowly. Name your stage honestly. It tells you your actual timeline.
The Questions You’re Actually Asking
Let me answer some things you might be turning over right now, because I hear versions of these constantly.
You might be afraid that admitting you’re not ready for your role will cost you the job, and you’re wondering how you know when it’s safe to be honest. This is a real risk that requires honest assessment of your specific organizational context. In psychologically safe organizations, where leaders respond to acknowledged gaps with support rather than punishment, being honest early is dramatically safer for you than letting the gap grow until it’s visible through performance failure. In genuinely unsafe organizations, you need to make a strategic judgment about how much you can acknowledge and to whom, while simultaneously pursuing the development work as aggressively as possible. Here’s the baseline principle: the gap is going to become visible eventually if you don’t close it. The only question is whether you control the narrative when it does, or whether it controls you.
You might be wondering how to know if you’re in the wrong role versus just in a gap you need to close. Ask Duckworth’s passion question: is this a role you genuinely want to be competent at? Not is it prestigious or well-compensated, is it the thing you want to be doing well? If the answer is yes, the work of closing the gap is in service of something meaningful, and grit is available to you. If the answer is no, if you were promoted into this role by organizational logic rather than your own aspiration, the competence work is in service of something that doesn’t genuinely motivate you. You should be having a different conversation with yourself about where you want to invest the next five years of your professional life.
Maybe you’re not in a formal leadership role, you’re just an individual contributor who got moved onto a project that’s over your head, and you’re wondering whether this framework even applies to you. It does, completely. The Peter Principle as a phenomenon isn’t confined to management hierarchies. Anyone who takes on work at the edge of their current competence, which is, in fact, anyone doing genuinely ambitious work, faces this same gap-performance dynamic. The same protocol applies to you: honest gap mapping, external input, deliberate practice, support structure. The stakes and the organizational complexity may be lower than the executive version, but your internal experience and your developmental requirements are structurally identical.
Maybe your boss promoted you and doesn’t know you’re struggling, and you’re wondering whether you owe him honesty. The more useful frame for you isn’t what you owe him but what serves you both best. Your boss has a stake in your success, he promoted you, which means his credibility is partly tied to your performance. A boss who finds out six months from now that you’ve been struggling in silence and not asking for help is unlikely to be pleased. A boss who finds out early that you’ve identified specific gaps and have a specific plan for addressing them has been given something useful: early signal and evidence of good judgment. Most competent managers would rather have the second conversation than the first discovery.
And you might have been in this role for three years, still not competent at key aspects of it, wondering if it’s too late for you. The developmental path is available at any point in your career. What changes over time is the cost-benefit calculation for you. Three years in, the gap is likely more visible and the expectations higher, which makes the intervention more urgent and the need for speed in closing it more pressing. Start with the honest gap mapping and the external input. Get the specific picture of where you are and where you need to be. Then build the deliberate practice regime. The urgency is real, but it doesn’t change the method. It just accelerates your timeline.
The Men Who Thrive After the Peter Principle Experience
Some men come through this experience in the best shape, emerging from the competence gap not just functional but genuinely stronger. Here’s what they share, worth you knowing as a model.
- They name the gap early. Not at the first sign of discomfort, that would produce perpetual paralysis, but before it becomes catastrophic.
- They treat the gap as information rather than a verdict. It tells them where to direct development energy, not whether they’re fundamentally capable of the role.
- They build their support structure deliberately and without embarrassment, as a first move rather than a last resort.
- They come out the other side with a genuine, embodied understanding of what it feels like to be incompetent at something important, acknowledge it honestly, and close the gap through sustained deliberate effort.
That last point matters most for you. Going through a genuine learning curve at high stakes and emerging on the other side competent is one of the most powerful confidence-builders available to you. Not the cheap confidence of never being tested. The real confidence of having been tested and developed through the test.
In this composite’s telling, Steven is now, five years after the conversation with his VP, one of the best regional directors his company has ever had. Not because the gap resolved itself. Because he stopped performing and started learning. The two years of genuine development work were the hardest professional years of his life. They were also, by his own account, the ones that produced the most lasting growth. That’s the Competence Acceleration Protocol at work. It’s available to you. The gap you have right now is not a verdict. It’s the starting line.
The Organizational Responsibility
- They name the development requirements of the new role explicitly at the time of promotion, telling the promoted person specifically what new skills they’ll need and over what timeline.
- They build in formal development support from day one, a mentor, a coach, or both.
- They create the psychological safety for honest gap acknowledgment by responding to it with support rather than punishment.
- They measure development progress with the same rigor they apply to performance outcomes, because development and performance aren’t separate activities, they’re sequential ones.
Everything so far has been from your own individual perspective, what Steven can do, what Patricia did, what you can do about your own situation. But organizations have a complementary responsibility worth naming, because you might be in a position where you make or influence decisions about other people’s development.
The organizations that produce the fastest competence development in promoted leaders share specific characteristics.
If you run an organization, lead a team, or make decisions about other people’s development, build these structures. The cost is real and the return is far larger for you. The alternative, promoting people and abandoning them to the Peter Principle cycle, is more expensive in every dimension. There’s the organizational cost of underperformance. There’s the human cost to the people going through it. And there’s the cultural cost of a place that treats failure to develop as a character flaw rather than a systems failure.
If you’re the one who did the promoting, you have a specific obligation here that’s easy to overlook once the announcement email goes out and everyone moves on. You saw enough in this person to promote them. That judgment was probably sound. But sound judgment about someone’s ceiling doesn’t automatically produce the infrastructure that gets them there. Check in with the people you’ve promoted at thirty days, ninety days, and six months, not to evaluate them, but to ask what they’re finding hardest and what they need. That single habit, repeated across every promotion you make, will do more for your organization’s competence than almost anything else on your leadership checklist.
The Impostor Syndrome Overlap
There’s significant overlap between what you’re experiencing and what psychologists call impostor syndrome, the persistent belief, despite objective evidence of competence, that you’re fundamentally a fraud who will eventually be exposed. The overlap matters to you because the two require different responses.
Impostor syndrome in the strict sense is a cognitive distortion. You have the skills, you’ve demonstrated them, you’ve received clear external validation, and you still can’t integrate the evidence of your own competence. The gap you fear is imaginary or dramatically exaggerated. The response to it is cognitive: building the internal evidence base that lets you accurately assess your own competence instead of systematically discounting the feedback you receive.
Your Peter Principle experience, in contrast, involves a real gap. The promotion has placed you in a role you genuinely don’t yet have the skills to perform at full effectiveness. Your response needs to be developmental, building the actual skills rather than just changing your self-assessment. If someone tells you to just believe in yourself more when you’re genuinely incompetent in a new role, that’s not just unhelpful for you. It actively prevents your developmental response by mislabeling the real problem as a perception problem.
The practical question is: how do you tell the two apart? The test is external feedback. If you systematically receive positive feedback from multiple credible sources about your performance in the specific domain where you feel the gap, and you still can’t believe it, that’s impostor syndrome, and your work is cognitive. If you receive feedback, from multiple credible sources, that your performance in specific areas is below what the role requires, that’s a real gap, and your work is developmental. Most men in your situation have some of both, some real gaps and some areas where they’re underselling themselves. Separating them accurately is your first step, and it requires the honest external input the Honest Gap Mapping phase is designed to produce.
The Role of Humility in Expert Development
Ericsson’s research on expertise development produced a finding that deserves more emphasis than it usually gets. The most important characteristic of people who develop expertise rapidly isn’t intelligence or talent. It’s the capacity to receive and use feedback effectively. And the prerequisite for receiving feedback effectively is a specific form of humility in you. Not self-deprecation or low confidence. The genuine intellectual openness to the possibility that your current understanding is wrong or incomplete. And the recognition that someone else’s observation about your performance contains information you actually need.
Maybe you’re in the Peter Principle situation and you’ve built your identity around being competent. Around being the one who knows things, who has the answers, who other people come to for guidance. If so, you probably have a specific problem with feedback receptivity. Your identity structure can’t accommodate the information “you’re wrong about this” without existential threat, so you manage that information away. You dismiss the feedback. You explain why the context was unusual. You redirect attention to your competence in adjacent areas.
You protect your self-image at the cost of the information you need.
Ericsson found that this pattern, which he observed in people who practiced extensively without improving, was the primary mechanism by which people got stuck at sub-expert performance levels. They were doing a lot of work, but the work was in the direction of confirming existing competence rather than extending it. The feedback that would have pointed toward the actual gaps was systematically filtered out by a self-protective identity structure. The result was decades of practice producing no improvement, because the information that would drive improvement was being rejected at the gate.
This shows up in small, specific ways you can catch yourself doing. Watch your own reaction the next time someone points out an error in your work. Notice whether your first instinct is to understand what they saw, or to explain why it isn’t actually a problem. The second instinct is the identity-protection reflex at work, and everyone has it to some degree, but the men who develop fastest are the ones who’ve trained themselves to pause before acting on it. Building genuine feedback receptivity requires you to first separate your self-worth from your performance quality. If your worth is contingent on achievement, you have no room for genuine feedback, because genuine feedback always contains improvement information, and improvement information presupposes current insufficiency, and current insufficiency triggers a core fear of worthlessness in you. Until you separate self-worth from performance quality, genuine developmental feedback cannot get through to you. This is the same inner work this show has covered before, applied here to a different problem.
The inner work and the outer work are one project.
The Doctor Who Had to Learn to Lead
One more composite, call him Michael. He’d been an exceptional emergency medicine physician for eighteen years when he was appointed chief of the emergency department at a major teaching hospital. His clinical skills weren’t in question, he was one of the best diagnosticians and most technically skilled physicians on the staff, and his reputation was the primary reason for the appointment. What the appointment hadn’t fully accounted for was that clinical excellence and departmental leadership are almost entirely different skill sets.
The emergency department at a teaching hospital is a complex organizational system. Two hundred staff members. Fifty thousand patient visits a year. A training program for forty residents. Relationships with a dozen other departments, regulatory requirements, and budget management. And the specific challenges of a high-stakes, high-stress environment that produces burnout at rates significantly above the hospital average. Leading it well required skills in organizational psychology, change management, financial literacy, curriculum design, and institutional politics that Michael had never needed as a clinician.
What Michael did right, from the beginning, was refuse to pretend he had skills he didn’t have. He told his department, in his first all-hands meeting, exactly where he stood.
“I am a very good physician. I am a developing leader. Those are different things. I am going to be making some decisions that turn out to be wrong, and when they do, I need you to tell me, because the only way I get better at this is through real feedback. I would rather know I’m wrong from you than find out from the consequences.”
This wasn’t a rhetorical strategy. He meant it, and his staff could tell the difference immediately, in a way that years of leadership training slogans never manage to achieve. The department responded with a quality of engagement his predecessor, a technically capable but defensively self-protective leader, had never elicited. When Michael made a policy decision that produced unintended negative consequences, senior residents brought the feedback directly rather than complaining sideways. When his performance review process needed redesign, his attending physicians told him specifically what wasn’t working rather than accommodating a broken process to preserve his feelings. He received the feedback he needed because he’d built the relational and psychological safety for honest feedback to reach him.
Three years in, Michael was running one of the lowest-burnout, highest-rated emergency departments in the region. Not despite his learning mode but through it. The genuine humility he brought to the leadership role, the actual willingness to be wrong and to know it, produced an organizational culture his previous department had never experienced. He’d learned the leadership role. The price was acknowledging, publicly and privately, that he hadn’t known it when he started. That price was cheap compared to the alternative.
What Michael’s residents remember most, years later, isn’t any particular decision he made. It’s the specific sentence he used, “I would rather know I’m wrong from you than find out from the consequences,” because it changed the physics of how information moved through the department. Bad news stopped traveling slowly, softened at every level of the hierarchy before it reached him. It started traveling fast and straight, because he’d made it safe to send it that way. That single shift, in an organization his size, was worth more than any strategic plan he could have written in his first ninety days.
The Two Traps: Freeze and False Confidence
If you’re in the Peter Principle situation, you tend to fall into one of two traps, and both prevent the developmental work that would resolve it for you.
The freeze trap: you become so focused on the gap that you’re paralyzed by it. You spend enormous energy analyzing the deficit. You worry about its implications. You catastrophize about what would happen if it were discovered. You manage the anxiety of the situation. And you never quite get around to the work of actually closing the gap. The analysis is real. The anxiety is real. The work is perpetually deferred. Men in the freeze trap often show up as “careful” or “thoughtful” to external observers, but the carefulness is actually avoidance of the risk that learning requires. Closing a real gap requires making mistakes in the direction of the new skill while the stakes are still manageable. Freeze prevents that risk-taking. The gap persists.
The false confidence trap: you overcorrect against the visible signs of inadequacy by performing a certainty you don’t have. You make decisions as if you understand the domain better than you do. You resist input because receiving it would require acknowledging the gap. You double down on the approaches you’re familiar with, because they produce the appearance of competence even when they’re not addressing the actual requirements of the role. Men in this trap often look effective for longer than men in the freeze trap, they’re generating action and demonstrating apparent decisiveness. But the action is in the wrong direction, the decisiveness is resolving the wrong problems, and the gap keeps growing underneath the performance.
The correct path between these two traps is what Edmondson calls “confident humility,” the capacity to act with the decisiveness your role requires while remaining genuinely open to the feedback that would reveal the flaws in your action. Not paralyzed by uncertainty. Not false certainty. Deliberate action paired with genuine learning orientation. This is not an easy balance for you to maintain, especially under the organizational pressure to look like you know what you’re doing. But it’s the only orientation that produces genuine competence development over time, and genuine competence is the only thing that ultimately resolves your situation.
Ask yourself which trap you’re more naturally drawn toward, because most men have a default. If you tend toward freeze, your practical fix is a forcing function: a deadline you can’t move, a commitment you’ve made publicly, something that requires you to act before you feel ready. If you tend toward false confidence, your practical fix is a feedback loop you can’t dodge: a mentor who checks in weekly, a metric you can’t spin, a person in your life with standing permission to tell you when your certainty has outrun your evidence. Neither fix is comfortable. Both are considerably more comfortable than staying stuck in the trap for another year.
Practical Steps for This Week
- Write down the top three areas where your current role requires competencies you don’t yet fully have. Be specific. Not “I’m not as strategic as I should be,” what specific strategic skill is missing? The more specific your gap description, the more addressable it is.
- Identify one trusted person in your professional network, a mentor, a peer, a supervisor, and ask them directly where they see your performance fall short of what the role fully requires. Listen without defending. Write down what they tell you. The discomfort of receiving this feedback is the price of the information. Pay it.
- For the single most important gap you’ve identified, pick one specific deliberate practice activity you could do this week that’s at the edge of your current capacity in that domain. Not reading about it, doing it, in conditions where you’ll receive feedback on how you did. Schedule it.
- Identify one person who’s done well at the specific competency where your gap is largest. Ask them for twenty minutes of conversation about how they developed it. Most people are willing to give this. Most men in your situation never ask. Ask.
- Set a six-month checkpoint. In six months, reassess the gap: has it closed? Is it smaller? What specifically changed and what didn’t? Committing to the measurement keeps your development honest. Without it, it’s easy to confuse activity with progress. Measure the actual gap, not the effort.
These five steps are the first week of your Competence Acceleration Protocol in practice. They’re uncomfortable. That discomfort is the feeling of actually addressing the problem rather than managing it. Welcome it. It means you’re working.
Notice something about this list before you move on. None of the five steps require you to already be competent. None of them require permission from anyone above you. None of them require a title change, a budget, or an official development program. They require an honest inventory, one conversation, one scheduled practice session, one twenty-minute call, and a date on your calendar six months out. You could start on all five today, this afternoon, with nothing but the willingness to be seen while you’re still learning. That’s the entire barrier to entry. It has always been the entire barrier to entry.
The Promotion That Reveals Everything
There’s something philosophically interesting about your own experience that most treatments of it miss by focusing too narrowly on the organizational mechanics. The promotion that puts you beyond your competence is, in a sense, the most honest moment your career will provide. It strips away the protective cover of demonstrated competence and forces the question on you: who are you when you don’t already know how to do this?
Before the promotion, you were able to maintain confidence partly on the basis of real competence, you knew you could do the job because you’d been doing it. After the promotion, you can’t rely on that. You’re in genuinely new territory. The question of who you are without the competence, without the performance your identity has been built on, is suddenly and unavoidably present for you.
For men with a performance-contingent sense of identity, this is existential crisis territory. For men with growth mindset and a psychological structure not built entirely on performance identity, it’s a different experience: genuinely uncomfortable, genuinely challenging, and genuinely interesting. The interesting part is that it’s the first time in a while the job has required you to actually grow. The comfortable performance of existing competence doesn’t produce growth in you. The genuine stretch into new territory does. The Peter Principle is, among other things, an invitation for you to become more than you currently are.
The men who accept that invitation, who treat the beyond-competence promotion as a growth event rather than a threat event, are the ones who come through it not just functional but genuinely expanded. They have the specific, durable confidence that comes from having closed a real gap through real work. They know something about themselves that the comfortable performance of pre-existing competence could never have taught them: that they can learn genuinely new things at genuinely high stakes and come out the other side better for it.
That knowledge changes how you approach the next stretch too, and the one after that. Once you’ve actually closed a real gap under real pressure, the next promotion, the next hard assignment, the next moment of visible not-knowing, carries less terror than it used to. Not because it gets easier in the moment, it doesn’t. But because you now have direct evidence, not theory, not motivational language, actual lived evidence, that you are the kind of man who can do this. That evidence compounds. Every gap you close honestly makes the next one less frightening to walk into.
The Long Arc of Competence: Career as Development
The deepest frame for everything we’ve covered is career as a development arc rather than career as a performance arc. The difference is fundamental for you, and it shapes everything about how you experience what you’re doing.
On the performance arc, your job is to perform at the highest level your current competence allows. Success is staying at the top of your current capability, executing reliably, and avoiding exposure of the inevitable gaps. The Peter Principle is catastrophic on this arc for you, because it forces the performance standard beyond what your current competence supports.
On the development arc, your job is to expand your capability continuously, to take on challenges that stretch you, to treat the gaps as the location of the most interesting work available to you. Success on this arc is growth: closing gaps, building new competencies, becoming genuinely more capable of genuinely more difficult things over time. The Peter Principle on this arc isn’t catastrophic for you. It’s the assignment. It’s the next growth challenge. The gap is the material.
Ericsson’s research on expertise development, read in this frame, is essentially an argument for the development arc as the basis for your career. He showed that the people who achieved the highest levels of performance in every domain weren’t the ones who executed reliably at comfortable levels. They were the ones who continuously pushed into their own discomfort. They treated every gap as the location of the next deliberate practice target. And they never confused the performance of existing competence for the work of building new competence.
The Peter Principle, on this arc, is a gift to you. It’s your organization telling you your development has produced enough value that they need more from you. It’s the invitation to the next level of your development arc. It’s uncomfortable and demanding, and exactly what the development arc requires of you. Accept the invitation. Build the skills. Come out the other side more capable than you went in.
Reframe the whole experience this way, right now, before you close this out. You are not a man who failed to be ready. You are a man whose organization believed you could become ready, and handed you the exact conditions required to actually do it. Most men never get handed those conditions. Most men spend entire careers inside roles that never stretch them past their existing competence, comfortable and static, and they call that comfort success. You have something rarer. You have a real gap, real stakes, and a real path through it. Treat that as the privilege it actually is.
When the Role Is Wrong: The Honest Exit
A complete treatment of this has to address the scenario nobody wants to talk about: sometimes the gap doesn’t close because the role is genuinely wrong for you. Not wrong because you can’t learn the skills, you can. Wrong because learning and performing those skills would require you to become someone you don’t actually want to be, in service of a career path that doesn’t align with your genuine values and interests.
This is different from the impostor syndrome scenario and different from the real gap scenario. It’s the scenario where you’re technically capable and have been placed in a role that’s technically learnable but that, when learned, wouldn’t produce a life you want. The successful regional director you’d become isn’t the professional identity you want to inhabit for the next fifteen years. The head of department you’ve been positioned to become isn’t who you actually are.
The honest response to this scenario isn’t to close the gap anyway and inhabit a career that doesn’t fit you. It’s to acknowledge the misalignment and make the strategic decision about whether to pivot before the gap is closed or after. This requires a different kind of honesty than the gap acknowledgment we’ve been discussing, it requires honesty about what you actually want, which is sometimes harder for you than honesty about what you don’t know.
If your own Competence Acceleration Protocol produces the realization that the gap you’re closing leads to a place you don’t actually want to go, that realization is valuable to you. It’s not a failure of the protocol. It’s the protocol working, because genuine self-honesty about competence development eventually requires self-honesty about whether the development is in service of anything you genuinely care about. Redirect accordingly. The decision to exit a role that doesn’t fit, made clearly and early, is dramatically better for you than the decision to close a gap into a life you don’t want.
This isn’t permission to quit the moment something gets hard. Discomfort alone doesn’t mean you’re in the wrong role, most genuine growth is uncomfortable, and bailing at the first sign of difficulty would just leave you repeating this same pattern in your next position. The distinction you’re looking for is between discomfort that’s pointing toward growth and discomfort that’s pointing toward misalignment. The first kind eases as your competence builds. The second kind doesn’t, no matter how much competence you build, because the problem was never the skill gap. Sit with that distinction honestly before you act on it either way.
The Mentor Relationship: The Fastest Competence Acceleration Available
Everything in your protocol benefits from one resource more than any other. A mentor who’s done what you’re trying to do. Someone willing to be honest with you about how they did it and where you’re falling short.
Ericsson’s research identified the mentor relationship as the single most powerful accelerator of deliberate practice in expert development. Not because mentors give you information you couldn’t find otherwise, most of that information is available in books or through experience. Because mentors give you something information cannot give you: calibrated, specific, honest feedback on your actual performance. It comes from someone who’s done the work themselves. Someone with both the credibility to speak and the investment to be honest rather than merely encouraging.
The mentor relationship that produces genuine competence development has specific characteristics for you to look for. The mentor has genuinely done the thing, not studied it or theorized about it, but done it themselves at a high level. The mentor is willing to give uncomfortable feedback, not brutal, but honest, and not filtered through the need to protect your feelings at the expense of useful information. You’re genuinely open to the feedback, prepared to hear that your reasoning is wrong, your approach misguided, your self-assessment inflated, and to treat that information as useful rather than threatening. And the relationship is sustained over time, not a single conversation, but an ongoing engagement where the mentor tracks your development and provides calibrated feedback as it progresses.
Most men underinvest in finding and maintaining genuine mentor relationships. You’re intimidated by the vulnerability of exposing your competence gaps to someone you respect. You’re not sure how to approach the relationship without seeming presumptuous. You treat the relationship as a one-time transaction rather than a sustained developmental engagement. All of these are mistakes you can correct. Find the person whose competence you most respect in the domain where you’re building. Ask them directly for the relationship. Be specific about what you’re working on and what kind of feedback you need. Show up prepared. Use what they give you. Report back on how it went.
Steven’s development accelerated most dramatically when his company assigned him a VP-level mentor who was direct, technically excellent in the strategic domain where Steven was weakest, and genuinely invested in the outcome. Six months of that relationship produced more competence development than the preceding fourteen months of unguided effort. That ratio isn’t unusual. Find your mentor. The investment pays.
If your organization doesn’t formally assign one, don’t wait for permission. Look at your own network right now, this week, and name one person who’s clearly done the thing you’re trying to learn how to do. You probably already know who they are. You’ve probably already thought about reaching out and talked yourself out of it, telling yourself they’re too busy, or that you’d be imposing, or that you should figure it out yourself first and only ask once you’ve made more progress. Reverse that logic. Ask before you’ve made progress, not after. That’s precisely when the guidance is most valuable to you, and most mentors, contrary to what you’re telling yourself, respond well to being asked. Being asked for guidance is a compliment, not a burden, to almost everyone who’s actually capable of giving it.
Closing: The Man Who Stops Performing and Starts Building
Your Peter Principle experience, at its core, is a confrontation with the limit of what you currently are. It’s the moment when your career, which has been, up to now, a vehicle for demonstrating who you already are, becomes instead a demand for you to become something you aren’t yet. That demand is uncomfortable for you. It’s also the most important invitation of your professional life.
If you accept the invitation, if you stop performing the competence you don’t have and start building the competence your role requires, you get to find out what you’re actually capable of. Not what you were capable of when the demands matched your existing skills. What you can build when the demands exceed you and you respond with genuine development rather than defensive performance.
That’s a different and better life than the performance arc offers you. Not easier. Better. More honest. More genuinely expansive. More aligned with the actual project of becoming more fully capable over time, rather than the limited project of demonstrating the capability you’ve already accumulated.
Picture the two versions of yourself at retirement, decades from now, and let that picture do some work on you. One version spent a career carefully staying inside the edges of what he already knew, protecting a reputation instead of building on it, and arrived at the end having demonstrated competence without ever having been meaningfully stretched by it. The other version spent a career walking directly into every gap that showed up, again and again, and arrived at the end having actually become someone larger than the man who started. Only one of those men gets to look back and say he found out what he was capable of. Decide now which version you’re building.
In this composite’s telling, Steven is now four years past the conversation that changed everything, the conversation where he stopped performing and told his VP he needed help. He’d put it this way now, looking back.
“The fourteen months I spent performing instead of learning were the most miserable of my professional life. The four years since have been the best. Same role. Different approach. Everything changed.”
That’s the whole story. It’s available to you. The only requirement is the decision to stop performing and start building. Make the decision. Do the work. The competence is waiting for you on the other side of the honest acknowledgment. It always was. It still is. Go get it, starting today, in whatever role you’re currently standing in, whatever gap you’ve been quietly managing instead of closing.
An expert is not someone who has stopped learning. An expert is someone who has learned to learn more efficiently and more deliberately than those around them. — paraphrase of Anders Ericsson, “Peak”
That’s the whole thing. The gap between where you are and where your role requires you to be is not evidence that you’re not an expert. It’s the location of the next level of expertise for you. Learn it. Do the work. The competence is on the other side of the deliberate practice. It always is. It always will be. This is how it works for everyone who’s ever built anything real. You are not the exception to that rule. You are subject to it, and that’s good news, because it means the path is available to you. Take it.
One last thing before we close. Somewhere in the last hour, you’ve probably thought of the specific gap that’s actually yours right now, the one you’ve been managing instead of closing. You know which one it is. You didn’t need this episode to tell you. What you needed was permission to stop performing around it and start actually working on it, and to hear, from someone else, that the discomfort of doing that is not a sign you’re failing. It’s a sign you’re finally doing the thing that closes the gap for real. Go do it. Not tomorrow. This week. The first honest conversation, the first specific ask for feedback, the first deliberate practice session at the edge of what you can currently do. Pick one. Start today.
Editorial StandardsCorrectionsMedical DisclaimerAbout Our ContentAffiliate DisclosureSite Map