How to tell someone they are not getting promoted

What do you actually say first?

You say the decision. In the first thirty seconds, in one sentence, before anything else.

Try something close to this: "I want to start with the decision, because you deserve to hear it straight rather than work it out from my tone. You are not being promoted this cycle. I want to spend most of our time on why, and on what happens next."

That is about fifteen seconds of talking. Everything a first-time manager instinctively wants to do first belongs after it: the praise, the context about headcount, the explanation of how the calibration meeting works, the reassurance that you value them. All of it lands better once the person has stopped scanning your face for a verdict.

The failure mode is the warm-up. You open with how much you appreciate their work, you mention the strong quarter, you note that the process was competitive, and by the time you reach the word "however" they have already heard the answer, and they have heard it while being complimented. Now the compliments are contaminated. They will be remembered as padding around a no.

Say the decision, then stop for a moment and let them have it.

What should you be certain of before you walk in?

Four things. If any of them is missing, move the meeting rather than improvise.

The decision is final. Not likely, not leaning, not pending one more conversation. If it is still moving, you are not having this conversation yet.

One or two reasons, with an example of each. Not five. Two is roughly the most a person can absorb while managing disappointment, and a list of five reads as a case assembled after the fact.

Your honest answer to "what would it take." Decide in advance whether the realistic answer is the next cycle, the one after that, or that this promotion is unlikely in this role. You will be asked. Improvising a timeline you cannot stand behind is how a hard conversation becomes a broken promise.

What you can actually offer. A project, a piece of scope, a named person to learn from, an hour a week of your time. If you would have to ask someone else before committing to it, do not name it in the room.

Write your decision sentence and your reason sentence down beforehand. If you cannot write them in plain language, you do not understand the decision well enough to defend it under pressure.

How much should you explain about the process?

Enough that they can see the decision was made carefully, and no more than that.

Someone who has just been told no will often reach for process questions, because process is easier to argue with than judgment. Who was in the room? Did they see the launch? Was the bar the same as last year? Answer those directly and briefly. Do not narrate the deliberation, do not attribute opinions to named colleagues, and do not offer to share what other people said about their work.

There is one specific move to avoid, and it is the one that tempts new managers most. Do not position yourself as their advocate against the decision. "I pushed hard for you, but I was overruled" feels generous in the moment and is corrosive afterwards. It tells the person that whoever owns their development has no influence over their advancement, and it puts an asterisk on every piece of feedback you give them for the rest of the year. If you were part of the decision, own it: "I was part of this decision, and I think it is the right one."

What makes a reason specific enough to be useful?

A reason is specific enough when the person could repeat it to a peer in their own words, and that peer would recognise the gap.

General reasons sound like this: not quite ready, needs more leadership presence, close but not there, it was a competitive cycle. Each one sounds true and none can be acted on. Worse, a vague reason invites the person to fill in the blank themselves, and the version they invent is usually harsher and less accurate than the truth.

A specific reason names the behaviour, the situation and the effect:

"The gap is scope. You run your own projects well and I have never had to check them. Twice this year, when the work needed someone to pull three teams into a single plan, you flagged the problem to me and waited. People at the next level start that conversation themselves. That is the distance between where you are now and the title."

Test yours before you go in. Can you point to two occasions? Would the person, hearing them, know what they would have done differently each time? If your reason survives both questions, it is a reason. If it does not, it is an impression, and you should go and find the examples before you book the meeting.

What do you say when they ask what it would take?

Answer in observable terms, and give an honest timeline even when the honest timeline is unwelcome.

The useless version is a list of adjectives: be more strategic, show more ownership, raise your visibility. The useful version describes what the promotable version of their work would actually look like: "For the next cycle, I want you to own the migration end to end. You write the plan, you run the review with the other two teams, and you bring me decisions rather than questions. If that goes the way I expect, I will put you forward in the spring."

There are three honest timelines, and you should know which one you are giving before you sit down:

• Next cycle, if specific things happen. Name them, and put a date on the check-in.
• Not next cycle. Say it plainly. "I do not think this is a six-month gap. I think it is closer to a year, and I would rather tell you that now than let you spend six months expecting a different answer."
• Unlikely in this role. This is the hardest one to say and the most important not to dodge. "I want to be straight with you. In this role, on this team, I do not see a path to that title in the next couple of years. If the title matters to you, then the conversation we should be having is about what would."

One thing to never say here: "keep doing what you are doing." They did what they were doing and it produced a no.

How do you respond when they say the decision is unfair?

Work out which of two things they mean, and answer only that one.

If they are saying the process failed them, and they are right, say so and fix it. Their work was not visible to the people deciding. The criteria moved and nobody told them. They were never given the bar in the first place. "You are right that nobody told you the bar had changed. That is my failure, not yours, and here is what I am going to do about it." An owned failure costs you far less than a defended one.

If they are saying the judgment itself is wrong, do not argue and do not fold. You can hold the decision and their reaction at the same time:

