The announcement goes out at nine. Congratulations to someone else, and your name sits in the same thread. By ten you are on a call with the person who got it, and you have to say something.
There are two ways this goes wrong from here. You say nothing, decide the whole thing was political, and carry it quietly for the next twelve months. Or you reply that afternoon while it still stings, and the meeting turns into a case for why the decision was wrong. Both cost you the only useful thing available right now, which is information.
Why you were passed over is a longer answer, and the passed-over-for-promotion guide works through all five reasons. This page is narrower. It is the conversation itself: what to ask, when to ask it, and how to leave the room with something you can hold people to.
The criteria were never written down
John Beeson wrote a piece for Harvard Business Review in June 2009 titled “Why You Didn't Get That Promotion” [1]. His argument was that these decisions look arbitrary and political from below because the criteria for moving up live mostly in people's heads rather than in a document you can read, and the feedback afterward stays vague enough that nobody can act on it. That gap is where you are standing this morning.
So the goal of the next conversation is not to reverse a decision that has already been announced. It is to get the list you were never handed. Everything else on this page follows from that one shift.
Ask for the meeting, not the appeal
Do not send the request the same day. Give it a day, maybe two, and let the ask point at the next cycle instead of this one. Keep it small. Thirty minutes, one topic, requested in writing. Managers say yes to that meeting. They dodge the one that smells like an appeal.
If you want the fuller version to open with, this is the one I hand people.
“Thank you for telling me directly. I am disappointed, I put real work into getting ready for that role, and I am still in this with the team. What I want from you is the specific gap: the competencies or the scope the committee needed to see and did not see from me. Can we take thirty minutes next week so I can hear it clearly and start closing it?”
Notice what that does. It names the disappointment once, in a single clause, and then spends the rest of its length on the next cycle. Disappointment you name yourself stops being the thing the other person has to manage.
In the room, ask about criteria and stay off the other candidate
The moment you compare yourself to the person who got the role, the conversation changes shape. Your manager starts defending a decision instead of describing a standard, and you leave with a justification rather than a list. Keep the other name out of your mouth entirely. These are the five things to walk out with.
- What did the committee need to see that they did not see from me? That is the whole meeting in one sentence. Ask it first, then stop talking and let the silence do its work.
- Which two of those matter most first? A list of six is a no delivered politely. Two is a plan.
- What does evidence of that look like here? If what comes back is an adjective, push once. Strategic how. Visible to whom. By when.
- What specifically would make me the obvious choice next cycle, and who else needs to see it? The second half of that question matters as much as the first. It tells you whose picture of you has to change, and that is rarely only your manager's.
- Write the answers down in their language, not yours. You are collecting a standard, not composing a rebuttal. Their words are the ones that get repeated in the room you are not sitting in.
If the answer stays fuzzy after you have pushed once, that is information too. It means the decision is being made somewhere you are not, on criteria nobody has written down, and that is a different problem than a skills gap. The pillar covers what to do when the room itself is the constraint.