Being passed over for promotion hurts, but the hurt usually isn’t the hardest part. The hardest part is not knowing what the decision turned on. You might have lost on the work itself. Or the people deciding may never have seen your work, or nobody spoke for you in the room. The role may have been shaped for someone else before it opened, and sometimes the cause is bias. Each of these calls for a different response, so you need to know which one you’re dealing with before you do anything.
Most advice treats a missed promotion as feedback on you. The usual line is to calm down and ask what you lacked, then close the gap. If nothing changes, you leave. That’s sound advice if the cause really was a gap in your work. If it wasn’t, a six-month skills plan fixes the wrong problem so the next decision goes the same way.
So this guide works the other way round. After the first 48 hours, it helps you work out which of five things the decision turned on and how to ask your manager in a way that gets a real answer. Only then does it get to what you do about it.
What should you do in the first 48 hours after being passed over?
Make no move you can’t take back in the first two days. Don’t send the email you’ve already drafted in your head, and don’t resign. Don’t ask your manager for the reason yet, either. Use the time to write down what you know instead.
Each of those has a reason behind it. A sent message is permanent, and whatever it says will be read as a reaction to the news. It may also be forwarded to people you never meant to reach.
A resignation is a big decision, and the day you hear the news is the day you know least about why it happened. You haven’t heard the reasons yet, and you don’t know whether the next chance is six months away or two years away. So a decision made now rests on the weakest information you’ll ever have about it.
Asking for the reason straight away is the subtler mistake. It feels reasonable because you do want to know, but a question asked an hour after the announcement tends to land as a complaint. Your manager hears that you’re upset and answers the feeling rather than the question. You also don’t know yet what you want to ask, which comes from the next section.
So spend the time on paper. Write down the facts you know and the dates they happened. When did the role open? Who told you, and what exactly did they say? What did you hear about the process, and who did you hear it from?
After that, write a second list of the questions you still can’t answer. Keep both lists factual and leave out what you think it all means.
This takes some emotional intelligence, because you have to notice what you feel without letting it write the message for you. The lists help, because they give the reaction somewhere to go that isn’t your manager’s inbox. Keep them somewhere safe, because you’ll come back to them more than once.
Which kind of passed over was it?
A promotion decision can turn on at least five different things. It may have been the work itself or how your work was seen. It may have been a sponsorship gap, which means nobody with influence spoke up for you. It may have been structure or timing, or it may have been bias. The answer decides what you do next, because each one needs a different response.
If you lost on the work, a skills plan makes sense. But if you lost because the decision-makers couldn’t describe your impact, more skill won’t change that, because they still won’t see it. And if the role was quietly promised to someone months ago, a skills plan does nothing at all.
The causes also overlap, and a decision can turn on two of them at once. The first three can look almost the same from where you sit. So the sections below describe what each one looks like, but you usually won’t know which applies until you’ve heard the reasons from your manager.
Was it the work?
Sometimes the decision really did turn on the work. The new role may need things you haven’t shown yet, such as running a project from start to finish or managing a budget. The evidence for this kind is specific. Whoever decided can name the gap and point to a piece of work where it showed, and the same gap would show up again if you were assessed tomorrow.
A general sense that you weren’t quite ready doesn’t count as evidence, because “not ready” with nothing attached could point to any of the five causes. If the work was the reason, you should be able to name the missing thing in one sentence once you’ve talked to your manager. If nobody can name it, the cause is probably somewhere else.
Was it how your work was seen?
This is the cause people find hardest to accept, because it feels unfair. You did the work, but a promotion is usually decided by people who only see part of it. Some of them may never have worked with you directly. So the question isn’t only how good your work was but whether the people in the room could describe what it achieved.
Being very good at your current job also isn’t always what’s being chosen. Alan Benson, Danielle Li and Kelly Shue studied sales workers who moved into management. Their paper, published as “Promotions and the Peter Principle”, found that firms promoted their best salespeople even when other traits were better signs of who would manage well. Current results are also the easiest thing for the people deciding to see.
The same authors later studied ratings of “potential” at a large retail chain. Those ratings helped decide who got promoted, and women received lower potential ratings than their later performance supported. That matters here because potential is a judgment about the future, and nobody can judge the future of work they haven’t seen.
That leads to a plain question you can ask yourself. If someone two levels above you had to explain your best result from this year, could they do it and say what changed because of it? If the honest answer is no, the decision may have turned on visibility rather than ability. The guide to communicating your impact at work covers how to describe results so other people can repeat them.
Was it a sponsorship gap?
A sponsor isn’t the same as a mentor. A mentor gives you advice, while a sponsor uses their influence to speak for you when decisions are made, often in rooms you’re not in. Herminia Ibarra, Nancy Carter and Christine Silva drew this line in a 2010 Harvard Business Review article on graduates of top MBA programs. The women in their study had plenty of mentoring but less sponsorship, and they were promoted less often than the men. Ibarra’s own write-up of the research explains the difference in more detail.
The distinction matters well beyond that study. In many companies a promotion is settled in a meeting of senior people, where someone says they’d back a candidate or nobody does.
So think about the person who got the role. Who spoke up for them? It might have been their manager, a senior leader they’d worked with or an important client. Now ask who spoke up for you. If you can’t name anyone, that gap may have mattered more than any skill.
This isn’t about being liked, since plenty of well-liked people have no sponsor at all. A sponsor is someone who has seen your work closely enough to stake some of their own credibility on it. Building that kind of influence takes time, and it usually starts with work that a senior person sees for themselves.
Was it structure or timing?
Some decisions aren’t about the candidates at all. The headcount may have been cut after the role was posted, so only a smaller version got filled. A budget may have allowed one promotion across two teams. The role may have been shaped around a particular person before it opened, which happens when a leader already has someone in mind. Or a reorganization may have moved the job somewhere you weren’t.
If the cause was structural, nothing in your work would have changed the result. That’s partly good news, because it means the decision says little about you. But it also means a skills plan is the wrong answer, because there’s nothing in you to fix. What matters instead is when a role like this will open again.
Was it bias?
Sometimes a decision turns on who you are rather than what you did. It could be about your gender, race or age. It could also be about a disability, your religion or another part of who you are. This is a real possibility, and it deserves the same care as the other four. You shouldn’t wave it away, but you shouldn’t assume it either.
Bias usually shows up as a pattern rather than in a single decision. You might see criteria that changed partway through, or were applied to you more strictly than to others. You might notice that people who share a characteristic keep missing out, or hear remarks tied to that characteristic. One decision on its own rarely shows which cause it was.
If you think bias played a part, keep a dated record of what happened and what was said. Stick to facts, and only use information you’re entitled to keep. Read your company’s own policy and find out how it asks people to raise concerns.
The rules on discrimination at work differ from place to place, including between the US, the UK and India. So get advice from someone qualified in the rules where you work. Time limits can apply, which is a good reason to get that advice early.
You don’t need a different approach with your manager. Ask the same questions anyone else would ask and don’t open with an accusation. Whatever your manager tells you becomes part of your record either way.
How do you ask your manager what the decision turned on?
This conversation matters more than it might seem to. Jason Shaw, Erin Wild and Jason Colquitt combined the results of many studies on how explanations change the way people react to decisions. Their review, published in the Journal of Applied Psychology in 2003, found that explanations helped most when the outcome was unfavorable. So asking for an explanation is a reasonable request, and a good one can help both of you.
When and how do you set it up?
Wait until the first 48 hours are behind you, and then ask for a scheduled conversation rather than catching your manager after a meeting. Tell them the topic when you ask, so it doesn’t feel like an ambush. You could write something like: “Could we find 30 minutes this week? I’d like to understand what the promotion decision turned on, so I can plan for the next one.” The last part matters most because it tells your manager you’re looking forward, which makes it easier for them to be honest with you.
Bring your lists from the first 48 hours. You don’t need to read them out, because they’re there so you remember which questions you couldn’t answer on your own.
What do you ask?
Two questions do most of the work. The first is what the decision turned on. The second is what would need to be different next time.
Ask the first one in a way that invites a real answer: “What was the deciding factor between me and the person who got it?” That’s easier to answer than “Why didn’t I get it?”, which can sound like a challenge to the decision. A manager who feels challenged tends to defend rather than explain.
Next comes the second question: “If the same role opened in six months, what would need to be different for me to get it?” This moves the conversation from the past to the future, which pushes the answer toward something you could act on.
Whatever comes back, try to pin it to something you could see and a date. Say your manager tells you that you need more visibility with senior leaders. Ask what that would look like in practice and when they’d expect to see it. “By the mid-year review” is something you can plan around, but “at some point” isn’t.
What does a real answer sound like, and what does a vague one sound like?
“It was really close, and the timing just wasn’t right.” That’s what Megan heard when she asked why she hadn’t been made a senior analyst. She’s an illustrative example rather than a real person, but the line is a very common kind of answer. It sounds kind, but it doesn’t name anything, so Megan left the room with nothing she could act on.
A real answer is specific. It names the piece of work, the criteria or the comparison. Here’s what that might have sounded like for Megan: “The other candidate led the vendor migration, and the panel wanted someone who’d already run a cross-team project. You haven’t had that chance yet.” Megan might disagree with that reasoning, but she could act on it because she now knows what the gap is.
Vague answers lean on stock phrases. “Not quite ready” and “a really tough call” are typical, and so is “keep doing what you’re doing.” But a vague answer is still information, because it often means one of two things: either the criteria were never clearly defined, or the decision wasn’t really your manager’s to explain. Both suggest the cause may not be the work.
So don’t accept the vague answer and leave. Ask one follow-up that invites a specific reply, such as “When you say timing, what would have needed to be different?” If that still gets nothing, thank them and write down what was said. A manager who can’t be specific after two tries has told you something about how the decision was made.
It helps to say these questions out loud before the real conversation, especially the follow-up to a vague answer. Merlin can play your manager and give you the brush-offs, so you can practice staying calm and specific.
What if your manager says it wasn’t their call?
Sometimes the honest answer is that someone else decided. Your manager may have put you forward and been overruled. That’s frustrating, but it’s useful to know.
Ask who made the decision and what they weighed, and then how you can be considered next time and whether your manager can help you get in front of the person who decides. You’re trying to learn how the process works, and going over your manager’s head now would cost you the one person who has to keep putting your name forward.
If your manager blocked you or never put you forward at all, you’re in a different situation. The guide on dealing with a bad manager covers what to do next.
What do you do with the answer?
Once you know what the decision turned on, the response follows from it. The table matches what you heard in the conversation to what you do next.
| Kind | What the conversation told you | What to do next |
|---|---|---|
| The work | Your manager named a gap and tied it to a real piece of work | Write a skills plan with dates. Name the gap, the project that would close it and when you’ll review progress together. |
| How your work was seen | The people deciding couldn’t describe your impact | Work out who will be in the next decision. Then find ways for them to see your results directly. |
| Sponsorship | The other candidate had a senior person speaking for them, and you didn’t | Do work that a senior person sees up close. Later, ask them whether they’d back you. |
| Structure or timing | The role was cut, reshaped or set up for someone else | Ask when the next opening is likely and who decides it. Then check back on that date. |
| Bias | The criteria shifted or were applied to you differently | Keep your dated record and get qualified advice, as described above. You can still do the other steps alongside it. |
If two causes applied, do both. The plans fit together well, because most of them come down to work that the right people can see.
How do you work alongside the person who got the role?
The first few days after the announcement are when people watch you most closely. Your colleagues know you wanted the role, so they’ll read your behavior for signs of how you’re taking it. That isn’t entirely fair, but it’s normal. So it’s worth planning for.
Congratulate the person who got it, and do it early. A short word in person or a direct message works better than a public post in the team channel, which can look like a performance. You don’t have to mean every word yet, only be decent.
They applied for a role and got it, so the decision isn’t their fault. If you treat them as the cause of your disappointment, the next few months will be harder for both of you.
Say very little about the decision in public. If someone asks how you feel, a short and honest answer works. You might say: “I wanted it, and I’m disappointed. But she’ll do well, and I’m talking to my manager about next time.”
Leave it at that, and don’t re-argue the decision with teammates, even the ones who agree with you. Those conversations travel, and each one makes it more likely that your reaction becomes the story rather than your work.
It’s harder when the person who got the job is now your manager, because last week you may have been peers. Keep it about behavior, and give them the same reliable work and the same courtesy you’d give anyone in that seat. If you disagree with a call they make, raise it the way you would with any manager, and don’t let it turn into a comment on whether they should have the job. If you’re easy to work with, they’ll notice, and so will the people who decide the next promotion.
When does being passed over mean it’s time to go?
Sometimes the investigation gives you an answer you don’t want, and the conversation shows that nothing is going to change. The structure may be fixed, with no role at the next level for years. There may be no one senior who could sponsor you, however good your work is. Or there may be a pattern of bias that the company shows no sign of dealing with. Diagnosing the cause won’t fix any of those, but it does tell you that this job can’t give you what you came for.
That’s a real outcome, and there’s no need to argue it away. Some people stay anyway for good reasons of their own, while others decide to go. If you’re weighing it up, this guide covers when sticking with something pays off and when it’s costing you too much. If the next level here is a management role you don’t want, read about growing your career without becoming a manager.
How do you recover your standing afterwards?
After the first week, the bigger risk is going quiet. You don’t need to look delighted, since acting perfectly content rarely convinces anyone. But if you stop speaking up in meetings or stop volunteering for things, people may assume you’ve checked out, and that view can follow you into the next decision.
What helps is steady and a little boring. Keep doing visible work at the same standard and speak up in meetings as you did before. Follow through on whatever you agreed with your manager, and let them see you do it. You can disagree with a decision and still work well after it. The guide to disagree and commit explains how that works once you’ve lost the argument.
After that, go back to the lists you wrote in the first 48 hours. By now most of the questions on them should have answers, which tell you which kind of passed over it was and give you a starting point for your next ask. You can show what was missing, what you’ve done since and the date you agreed to review it, so the next conversation is a check on a plan you both agreed to rather than a fresh request. The guide to asking for the project or the promotion you want covers how to make that ask, so this one won’t repeat it.
Put a date in your calendar now, about three months out, to book that conversation. It helps to say the ask out loud before you make it. Merlin runs natively in Slack and Microsoft Teams, so you can try a few versions first and hear which one sounds like you.
Practice the ask with Merlin before you book the meeting.