Get Promoted

Promotion denied? Ask these 9 questions next

How to tell a gap you can close from a role that will never open, and what to say when the feedback is vague.

12 min read

You got the no, and the explanation was probably one vague sentence. Most people do one of two things next: accept it and quietly start job hunting, or push back in the same meeting while they're still upset. Both waste the follow-up conversation, which is where you find out whether this decision was about a gap you can close, evidence nobody saw, a cycle you can wait out, or a role that doesn't exist.

This article gives you nine questions for that follow-up conversation, scripts for the most common vague answers, and warning signs that the path you're being offered isn't real. If you haven't actually made the ask yet, read how to ask for a promotion first; this article is about what to do after a no.

The advice comes from Alisa Cohn, an executive coach who trains managers to deliver these decisions; Nikhyl Singhal, who ran product at Meta and was CPO at Credit Karma; Claire Vo, a three-time CPO; Ethan Evans, a retired Amazon VP; and Sarah Ellis, co-founder of the career consultancy Amazing If.

Take the first reaction outside the company

Sarah Ellis, co-creator of the "squiggly career" framework, says the first step after a denial is naming what you're feeling, and doing it with someone who doesn't work with you. You'll ask better questions once you've talked through the anger, embarrassment, or shame with someone safe.

Working It: how to get ahead without getting promoted. This one is audio only. Sarah Ellis's advice is at 4:04; the player starts from the top, or open it on Apple Podcasts cued to 4:04.

"The first thing that we should do, which is name the emotions that we're feeling, but probably not to somebody that we work with... I think having a thinking partner for this process is very useful, and I do think someone outside of the immediate situation often does help."
Sarah Ellis, co-founder of Amazing If · Working It, Financial Times (4:04, audio)

In the first conversation, get the headline reason and buy yourself time. You don't have to build the whole plan while you're still processing the disappointment.

What to say first

"I'm disappointed, and I want to understand the decision well enough to respond constructively. Could you give me the headline reason now? I may need time to process before we build the next plan."

Executive coach Alisa Cohn role-plays these conversations from the manager's side. In her version of a well-delivered no, the manager states the answer, explains the reason, and commits to a path forward. Listen for those three parts in your own conversation, because whichever ones are missing are the ones you'll need to ask for.

A manager modeling the denial. The player below is queued to 25:56, the exact moment Alisa Cohn role-plays how a manager should deliver a no. Watch on YouTube.

"Matilda, I know this is going to be challenging for you to hear. I know you were hoping to get that promotion, but I want to let you know that we are going to actually be looking for an external candidate. I want to give you a few thoughts about why."
Alisa Cohn, executive coach · Lenny's Podcast

Sort the denial into four types

Most explanations fall into four categories, and your follow-up plan depends on which one you're facing:

Four denials, four next questions

  • Readiness: the people deciding see a specific gap in behavior, scope, or results. Ask what observable evidence would close it.
  • Visibility: the evidence exists, but the people deciding haven't seen or credited it. Ask who lacked which information.
  • Timing: a formal cycle, budget, or another candidate affected this decision. Ask for the next real decision date.
  • Structure: the organization has no role, level, or business need that your performance can unlock. Ask what would have to change for the role to exist.

Nikhyl Singhal, former Meta VP of Product and former Credit Karma CPO, warns against jumping straight to "the company is dysfunctional." Sometimes that's the right diagnosis, but his advice is to start by assuming the decision was correct and testing it against the evidence. He also points out that your manager's feedback may not be the full picture: a manager can be positive while a skip-level leader has specific concerns that never reached you.

The Skip: when your manager and your skip-level disagree. The player below is queued to 36:56, the exact moment Nikhyl Singhal takes a question from a team lead whose manager gave no critical feedback while the skip-level had specific concerns. Watch on YouTube.

That gap changes the diagnosis. Ask whose assessment affected the decision and whether you've been working from the same standard they used.

Ask the nine questions in three rounds

The order matters. Establish what happened first, translate it into work you can actually do, then test whether the organization will give you access and a decision date.

Round one: find the reason and what you can change

  1. What was the primary reason for the decision? Get the headline before collecting ten smaller observations. Was the constraint readiness, visibility, another candidate, headcount, timing, or organizational need?
  2. Can strong performance realistically change the outcome here? This exposes structural limits before they turn into an endless development plan.

Round two: turn the reason into evidence

  1. Which expectations for the next level am I already meeting? This captures what you're already doing well and gives you an accurate starting point.
  2. Which one or two gaps mattered most? Prioritize the behaviors that actually affected the decision. General requests for "more strategy" or "more leadership" give you nothing to act on.
  3. What behavior or evidence would show I closed each gap? Turn the label into something people can see you do. "Strategy" might mean framing a multi-quarter decision or connecting a roadmap choice to a business outcome.
  4. Which opportunity will let me produce that evidence? Ask for the project, decision, or forum that gives you the scope you need.

Round three: test the path

  1. Who else needs to see or support my work? A calibration group may need stronger evidence, cross-functional partners may need direct experience with your judgment, or a sponsor may need to advocate for the role.
  2. When will we formally reassess? Get a calendar date, and be clear about whether it's a progress review or a promotion decision.
  3. Which organizational constraints should I understand? Ask about budget, role availability, promotion cycles, company performance, and whether the work actually requires the next-level role.

Turn vague feedback into observable behavior

"You need to be more strategic."

What to ask

"Can you point to a recent situation where my approach was below the next-level expectation? What would a next-level response have looked like, and what upcoming decision could I lead to demonstrate it?"

