How to Tell a Good Employee They're Not Ready for Promotion

The Conversation Most Managers Dread

Taylor walks into your one-on-one with a list. They've prepared for this. You can tell they practiced it in the car on the way in. They make their case for Staff Engineer, walk through their accomplishments from the past year, and then they look at you.

And they're right about some of it. They've had a genuinely strong year. They ship clean code, they hit their deadlines, their peers like working with them.

They're also not ready. Not yet.

What happens in the next ten minutes matters more for Taylor's career than almost anything else you'll do for them this year. Handle it well and you give them a real development path. Handle it poorly and you either give them false hope with a wishy-washy non-answer, or you crush the ambition that makes them worth investing in. Both outcomes cost you.

Here's how to get it right.

Say the True Thing First

The worst version of this conversation starts with a manager dancing around the answer for five minutes before landing on it. Taylor came in prepared. They asked a direct question. They deserve a direct response.

Something like: "I'm really glad you brought this here. I'm going to be honest with you, and I want you to hear this as me taking your career seriously. You're not ready for Staff yet. That's my honest assessment right now, and I want to explain what I mean by that, because I think the path to getting there is real and it's closer than you might think."

That's it. You said the true thing. You didn't dress it up or bury it. And you opened the door to the more important part of the conversation, which is what "not ready" actually means and what needs to change.

A lot of managers skip the direct statement because they're afraid of the reaction. What they get instead is an employee who leaves the conversation unsure whether the answer was no, maybe, or "work harder and see." That ambiguity is worse than a clear answer. It's disrespectful, even when it comes from a kind place.

Name the Specific Gap, Not the General Concept

Here's where most of these conversations fall apart. The manager says something like, "You need more experience at the next level," or "You need to think more strategically." Taylor nods, says okay, and walks out with no idea what to actually do.

Vague feedback is not feedback. It's a way of sounding like you gave feedback without doing the actual work.

For Taylor, the gap isn't effort or dedication. Those are real. The gap is scope. Senior Engineer is about doing excellent individual work. Staff Engineer is about multiplying the output of others, driving architecture decisions across teams, mentoring other senior engineers, and operating at a level where your influence shapes things you're not directly building.

Say that explicitly. "Your individual contributions this year have been strong, and I mean that. The pattern I need to see more of is you operating across teams. Driving a technical decision that other engineers have to align to. Mentoring a more junior engineer through a hard problem. Owning a piece of architecture that lives beyond your own tickets. That's not a criticism of what you've done. It's a description of what the next level actually requires."

That's a conversation Taylor can do something with. They leave knowing what the target looks like.

Co-Create the Plan, Don't Hand It Down

Here's the part that separates managers who develop people from managers who just assess them. After you name the gap, you don't just hand Taylor a list of things to go work on. You build the path together.

Ask them which of those gaps feels most real to them. Taylor probably already knows. Good engineers have pretty accurate self-assessments when you give them a safe environment to be honest. "If you're being hard on yourself for a second, where do you think the gap is biggest?" You might be surprised what they say.

Then figure out where you can create the conditions for them to close it. That's your job, not just theirs. If Taylor needs to demonstrate cross-team architecture influence, you need to find or create an opportunity for that. A project with real scope. A decision that needs someone to own it. A junior engineer on the team who could use a mentor. You don't just tell Taylor to "seek out more leadership opportunities" and call it a day. You make the opportunities concrete.

Set a 90-day milestone. Something specific and observable. Not "show more leadership" but "lead the technical design review for the API refactor and get sign-off from the Android and iOS teams." Something that, at the end of 90 days, you can both look at and agree on whether it happened.

Then put a follow-up on the calendar. Not "we'll revisit this at your next performance review." An actual date, 90 days out, where you come back to this conversation specifically.

What to Do When Taylor Pushes Back

They might. Some people hear "not yet" and receive it well. Some people hear "not yet" and get frustrated, or quietly feel like they've been passed over for the wrong reasons.

If Taylor pushes back, don't get defensive and don't immediately soften your assessment to reduce the tension. That's the instinct, and it's wrong.

If they say, "I feel like I've been doing Staff-level work already," the right response is to take that seriously. "Walk me through what you mean. I want to understand your read." Maybe they have been doing some of it and you haven't seen it clearly. Maybe they have a different understanding of what Staff-level work means. Either way, that's a real conversation worth having, not a challenge to deflect.

If their frustration is more about the timeline, or about feeling like the goalposts keep moving, acknowledge that directly. "I hear you. And if I haven't been clear enough about what the target looks like, that's on me. Let me fix that right now." Then be specific.

What you don't want is Taylor walking out of there feeling dismissed or patronized. Ambition is good. You want to protect it, not punish it.

The Mistake That Kills the Most Careers

I've seen this version more times than I can count. The manager doesn't want to have a hard conversation, so they say something like, "Keep doing great work and I'll make sure you're considered." Taylor hears "yes, eventually." The manager meant "I don't want to deal with this today." Six months later, someone else gets promoted and Taylor starts updating their resume.

You haven't done Taylor any favors by being vague. You've just delayed their disappointment and eroded their trust in you in the process.

The conversation that feels hard in the moment is actually the kind thing. Telling someone specifically where they are, what the gap is, and what you're going to do together to close it is one of the most valuable things a manager can do. Most people don't get it. Most people get performance reviews full of platitudes and a raise percentage that doesn't quite make sense.

Taylor asked for a real conversation. Give them one.

After the Meeting

Send a follow-up note the same day. Not a formal document, just a short message that captures the key points. What you agreed the gap is. What the next 90-day milestone looks like. When you're coming back to revisit.

This does two things. It shows Taylor that you took the conversation seriously enough to document it. And it gives you both a shared reference point so the next conversation doesn't start from scratch.

Then actually do the work. Find the project. Create the opportunity. Check in before the 90 days are up, not to hover, but to see if they need anything.

If you do all of that, you haven't said no to Taylor's promotion. You've said yes to their development, which is the better answer anyway.