"I am not going to try to talk you out of being disappointed. You have every right to feel this. And I am not going to change the decision, because I think it is the right one. What I can do is be much clearer with you about what would change it."

Do not re-litigate the examples one by one. If they dispute a specific fact, and it is a fact rather than an interpretation, take it away: "Let me go back and check that. If I have it wrong, I will tell you, and I will tell you what difference it makes." Then actually go and check, and come back either way.

Fairness objections are a distinct kind of pushback and they do not respond to more evidence — what to do when someone gets defensive sets out why, and what to say instead.

What if they go quiet, or get upset?

Let the silence sit. Their reaction is not a problem for you to solve.

A new manager's instinct in a pause is to keep talking, and every extra sentence in that pause is reassurance that dilutes what you just said. The silence after "you are not being promoted" is the sound of someone absorbing information. Filling it stops them thinking and starts them managing your discomfort. Count to ten if you need to.

If they become visibly upset, name it once and hand them control of the room: "Take whatever time you need. We can stop now and pick this up tomorrow, or we can keep going. Both are genuinely fine." Then let them choose and mean it. Do not touch them, do not make a joke to break the tension, and do not apologise for the decision, which reads as either insincere or as a hint that you might reverse it.

If they go cold and start answering in single words, do not push through the rest of your script. "I do not think much more will land today. I will send you a short summary of what I have said so we both have it written down, and I would like to pick this up on Thursday." Then leave.

What should you never say in this conversation?

Six sentences that feel kind in the moment and cause damage afterwards.

"Nothing is final yet." If it is final, this is a lie with a very short shelf life, and they will remember that you told it.

"This was out of my hands." Even when a committee decided, you own this person's development. The sentence gives away your standing to give them feedback for the next twelve months.

"I fought for you." It invites them to be angry at someone else instead of hearing the reason, and it makes the reason optional.

"You were so close." Usually not true in the way they will hear it. It turns a decision into a near-miss they will expect to be corrected automatically next time.

"I know exactly how you feel." You do not, and it moves the conversation onto you.

"Let's not let this affect the work." Their disappointment is legitimate and the work probably will wobble for a week. This asks them to perform being fine, which is the opposite of what you want.

How do you end the conversation?

With one concrete next step and a date, agreed out loud, in the calendar before either of you leaves the room.

Not "my door is open." Not "let's keep talking about this." The close is the moment the person decides whether they have just had a decision or a dismissal, and a specific commitment is what separates the two.

"Here is what I would like to do. Take the rest of the week and put this down. Next Wednesday, let us block an hour and write the plan for the next six months together. I will bring my draft of what the next level looks like so you can argue with it. I am putting it in the calendar now, while we are sitting here."

One step. One date. Something you control and can genuinely deliver.

What should you do in the week after?

Send a short written summary within a day, then behave completely normally.

The written note does two jobs. It stops the conversation being remembered as vaguer or harsher than it was, and it gives the person something to reread once the adrenaline has drained. Keep it to a paragraph: the decision, the same one or two reasons in the same words you used out loud, the next step and the date. Introduce nothing new. A follow-up note is not the place to add the reason you lost your nerve on in person.

Then hold steady. Two failure modes follow this conversation. The first is quietly disappearing, because the meeting was uncomfortable and avoidance can be mistaken for giving someone space. The second is over-correcting into extra praise and attention, which reads as pity and confirms their worst interpretation of the decision. Run the next one-to-one at the usual time with the usual agenda, and let the fact that nothing has changed do the reassuring for you.

Then deliver the thing you promised, on the day you promised it. Until they see that happen, everything you said in the room is provisional.

None of what you agree here should be new information at the next formal review. If the promotion criteria you have just described turn up as a surprise in that meeting, the problem is the intervening months rather than the review — performance review conversations that actually land covers keeping the two consistent.

What if they start looking for another job?

Some will, and acting on an accurate no is a reasonable thing for an adult to do.

Do not treat it as a betrayal, do not counter-offer in a panic, and above all do not suddenly rediscover that the promotion might be possible after all. A promotion produced by a resignation threat teaches everyone watching exactly how promotions are obtained on your team, and you will spend the next two years dealing with the consequences.

If they tell you they are interviewing, take it seriously and stay honest: "I would rather you stayed, and I understand why you are looking. What I told you about the timeline is still true, and I am not going to change it because you have interviews. If it helps you decide, I will be as concrete as I can about what the next year here would look like."

Some of them will stay. Some will leave, and a few of those would have left anyway, later, with more resentment and less notice. The manager who keeps their credibility is the one who told the truth on Tuesday and did not renegotiate it on Friday.

This is one of the two or three conversations most worth saying out loud before you have it. The sentence that states the decision plainly is the one almost everyone softens into something ambiguous under pressure, and finding that out in the room is expensive — why rehearsing a conversation works explains what changes when you run it once beforehand.