Manager conversations · Guide

How to Tell an Employee They Didn't Get the Promotion

Answer in the first fifteen seconds, give the real reason, handle the four reactions, and close with a development path you actually control. Written for managers who do not have an HR partner to rehearse with.

2026-09-04 · 8 min read

Run this scenario out loud, free, no account

Pick the role. You get five scenario prompts written for it, you answer each one out loud into your microphone, and you get scored written feedback on clarity, structure, and how you handled the moment. Two minutes to see what the platform scores before you put a team on it.

Putting an employee on a PIP
Denying a raise request
Underperformance after a strong year
Managing former peers
Missed deadline
Telling someone they did not get the promotion
Feedback to a defensive employee
Termination for cause
Delivering layoff news
Attendance problems
Mediating conflict between two employees

Situations you will get: the employee asks why the other person got it; the employee says the process was unfair; the employee gets visibly upset; the employee asks whether they should look elsewhere; the employee asks for a timeline you cannot promise.

Five prompts. About ten minutes.

Voice, not chat
No account
Scored feedback
Same rubric your team would use

What is actually at stake in this conversation

The decision is already made, so the conversation cannot change the outcome. What it decides is whether the person stays, and on what terms. Internal candidates who get a bad rejection conversation start job searching within weeks, and the ones who leave are disproportionately the ones you wanted to keep, because the people confident enough to apply internally are confident enough to apply externally.

The conversation also gets watched by people who are not in the room. The candidate will retell it, roughly accurately, to the coworkers who knew they applied. You are writing the story your team tells about whether trying for more at this company is safe.

So the bar is specific: the person should leave knowing the answer, knowing the real reason, and knowing what would make the answer different next time, without a single line they can quote later as a promise you did not keep.

The four ways managers get this wrong

  • Burying the answer. Two minutes of appreciation for their candidacy before the verdict is two minutes of hope you are about to take away. They know why the meeting exists. Answer in the first fifteen seconds.
  • Blaming the process. "It was a really strong pool" and "leadership went another direction" are sentences designed to make the messenger comfortable. They tell the candidate nothing, and worse, they signal that the real reason is unsayable, which reads as either politics or something damning.
  • Manufacturing a gap. If the honest reason is that the other candidate was stronger in one area, say that. Inventing a development need to justify the decision sends the person off to fix something that was never the issue, and they find out eventually.
  • Promising next time. "You are next in line" feels kind and costs you the relationship when the next role goes to someone else. You do not control the next pool. Commit to what you control: the development, the visibility, your advocacy.

How to open it

Book it as a private conversation within a day of the decision being final; internal candidates should never learn the outcome from the announcement. Then answer immediately:

"I want to tell you directly: we chose Sam for the team lead role. I know that is not the news you wanted, and I want to walk you through how the decision got made and what I saw in your candidacy, because I think you should hear both."

Then the real reason, in one or two sentences, framed as the comparison it actually was: "The deciding factor was client-facing escalation experience. Sam has run two years of it; that showed up in the panel." Specific enough to be useful, short enough that it does not become a re-argument of the decision.

Then stop and let them react. The first reaction is rarely the real one; give it room before you move to what comes next.

The four responses to expect, and what to do with each

  • The comparison question. "What does Sam have that I don't?" Answer the version you already prepared, about the role's requirements, and decline the version about Sam's flaws. "I am not going to run down Sam's file with you, and I would not run down yours with them. The deciding requirement was X."
  • The fairness challenge. "Was this already decided before the interviews?" If the process had a real front-runner, do not insult them by denying it; describe what the panel actually weighed. A candid answer about an imperfect process beats a clean answer they do not believe.
  • The quiet exit signal. "Okay. Thanks for telling me." Flat acceptance usually means the processing will happen tonight, somewhere else. Leave the door open explicitly: "I want to talk again next week when this has settled, because I have specific thoughts about your path here."
  • The direct question about leaving. "Should I be looking elsewhere?" Do not flinch and do not oversell. "I want you here, and I think the path I am describing is real. You will make your own call, and I will be straight with you either way."

Closing it, and the follow-up that decides retention

Close with the development commitment, stated in observables you control: "Over the next two quarters I will put you on the escalation rotation and have you run the client QBR in March. When the next lead role opens, that gap will not be the reason." No promises about outcomes; concrete promises about opportunities.

Then keep the follow-up meeting you offered, and keep the commitments visibly. Retention after an internal rejection is decided in the ninety days after the conversation, not in the conversation itself. The candidate is watching whether the development plan was real or a soft landing.

If you manage the person who did get the role, the first weeks matter there too; the promoted peer now manages people who wanted their job, and our team lead promotion guide covers that transition from the other side.

How Capstone Workforce fits

Managers get better at this by running it more than once.

Capstone Workforce lets a manager rehearse this exact conversation against an AI persona that reacts the way a passed-over candidate actually does, then scores the attempt on clarity, composure, and whether the commitment was specific.

Next step

See how manager conversation practice works

For owners, ops leads, and first-time managers

Get the manager conversation guides as we publish them

Practical walkthroughs for the conversations managers dread: denied raises, PIPs, terminations, attendance, conflict between reports. One situation at a time, with the actual language that works.

No spam. Unsubscribe with one reply. We use your email only to send the platform briefing and PDF companions.

Frequently asked questions

Should I tell them before or after the winner is announced?

Before, always, and privately. An internal candidate who learns from the announcement email learns two things: they did not get it, and they were not worth a conversation. The second one is what they resign over.

What if the real reason is something I cannot share?

Share the shareable layer honestly and say plainly that some inputs are confidential, rather than inventing a substitute reason. "There were factors in the decision I cannot walk through, and the part I can tell you is X" survives later scrutiny. A manufactured reason does not.

What if I disagreed with the decision myself?

Do not say so. Undermining the decision buys you a moment of rapport and costs the candidate their belief in the process and in your influence. Deliver the decision as the organization's, describe what was weighed, and put your energy into the development path you control.

How do I keep them from quitting?

You cannot guarantee it, and trying to guarantee it produces the over-promises that backfire. What measurably helps: hearing it first and privately, hearing a real reason, a development plan with named opportunities and dates, and the follow-up meeting actually happening. All four are in your control.

They asked for the interview feedback in writing. Should I provide it?

Provide the development summary you committed to, in writing, framed forward: the requirement gap and the plan. Do not forward raw panel notes or scores; those documents were written for a decision, not for development, and they read differently outside that context.

For your team

Rehearse this conversation before you have it for real

30 minutes. Bring the situation you are actually facing. We will show you how the practice scenario runs, what the scoring picks up, and what it costs for a team your size.

CapstoneWorkforce
For TeamsPricingSign In

Last updated: 2026-09-04