Most imposter syndrome advice was written for someone who has never done the job before. A promotion is the opposite problem. You already know how the work gets done. What you don’t know is how to do it as the person who used to argue with these people in the team meeting and now decides what they work on.
That mismatch is why the standard advice lands badly after a promotion. Learn the systems, ask more questions, give yourself time to ramp: all of it assumes a knowledge gap you don’t have. Your gap is somewhere else, and it has three specific parts.
Two of the three are about other people.
A promotion is not a new job
Imposter syndrome at a new job starts with a knowledge gap. A promotion starts with an authority gap: managing people who watched you not have the title yesterday.
That earlier post covers the five patterns the feeling shows up as, plus a week-by-week plan for a first quarter. This one doesn’t repeat either. The job changed. Your information about it did not.
Be precise about what we’re describing. Pauline Rose Clance and Suzanne Imes named it in 1978, and their original paper is careful: “The term impostor phenomenon is used to designate an internal experience of intellectual phonies, which appears to be particularly prevalent and intense among a select sample of high achieving women.” They also wrote that women who exhibit the impostor phenomenon “do not fall into any one diagnostic category.” A phenomenon, then. Not a diagnosis, and not something you treat.
Ruchika T. Malhotra and Jodi-Ann Burey push on the same point from a different direction in Stop Telling Women They Have Impostor Syndrome, Harvard Business Review, February 2021. Their argument: locating the fault inside the individual misses what she is usually responding to, which is bias and exclusion in the workplace around her. A promotion is a smaller version of the same structural point.
The three mechanics of promotion-specific imposter syndrome
Here is what actually changed on the day your title did.
Managing people who were your peers yesterday
SHRM, reporting on William Gentry’s research at the Center for Creative Leadership, describes the hardest part of a first management job as holding authority over people who were co-workers and friends first.
Here is where that stops being abstract. Your team splits a project two ways. One person gets the client presentation. One gets the compliance paperwork nobody wants. Last month that split went to whoever spoke first in the Monday team meeting. Now you decide it.
So you soften it. “Would you mind taking the paperwork?” It reads as optional, because a month ago it was.
You’re not being cowardly here. You’re reaching for the only register you have ever used with this person, and that register had no way of saying no inside it. Peers ask. Peers also decline, reshuffle and trade. The grammar of your sentence hasn’t caught up with the change in the room.
Your former peer says yes, then treats the timing as negotiable, because nothing in the ask said it wasn’t. They aren’t testing you. They heard a peer ask a favor and they filed it where favors go. The work slips a week. You read the slip as proof you have lost their respect, and that reading is the imposter feeling arriving. It arrived through a sentence you chose.
The complete version costs one more sentence than the soft one. You state the decision, the reason for it, and what done looks like by when, in a single pass: you’re taking the paperwork this week because you ran the same compliance check last quarter, and it needs to be filed before Thursday’s board meeting. Then you say the true part out loud. This is the first time I have had to give you work you did not pick. That sentence is expectation setting, not authority.
Evaluated on outcomes you no longer personally produce
Your output is now your team’s output. That sounds like a perk until the first week something goes well and you can’t point at the part you did. You ran two planning conversations, sorted out a scheduling conflict that would have delayed someone else’s piece of the work, and talked one person out of redoing work that would have cost three weeks. None of it is in the report that goes out afterward. The report lists four names, and none of them are yours.
The question underneath the feeling changes shape here. Before the promotion it was “can I do this,” and you had an answer you’d spent years building. After the promotion it is “can I make this happen through other people,” which is a different kind of competence and a much newer one. Delegation is the visible half of it: who gets what, with how much room to decide. The other half is calibration, knowing whose estimate to trust and whose to quietly double, and that one takes a few months of being wrong first. The first time you get it wrong in public, you hand a piece you’d have closed in a day to someone who needs six, the date moves in front of everyone, and you decide you can’t read your own team. The second time, you ask for the estimate before you assign it. That is most of the fix and none of the comfort.
The feeling arrives because the feedback loop got long. As an individual contributor you knew by Thursday whether Tuesday’s work was any good. As a manager you find out a quarter later, filtered through five other people’s execution, and by then you can’t separate what you did from what the team would have done without you. Most new managers fill that gap with the least generous explanation available: that they aren’t adding anything, and the quarter would have landed in roughly the same place with the chair empty. It is untestable, which is exactly why it sticks.
Old-job competence does not transfer
You were promoted for being excellent at something, and most of the time that something is now the thing you do least. The strongest individual contributor on a team gets the title, then spends the next year barely doing the work that earned it. Nobody says this at the announcement. The email says congratulations, your calendar fills with 1:1s, and the work you were best at moves to somebody else’s queue over about six weeks.
| What used to signal you were good | What signals it now |
|---|---|
| Delivering the hardest piece of work yourself | Deciding who delivers it, and being right about that |
| Knowing the most about the system | Knowing who on your team knows more than you, and saying so in front of people |
| Being the fastest person in the room | Being the reason three other people finished this week |
| Being praised for the output | Hearing nothing, because the output arrived without you touching it |
| Being asked for your opinion | Being asked for a decision |
The right-hand column is a real skill set, and nobody teaches it before the title changes. So competent people spend two quarters scoring themselves against a column they no longer play in and read the gap as fraud. Some of that doubt is worth keeping, because it’s what makes a new manager check their read before acting on it. The rest is a measurement error with a very convincing story attached, and it usually takes two review cycles before the right-hand column starts returning anything that feels like proof.
Where the standard fix backfires
Nearly every guide on this topic tells you to set clear boundaries with your former peers early. Good advice, with a cost nobody prices.
Draw the line hard and fast, in the first two weeks, and it reads as betrayal. The people who were your friends on Friday learn on Monday that the friendship had a manager in it all along. You get the authority, and you spend the exact trust you need most in your first quarter to buy it. The ones who take it worst are usually the ones who were happiest for you.
Draw it slowly instead, protect the relationship, let the old dynamic run a few more months, and the authority gap from the first mechanic never closes. Requests stay optional. Timing stays negotiable. By the time you finally set the line, you’re setting it in response to something that went wrong, which makes it look punitive rather than structural, and the person on the receiving end is right to notice the timing.
Both failure modes are real, and the same manager can produce both in sequence by starting soft and overcorrecting in month four. There’s no version of this that costs nothing, and we haven’t found a rule for which cost to take.
The advice that stops working the day you’re promoted
Search this topic and nearly every result comes back with the same tip: document your wins. Keep a list. Read it when the doubt hits.
It’s the most portable piece of imposter syndrome advice there is, and it’s the first one that breaks after a promotion.
The reason is the second mechanic again. A wins log is an evidence file, and evidence only counts against the standard you’re actually judged by. Your standard changed. What the list holds is a record of things you personally did: the deck you built, the escalation you took at 11pm, the error you caught in the numbers before they went out. Every entry is evidence for the job you no longer have. Read it on a bad Tuesday and you’ll feel better for an hour, then look at this quarter and find four weeks whose honest entry is “ran the process, said less in reviews, the project landed.” The log reads that as a drought. That is the job now.
A wins log works while you are still the person producing the wins, which is why it helps in a new job and stops helping after a promotion: the output you are now judged on is produced by your team, not by you.
The relationship survives the org chart change
When managers first take over a team of former peers, we see the same pattern: they change what they say in the 1:1 but not what they say in the group chat.
“Fixed, it’s live now, sorry for the noise.” Dana, an illustrative composite rather than a specific person, posts that in the team channel fifty seconds after someone flags an error in the team dashboard, the way she always has. She was promoted over the four-person team she sat inside for two years. In her 1:1s she is genuinely different now: she asks about workload, names blockers, closes with a commitment. In the channel she hasn’t changed at all. A deadline slips and she still drops the joke reaction on it. The two versions don’t match, so the team reads the 1:1 as the performance and the channel as the real Dana, and her workload conversations stop being binding. The fix is one behavior, and it isn’t gravitas or distance: in the channel, she asks who is picking it up, and then she waits.
The friendship doesn’t have to end. The default reply does have to change, and that is something the team can actually see.
Build the habit before the next 1:1
Both behaviors in this post are small, and both feel wrong the first time: saying what done looks like before the work starts, and handing over a decision you could make faster yourself.
That’s what Merlin is built for. Merlin runs inside Slack and Microsoft Teams, so the coaching happens where the work already is. You can walk through the exact sentence you’re about to send your former peer, before you send it, and get a read on how it will land from their side. Expectation setting and delegation are both skills it coaches, and Risely users see an average 26% improvement in the skills people work on, over 12 weeks.
If the doubt itself is the part you want to work on first, we have a blunter set of interrupts for that. Otherwise, open your calendar, find the next 1:1 with a former peer, and write the one sentence you’ve been avoiding before you walk in.