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

Four weeks after you give this feedback, she'll either be more committed to growing into the role — or updating her LinkedIn. The difference is almost entirely in how you frame the conversation, not the content of it.

The trap most managers fall into is delivering this as a verdict: "You're not ready." That puts her in a defensive posture immediately, and defensive people don't hear development feedback — they audit it for unfairness [3]. The move instead is to make her a co-investigator of the gap, not a defendant in a case.

Before the conversation, get specific about what "not ready" actually means. Director-level gaps usually fall into a handful of categories: she hasn't managed other managers yet, she's never driven org-level strategy (versus executing someone else's), she hasn't built cross-functional credibility outside engineering, or she's strong as an individual contributor but hasn't demonstrated she can multiply through others at scale. You need to know exactly which gap (or combination) you're naming — because "not ready" without a precise diagnosis sounds like a runaround, and she'll know it.

In the conversation itself, lead with what you see, not what's missing. Something like: "I want to talk to you directly about the director role because I take your career seriously. Here's what I see in you that makes this role make sense for you to want — [specific capabilities]. Here's the gap I'd need to see closed before I'd feel confident advocating for you in that role — [one or two specific things, not a laundry list]. I want to help you close it. That's why I'm having this conversation now rather than just making a decision."

That framing does something important: it signals that this is a when conversation, not a no conversation [2]. If it genuinely might be a no — if the role is going to someone else, if the org isn't structured to get her there — don't let her build toward a destination that doesn't exist. That's the version of this conversation that loses her for real.

The hardest part is what comes after. If she pushes back — "I think I am ready" — don't debate it [3]. Ask her to make the case. Let her show you what she's seeing. Sometimes the gap you've identified looks different from her vantage point, and you learn something. More often, the act of articulating her own readiness (or struggling to) does more development work than you telling her.

One more thing worth naming: your best engineer wanting the director role isn't a threat to manage — it's a signal that she has ambition and organizational awareness. That's rarer than technical skill. The conversation you're about to have is also, effectively, a retention tool. Done right, it tells her: this company has a path for me and a manager who will advocate for it.

What's the specific gap you've identified? I can help you build the actual language for it.