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.
The recap, and the date that keeps it alive
Close the loop in writing that same afternoon. A short recap: what you heard, in their words, and what you are taking on. The recap is the part most people skip, and it is the part that changes the next conversation. It turns one manager's opinion in a hallway into a written standard. When the next role opens, your manager is reading their own sentences back.
Then put a date on it. Do not ask for a standing check-in, because a recurring meeting with no decision attached settles into a status update within two months. Agree on one specific review in the next 60 to 90 days, with named criteria, so the conversation becomes a plan with a date instead of a maybe that quietly expires.
“Let us revisit this later” is how a passed-over conversation dies a second time. A checkpoint 60 to 90 days out, with written criteria, tells you fast whether the door is open or only politely closed. Either answer is useful to you. A vague one is not.
The Monday after
There is no posture for the team meeting on Monday. Composure is not a face you put on at the door. It is what is left over once you have named the thing somewhere else first.
The sequence I teach for any setback is the R4 framework from Dear Resilient Leader, and it works the same way here. Name what is being tested, out loud, as a fact rather than a forecast. I feel rejected and I feel scared. Then reappraise it into something true and narrow. This was one decision, in one cycle, made on criteria nobody wrote down. Then shrink the goal to something you can finish today, a follow-up sent or one thing posted, and mark it done where you can see it. Name it, prove your strength, reset the pattern, then let the small win count.
I have watched strong professionals carry a single bad quarter for two years, running it back in their heads long after everyone else forgot, letting one loss quietly rewrite the story they tell about their entire career. That is the real exposure in the weeks after a no. Not the standup on Monday.
What this conversation cannot fix
None of this obligates anyone to promote you. Budget freezes are real, and so are reorgs decided three levels above your manager. What the conversation does is move the criteria out of somebody's head and onto a page you can work against, and it gives you a dated test of whether that standard was real.
One boundary worth stating plainly. This is career guidance, not legal advice or HR grievance counsel. If you believe a decision was discriminatory or retaliatory, that belongs with an employment attorney rather than a career article.