My best engineer wants the director role but isn't ready. How do I have the conversation without losing her?

The tension here is real: you need to protect the integrity of the role while making sure she doesn't interpret a "not yet" as a "not ever" — because that's the interpretation that makes people leave.

Name the framework first: Separating the decision from the relationship

Most managers conflate two things in these conversations: the promotion decision and the person's trajectory. When you blend them, the person hears "you're not good enough" instead of "here's the gap and here's how we close it." Your job is to make those two tracks explicit and separate.

There's a useful concept from how experienced leaders handle these moments: the difference between pushback and productive dialogue [3]. When someone believes they deserve a promotion, they'll often respond with evidence of tenure, peer comparisons, or past performance — things that feel relevant to them but may not be part of your decision-making criteria. If you get pulled into a yes-you-are / no-you're-not loop, nobody wins. Instead, acknowledge what's true ("You're the strongest engineer on this team, and I want you in leadership") while being direct about what the director role actually requires that she hasn't demonstrated yet.

What the conversation actually looks like

Open with your bet on her, not the gap. Something like: "I want to talk about the director role, and I want to start with the fact that I see you in it. The question isn't whether — it's when, and what needs to be true first." This reframes the conversation from gatekeeping to joint planning.

Then be brutally specific about the gap — not vague. "Director here means X, Y, and Z. You're exceptional at X. What I haven't seen yet is Y in this context, and here's what demonstrating it would look like." Vague feedback ("you need more leadership experience") is what makes people feel the goalposts are moving. Concrete gaps feel solvable. David Sluss's research on leadership transitions reinforces this — people evaluate leaders (and their own path to leadership) based on specificity and credibility, not platitudes [2].

Co-build a timeline. Don't just say "not yet" — say "here's what the next six months could look like if we're intentional about closing this." Offer her stretch assignments, visibility with senior leadership, or a scope expansion that lets her practice the missing competencies in lower-stakes settings. The goal is to make the path feel concrete and jointly owned, not like a vague promise.

The misunderstanding most managers have

Most managers think the risk in this conversation is saying no. It's not. The risk is being unclear about what yes requires. When people leave after being passed over, it's rarely because the answer was no — it's because they couldn't see a credible path to yes, or they suspected the criteria would shift again next cycle. Your best engineer has probably already thought about this more than you realize. She's watching whether you treat her like someone worth investing in or someone to manage.

One more thing worth naming: if she's your best engineer and the director role requires capabilities she hasn't built yet, you also owe her honesty about whether she actually wants what the director role entails — not just the title, but the work [1]. Some of the best engineers discover that management pulls them away from what makes them exceptional. That's worth exploring together, not assumed either way.

Want me to draft the specific talking points for this conversation, or would it be more useful to walk through how to handle the most likely pushback she'll give?