👋 I'm Parsa Jiravand — I work in IT, and this is Best Practice. One article every day, one soft-skills episode every week. It all lives at bestpractic.org — come join us.
The moment
You don't usually find out you didn't get the promotion. You find out someone else did. A title changes in the org chart tool before anyone tells you directly. Someone's email signature updates. A channel posts congratulations and your name isn't in it, and you have to work backward from that to the thing that actually happened to you, which is a no you were never formally given.
The sting isn't only the no. It's that you have to assemble it yourself, out of other people's good news, on a day you weren't braced for it.
What's actually happening
The conversation where you hear about it is not the conversation where it got decided. That one happened weeks earlier, in a room with your manager and some number of other managers, going person by person against a number of open slots that was fixed before anyone discussed anyone's actual year. It is a budget meeting wearing a performance-review costume.
This matters because it changes what the no is actually telling you. A room with five strong candidates and two slots produces three disappointed people regardless of how any of them performed. If you've gone through a headcount freeze or a round of cuts this year — and a lot of teams have — the number of slots can be smaller than it was the last time you were up for this, which means "ready" stopped being sufficient even where it used to be enough on its own. None of that shows up in the sentence you get told, which is usually some version of "not quite yet," delivered as if it were a statement about you alone.
Your manager's job in that room was to argue for you. Some managers are good at this — they walk in with your specific wins written down, they've pre-briefed the room, they know which objection is coming and have an answer ready. Some managers are bad at it, or didn't prepare, or got out-argued by someone representing their own report harder than yours was represented. You cannot see which one happened to you from the outside, and the answer changes what you should actually do next.
What works
The question most people ask is "why not me," usually within the hour, while they're still raw. It's an understandable question and it gets you almost nothing, because it's shaped like an accusation and your manager will answer it like one — with reassurance. "You're doing great, it's close, next cycle for sure." That sentence costs your manager nothing to say and commits them to nothing either.
Wait a few days, past the part where your face gives you away, and ask a different question: "What did she do differently that I should be doing now?" That's not an accusation, it's a request for a comparison, and a comparison is specific in a way reassurance can't be. A manager who has an honest answer will give you something concrete — she's been running the migration project end to end, she's the one three teams page when something breaks, she started writing the design docs before anyone asked her to. A manager who doesn't have an answer will dodge into more reassurance, and that dodge is itself information: it tells you they didn't actually advocate with specifics, which tells you something about the quality of representation you're getting in that room whether or not you deserved the promotion.
A second question, for later in the same conversation: "If we ran this again in six months, what's the one thing that would be different?" This is the question that turns a vague "next cycle" into something you can actually act on or actually check up on. If the answer is specific — ship this, lead that, get visible to this other team — you now have a target. If the answer is still vague the second time, that's not you failing to extract information. That's the answer.
Where it backfires
Asking "is this close?" feels like it should get you something useful, and it usually gets you kindness instead. Most managers, asked directly whether it was close, will say yes, because saying no to someone's face in that moment is harder than saying yes, and because "it was close" is true of almost every decision if you squint — there's always a version of events where it goes the other way. Treating "it was close" as real information is where people talk themselves into waiting another full cycle for something that was never actually close, because the kind answer and the accurate answer aren't the same answer, and your manager picked the kind one.
The "is this a 'not yet' or a 'not here'?" question exists specifically because it closes that door. It forces a choice between two answers, and both of them are useful. "Not yet" with specifics is a real runway. "Not here" — meaning this team, this manager, this room, isn't going to produce it for you regardless of what you do — is also real information, and it's the one people are most likely to avoid hearing because it means the fix isn't something you can execute your way out of.
The part that's uncomfortable
Here's the thing nobody says in the moment: the person who got it might genuinely be better at the job than you, or they might be better at being seen doing the job, and those are different skills that this process does not reliably tell apart. You don't get to know which one happened, and spending real time trying to litigate it in your own head is not a good use of the only thing you actually control, which is what happens from here.
It's also true that whether this question even gets you a useful answer depends entirely on whether your manager has real standing in that room and is willing to spend it advocating for specifics instead of vibes. If they don't, or won't, better questions from you don't fix that — that's not a you problem, and it's not solvable by trying harder to ask well. Some of what decided this was budget, and timing, and who else happened to be up for a slot this cycle, and none of that is something a better conversation un-decides.
Monday
Don't make the big move yet — not the frustrated message, not the quiet quiet-quitting, not deciding anything permanent on the week you're still stinging. Write down, this week, the one sentence you'd want said about you in the next room like that one — the actual thing, not the vague "I work hard" version — and send it to your manager as a statement of direction, not a complaint: "here's what I'm building toward before the next cycle." That puts something concrete in their hands before the next meeting happens, instead of leaving them to reconstruct your case from memory the way you had to reconstruct the no.
And if you ask the specific question and get the vague answer twice — once now, once next cycle — that's not bad luck repeating. That's your answer, said the only way it was ever going to get said.
🚀 Want more like this? Every guide, playground, and quiz lives on bestpractic.org — open it and sign up free so the next one finds you.
Thanks for reading! Let's stay connected:
- ⭐ GitHub — follow me and star the projects: github.com/parsajiravand
- 💬 Discord — join the frontend best-practices community: discord.gg/d9KRhuAwQ
- 📸 Instagram — frontend best practices, daily: @bestpractice___
🤝 Want to make something with us? Write a piece, come on the podcast, or bring an idea that should exist — bestpractic.org/collaborate.
And if this one helped, send it to the person you know who needs it this week. That's what keeps these coming.
