You earned the promotion. That's why it feels like fraud
Why it spikes during identity transitions, even for top performers
You get promoted. People congratulate you. Your calendar fills up like someone accidentally set your life to high-frequency interrupts.
A week later, you’re staring at a document you wrote and thinking: they’re going to realize they made a mistake.
Nobody tells you this part. Success sounds unstable when you say it out loud.
Impostor feelings are not reserved for people who lucked into the role. Research going back to Clance and Imes’ original 1978 study found that the phenomenon hits hardest among high-achieving people, not low performers guessing their way through (that is a whole different phenomenon). It spikes right after a promotion precisely because you earned it and the system just changed underneath you.
Small-to-medium orgs make this worse. No onboarding for the new level. No peer cohort who just went through the same transition. No “here’s what your job actually is now” document, because who had time to write one? The role is what you make it. That sounds like freedom until your internal evaluator has nothing to measure against.
I’m not here to reassure you. I want to build a clean model of why this spike happens, what it does to your execution, and where you put your hands on the controls. Whether you just moved from staff to senior staff, manager to senior manager, or director to VP.
The failure mode in the wild
In the first 30 to 90 days after a promotion, top performers do some version of the same thing.
They over-prepare. They over-document. They re-run decisions in their head like a flaky test. They keep doing the old job at night “just to be safe.” They avoid asking obvious questions because they’re supposed to be the person with answers now.
From the outside, it looks like conscientiousness.
From the inside, it feels like exposure risk.
And because you’re competent, you mask it. Still delivering. Still sounding sharp in meetings. Just doing it with a low-grade sense that you’re one question away from being revealed. That masking works especially well in smaller companies, where everyone’s busy enough that no one scrutinizes your adjustment period. You run hot for months before anyone notices the difference between “she’s really ramping hard” and “she hasn’t slept properly since the title change.”
High competence hides high distress long enough for it to calcify into a working style. I’ve seen people operate this way for years without anyone intervening. That’s the trap.
Promotions are identity transitions with a temporary observability drop
A promotion is not just “more scope.” It shifts what you’re responsible for, what counts as good, what people notice, and how your work gets evaluated.
Researchers at INSEAD who study role transitions in organizational life describe the process as moving from “an existing clarity of understanding to doubt, uncertainty, and ambiguity, and ultimately to a state of renewed clarity that resolves into an altered form.” The ground disappears for a while and comes back in a different shape.
During that transition, three things break at once. How they break depends on the specific jump you’re making.
Your old proof system stops compiling
In your previous role, you had a stable proof loop. You pointed at an artifact and said: this is what I did, and it worked.
Then you got promoted. The nature of the proof changed.
Staff to Senior Staff. The shift is from “I solved the problem” to “I made sure the right problem got solved.” Your previous proof loop was the code you shipped, the incident you resolved, the design doc that landed clean. Now the real deliverable is invisible: the architectural decision that prevented a class of future incidents, the technical direction that kept three teams from diverging, the conversation where you changed someone’s mind about a tradeoff before it became a production problem.
In a small-to-medium org, there’s no staff engineering ladder document telling you “technical leverage” is the new unit of output. You just feel less productive. One senior staff engineer I worked with told me she spent her first three months keeping a secret spreadsheet of pull requests, just to prove to herself she was still contributing. She was doing the most important work of her career, and her self-evaluation system couldn’t see any of it.
Manager to Senior Manager. You go from managing people to managing the system that manages people. Your old proof loop was your team’s output, your 1:1s, your sprint health. Now you’re accountable for outcomes across multiple teams, and the work is about alignment, hiring strategy, and making sure your managers develop as leaders rather than just deliver as operators.
In a smaller org, you might still manage some ICs directly while also owning a broader function. Your proof loop splits. Half your brain counts the old metrics while the other half can’t articulate the new ones. A senior manager at a Series B company told me he felt like two people: the one in the sprint review who knew exactly what was happening, and the one in the leadership meeting who had no idea what “strategic” meant when applied to him.
Director to VP. The artifact disappears almost entirely. Your deliverable is now the organization’s capability over a 6-to-18-month horizon. Can it execute. Can it hire. Can it survive the next strategic pivot without falling apart. You stop being in the room for most decisions. You start being evaluated on the quality of decisions made in rooms you never enter.
In a small-to-medium company, this transition happens before you have a proper leadership team underneath you. The gap between “what I’m accountable for” and “what I can directly observe” is enormous. One VP I know described the feeling as “trying to grade your own test when someone else is holding the answer key and won’t show you.”
In all three jumps, your internal evaluation system loses observability.
Your confidence drops because the metrics disappeared. Not because you got worse.
That’s a monitoring problem. Not a personality flaw.
The error bars widen
Early in a new role, you have fewer priors. You don’t know which risks are real, which stakeholders are bluffing, which decisions are reversible, which ones are career-defining.
Top performers are top performers partly because they’re good at reducing uncertainty. Right after a promotion, uncertainty increases faster than your ability to reduce it.
Psychological research on identity and life transitions shows why: when transitions alter our social roles and group memberships, they consume psychological resources at the exact moment we need those resources most. Your brain doesn’t distinguish between “I’m learning a new job” and “my social standing is at risk.” Same threat architecture fires for both.
In a small-to-medium org, this is amplified because the ambiguity is real. Not just perceived. The role probably hasn’t been done before, or it was done by someone who left without documentation, or it was carved out of a founder’s responsibilities and nobody’s quite sure where the boundaries are. You’re uncertain about yourself and you’re uncertain about the job. Those compound.
The result is rumination, hypervigilance, and a persistent hum of “I should already know this.”
Impostor feelings, in this frame, are your threat model reacting to a new attack surface.
Feedback degrades right when you need it most
This is the part people underestimate.
When you move into a more senior role, the room relates to you differently. Your questions sound like judgments. Your suggestions land like decisions. Your presence changes the social calculus of the meeting.
So people give you less direct correction and more vague evaluation. “You’re doing great.” “Keep driving alignment.” “Be more strategic.”
Research on why senior leaders get less useful feedback makes the mechanism plain: when someone is powerful, others go to great lengths to avoid upsetting them, aware that leaders hold some power over their future. Praise replaces criticism. Silence becomes the safest strategy.
In a smaller organization, this dynamic kicks in earlier than you’d expect. A senior staff engineer in a 200-person company wields more organizational influence than a principal at a large tech company, simply because there are fewer layers. A senior manager might be the most senior people-leader in the entire engineering org. A new VP might report directly to the CEO with no peer to calibrate against.
The smaller the company, the faster the power gradient steepens after a promotion. And the faster feedback degrades into pleasantries.
When feedback gets less concrete, your brain fills the gap with worst-case narratives. Vagueness is a vacuum. Anxiety is an efficient gas.
Why top performers get hit hardest
I want to be specific about this because it sounds counterintuitive.
High performers carry two traits that make the spike more intense. First, they’ve learned that effort works. When things feel shaky, they apply more force. The impostor cycle that Clance originally described has this at its center: over-preparation driven by anxiety, followed by relief at success, followed immediately by attribution of that success to the effort rather than ability. Which reloads the anxiety for the next round. It’s a loop that rewards itself.
Second, they’re rewarded for being the person who notices risks early. They are tuned for detection. After a promotion, those traits turn inward. You apply force to yourself. You start detecting your own uncertainty as the primary risk.
You become both the engineer and the alerting system. And you page yourself constantly.
In a smaller organization, there’s a third factor nobody talks about: you were probably promoted because you were already doing the job. That creates a strange illusion. Nothing should feel different. So the disorientation feels like personal failure rather than what it actually is, which is a normal system response to a role change the organization didn’t properly instrument.
The cost
Left alone, impostor feelings change behavior in ways that hit execution. I’ve watched this progression play out enough times to describe it with some confidence.
It pushes you toward over-functioning. You do work your team should own, because delegation feels like betting your credibility on someone else’s output. A senior staff engineer starts writing code her senior engineers should own. A senior manager starts running meetings his managers should lead. A VP starts making decisions that should never reach her desk.
It creates risk aversion. You avoid the bold decision because if it goes wrong, it confirms the story you’ve been telling yourself.
It drives performative busyness. You optimize for visible activity over high-leverage outcomes, because visibility feels like safety. I watched a newly promoted director spend his entire first quarter creating dashboards nobody asked for. He was building evidence of his own usefulness. The dashboards were fine. The strategic planning he should have been doing never happened.
It narrows your strategic aperture. Rumination consumes the attention you need for pattern recognition, talent development, and long-range tradeoffs.
And it quietly trains your team: if you keep grabbing the steering wheel, they stop learning to drive.
The cost profile scales with level. A senior staff engineer over-functioning means the engineers below stop growing technically. A senior manager over-functioning means the managers below never learn to manage. A VP over-functioning means the entire organization becomes dependent on a single person’s bandwidth. That’s how you end up with the “key person risk” that keeps founders up at night. Your organization becomes dependent on your overwork and then mistakes your exhaustion for leadership commitment.
The control surface
You cannot think your way out of a measurement problem. You fix measurement problems by changing what gets observed.
Treat the transition like any other system migration. Define the new interface, instrument the new success signals, agree on what “good” looks like before you start self-punishing for not hitting a target nobody defined.
Here’s a forcing function that works because it replaces vibes with concrete evaluation.
The Role Transcript Check
In your next 1:1 with your manager, or whoever owns your success in this role, get to the transcript version of the job:
What decisions are now yours to make, without escalation. What outcomes you’re accountable for this quarter that you weren’t accountable for before. What “great” looks like at 30, 60, and 90 days in observable terms. What you should stop doing, even if you’re good at it. What failure looks like, so you can stop inventing imaginary failure conditions.
This is a spec. Not a self-esteem exercise.
Without a spec, you default to old metrics. Old metrics make you feel like you’re failing, because the job changed.
Here’s what the conversation sounds like at each level.
Staff to Senior Staff. “What technical decisions am I now expected to make without getting consensus first? What does ‘technical leadership’ mean in concrete terms? Is it design reviews, is it setting standards, is it unblocking other teams? What should I stop personally building, and what happens if I keep building it?”
Manager to Senior Manager. “Which teams am I accountable for that I wasn’t before? Am I responsible for my managers’ development as leaders, or just their teams’ output? What organizational outcomes like hiring velocity, attrition, cross-team execution are now mine to own? What management work should I stop doing myself so my managers can learn it?”
Director to VP. “What is the time horizon I’m being evaluated against? What does ‘organizational health’ mean in terms you’d use at a board meeting? What decisions should stop reaching me, and who should be making them instead? What would a successful version of this role look like in a year, described in outcomes, not activities?”
If your manager can’t answer these with specificity, that’s data too. You are operating in an under-specified system, and your discomfort is rational. In a small-to-medium org, this is common. Not a red flag about you. A design gap in the company.
The Decision Transcript Check
There’s a second transcript worth capturing. The decisions you’re making that don’t leave clean artifacts.
When you catch yourself spiraling on “I didn’t do enough,” write down the decision. What decision was being made. What you recommended and why. What risks you named. What alternative you offered. What the business chose, and what happened next.
This does two things. It gives you evidence that your work is real even when there’s nothing to ship. And it prevents your brain from rewriting history into a story where you just sat in meetings all week.
I started doing this myself after a role change some years ago. Within two weeks I had a document showing I’d influenced eleven significant technical decisions, and my internal narrative had been “I haven’t done anything useful.” The gap between what I actually did and what my anxiety reported was staggering.
This tracks with what research on structured feedback-seeking behavior shows: when you force specificity into self-evaluation, you reduce the space where vague anxiety operates. Specific, behavior-linked self-assessment outperforms the open-ended “how am I doing?” question every time. The open-ended version just invites your threat model to fill in the blanks.
How you’ll know it’s easing
You don’t cure impostor feelings by never feeling them. You know the transition is stabilizing when the system stops amplifying them.
You stop rehearsing your credibility before every meeting. You delegate without secretly keeping a parallel backup plan. You make a reversible decision quickly and reserve your depth for the irreversible ones. Feedback gets more concrete because you’ve required specificity and built shared language for what good looks like.
Your identity catches up to your scope. Not because you finally feel senior, but because your operating rhythms match the job.
Promotions are migrations. Migrations have turbulence. The point is to instrument the new role so you can run it on evidence, not adrenaline.