"You need more visibility."

Adam Goyette learned this one the hard way: an intern got the promotion he wanted. His boss knew his work, but the founders couldn't connect business results to him. His fix was to start sharing concise reports that tied experiments to revenue and named what the team learned.

The fix for missing visibility. The player below is queued to 17:03, the exact moment Adam Goyette says it. Watch on YouTube.

"I think the biggest thing is I started celebrating my wins, like, publicly."
Adam Goyette, former VP of Demand Generation at G2 · Delivering Value

Ask who was missing evidence, what they were missing, and where you should post your results next time. Treat visibility as one possible diagnosis. Bias, politics, and inconsistent standards can also be behind a no, so keep testing the explanation against what you can verify.

What to ask

"Visibility with whom, and about what? Do people need to see my results, experience my judgment, or build more cross-functional trust with me?"

"There just wasn't room this cycle."

What to ask

"If my performance stays strong, when could room realistically exist? What would cause that date to move? Which parts of the plan are within my control?"

"Another candidate was stronger."

What to ask

"Which evidence made the difference in that decision? I'd like to understand the standard without comparing personalities, then identify the experience I should build before the next opening."

"Keep doing what you're doing."

What to ask

"I'm glad the work is valued. What additional evidence would make the next decision different? If the constraint is structural, I'd like to understand that directly."

Ask the nine questions out loud first

Work Coach plays your manager giving the vague answer, so you can practice the follow-up that makes it specific. It also flags where you softened the question on the way out of your mouth.

Start Free Trial

2-week trial, no credit card needed. Your data is never shared with your employer.

Test whether the path is real

Before you decide the readiness explanation is cover for something else, consider that it might be true. Claire Vo, a three-time CPO, has seen ambitious people get scope that left them ineffective or unhappy, and she's blunt about her own record on this.

The case for a real readiness concern. The player below is queued to 18:12, the exact moment Claire Vo says it. Watch on YouTube.

"I've never regretted promoting somebody too slowly. I have regretted promoting somebody too quickly."
Claire Vo, three-time CPO and founder of ChatPRD · Lenny's Podcast

So ask for examples before rejecting a readiness concern. A valid constraint should still come with clear scope, timing, and a next review date. A weak path gives you encouragement but not the opportunity or the date you'd need to act on it.

Put the plan in writing

The Mochary Method recommends regular "absolute feedback" throughout the year: a current rating, specific positive behavior, and the actions required to reach the next level. Ask whether the promotion criteria existed before the denial, and request monthly written calibration afterward. Then send a short email summarizing what you agreed.

The follow-up email

Subject: Promotion decision follow-up

Thanks for walking me through the decision. I'm writing down the plan so we can check that I understood it correctly.

The primary reason was [reason]. You see me already meeting [expectations]. The two gaps that mattered most were [A] and [B]. I can demonstrate progress through [specific opportunity and observable evidence].

I will [employee action] by [date]. You will [manager action or access] by [date]. The people who need to see the evidence are [names or groups]. We will review progress on [date], and the next formal decision point is [date].

Please correct anything I missed.

The note turns a supportive conversation into a plan you can check. It also shows you fast if nobody owns a step, or if neither of you actually agreed to the dates.

Set your own decision date

Ethan Evans, a retired Amazon VP, distinguishes a real development plan from moving goalposts. His Magic Loop framework for building the case before you ask is covered in how to ask for a promotion; here he's describing what to do when you've asked, you've done the list, and the list keeps growing.

Moving goalposts. The player below is queued to 23:11, the exact moment Ethan Evans says it. Watch on YouTube.

"You start pushing when you're not getting answers, or where the answers start to ring of... you just sort of are getting an ongoing list that keeps changing, or that contains something impossible, like, 'We totally believe you are ready for promotion, there's just one more thing you need to do: you need to be taller.'"
Ethan Evans, retired Amazon VP · Level Up

Ask directly what blocks advancement. If the answer stays implausible or keeps moving, set your own deadline and start learning what the external market values while you keep working the internal plan. A low-growth organization may simply have no next-level role until someone leaves, regardless of your performance.

Watch for these warning signs:

Staying makes sense while the company can explain the standard, give you the opportunity, and keep the review date you agreed on. When that stops being true and your own deadline arrives, leave.

Frequently asked questions

Should I challenge the decision in the same meeting?

Clarify factual errors, then give yourself time to process. Come back with focused questions once the disappointment has settled and you can think clearly about the reason.

Should I ask for a raise instead?

Only if compensation is genuinely the issue. Title, scope, and salary solve different problems. Discuss them separately, after you understand why the promotion was denied.

How long should I wait after a denied promotion?

There's no standard waiting period. The right one depends on the gaps, your access to new scope, and the company's cycle. Agree on a realistic decision point with your manager, and set your own deadline too.

The denied-promotion playbook on one page

Process

  • Talk through the first reaction with someone outside the company.
  • Ask for the primary reason before collecting smaller feedback.

Diagnose

  • Decide whether the denial is about readiness, visibility, timing, or structure.
  • Ask whose assessment affected the decision, including skip-level leaders.

Build the path

  • Turn each gap into observable behavior and evidence.
  • Get the project, decision, or forum where you can produce that evidence.
  • Learn who must see the work and who will advocate for it.
  • Put the plan in writing with owners, dates, and the next decision point.

Decide

  • Set your own deadline for how long you'll work the path if the explanation or date keeps moving.
  • Explore the external market while the internal plan runs.