The Promotion Conversation 1-on-1 Template

Published on August 7, 2026

A promotion conversation gets mishandled in one of two directions, and most managers only ever notice the one they're not prone to. Some bury the actual answer under ten minutes of context and caveats, so the person spends the whole conversation trying to read tone instead of just hearing the news. Others do the opposite: a straightforward "not this cycle" comes out flat, with nothing attached to it, and lands as a much harder no than the manager actually meant.

Both versions cost you something. The first wastes the moment where clarity mattered most. The second can cost you the person entirely, especially if what was actually a timing problem gets heard as a verdict on their ceiling. What follows is a structure for this conversation that avoids both: what to actually say, in what order, and why it matters.

1. Say Clearly Where Things Stand

Managers hedge to soften a hard answer or to avoid overpromising a good one, and it backfires in both directions. Hedge on good news and the person leaves not quite believing it. Hedge on bad news and you just extend the anxiety while they wait for you to actually say the thing. Leading with the plain answer isn't blunt, it's the only version of this conversation that doesn't make someone sit through their own verdict in suspense.

What to actually cover:

• Say the actual outcome, or where things currently stand if it isn't decided yet, in the first minute, before any explanation.
• If it's good news, say it plainly enough that there's no ambiguity to second-guess later.
• If it isn't happening this cycle, say that directly too, rather than talking around it until they have to ask outright.

2. Walk Through What the Case Actually Needs to Show

"Keep doing what you're doing" isn't a plan, it's a placeholder for a conversation you haven't had yet. A promotion case at most engineering organizations has to demonstrate a specific level of scope and impact, and if the person doesn't know what that actually looks like in practice, they're left aiming at a target that only exists in your head or in a leveling document they've never read closely.

What to actually cover:

• Name the specific scope or level of impact the next level actually requires, not a general sense of "more."
• Point to real examples, from their own work or from someone else's recent promotion, of what that scope looked like in practice.
• Be honest about which parts of the case are already strong and which parts are still thin, rather than treating the whole thing as one undifferentiated block.

3. Separate "Not Yet" From "No"

This is the section that matters most, and the one managers skip under time pressure most often. A timing problem, wrong cycle, team not ready to lose the scope, budget frozen, and a capability problem, not ready for the level, are two completely different messages, but they sound identical if you don't explicitly separate them. Someone who hears a timing problem as a capability verdict tends to start quietly job hunting, and by the time you realize what happened, the conversation you actually meant to have is no longer the one that landed.

What to actually cover:

• State outright whether the delay is about timing and circumstances, or about the case itself not being there yet. Don't leave them to infer which one it is.
• If it's timing, name the actual constraint causing the delay, so it doesn't read as an excuse.
• If it's the case itself, go back to what's specifically missing rather than leaving it as a vague sense of "not ready."

4. Set a Timeline They Can Actually Rely On

"We'll see how next cycle goes" isn't a timeline, it's a way of ending the conversation without committing to anything. Without a real checkpoint, the next promotion conversation starts from the same uncertainty as this one, and the person has no way to judge whether they're actually making progress or just waiting indefinitely.

What to actually cover:

• Set an actual date or cycle for the next check-in on this specifically, not a vague "soon."
• Say what you'll be looking for by that date, specific enough that you could both agree afterward on whether it happened.
• If the timeline depends on something outside your control, headcount, a reorg, budget, say so plainly instead of implying it's entirely a matter of their performance.

5. If the Answer Is No, Make the Path Forward Concrete

A conversation that ends on pure disappointment teaches someone that promotion conversations are just bad news delivered on a schedule. Even when the honest answer is no, or not soon, leaving them with something concrete to work toward is what determines whether they stay engaged or start quietly checking out.

What to actually cover:

• Name one or two specific things that would meaningfully change the case, not a general instruction to keep working hard.
• Ask what support would actually help, a stretch project, more visibility with a specific stakeholder, and be honest about what you can actually provide.
• End by confirming when you'll revisit this again, so the conversation closes on a next step instead of just a decision.