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

The stakes here are real: your best engineer has earned the right to expect a path forward, and if the conversation feels like a door closing instead of a timeline extending, she'll start interviewing within a month. The move is to be honest about the gap without making her feel like she's being managed.

Name the gap with specificity, not vagueness

The worst version of this conversation is "you're not ready yet" with no precision about what "ready" means. That's how you create resentment — she hears "I don't see you" instead of "I see exactly where you are." The best version names 2-3 concrete capabilities she'd need to demonstrate at the director level that she hasn't yet, and frames them as learnable.

Scott Eblin's concept of level-shifting is directly relevant: when someone moves from senior IC or manager to director, the value they create has to shift from personal technical output to influencing and enabling others [7]. Your engineer almost certainly still derives her identity from being the best individual contributor. The gap isn't talent — it's operating model. Name that explicitly: "Your engineering is not the question. The question is whether you can lead through others at scale, and I want to help you get there."

Structure the conversation in three beats

Beat 1: Lead with what you see in her. Not generic praise — specific observations about her work and why you're invested in her trajectory. This isn't softening; it's establishing that your feedback comes from someone paying close attention. As David Sluss's research on leadership transitions emphasizes, people make sticky evaluations fast — she'll decide in the first 90 seconds whether this conversation is supportive or political [2].

Beat 2: Be direct about the gap. Pick the two most concrete things. Maybe it's that she hasn't yet demonstrated she can develop other engineers, or that she defaults to solving problems herself rather than building systems that solve them. Maybe she hasn't shown she can operate cross-functionally with product and design leaders as a peer. Whatever it is — name it, give an example, and explain what "director-level" looks like in that dimension.

Camille Fournier makes this point sharply in The Manager's Path: at the senior level, your value shifts from being the expert to being the person who figures out how to help the company grow, and that requires a fundamentally different set of muscles [5]. Share that framing with her — it's not a criticism, it's a map.

Beat 3: Co-build the path. This is where most managers fumble. They deliver the "not yet" and then leave the engineer to figure out what to do with it. Instead, propose a 6-month development plan with specific stretch assignments that let her practice the director-level skills in lower-stakes settings. Lead a cross-team initiative. Mentor two junior engineers with real accountability for their growth. Present the technical strategy to leadership, not just execute it.

The mistake most managers make here

They try to make the conversation painless. They hedge so much that the engineer walks out unsure whether she was told no or maybe. That ambiguity is worse than directness — it breeds the kind of internal narrative ("they're stringing me along") that accelerates departure.

There's a useful framing from a conversation on Lenny's Podcast about handling pushback in these moments: when someone responds with "but I've been here for X years" or "my peer got promoted," don't argue the point — acknowledge the feeling, then redirect to the criteria [8]. "I understand you expected this. Here's what I need to see, and here's how we get there together." The back-and-forth of "yes you are / no you aren't" is never productive.

One thing to watch for in yourself

If part of you doesn't want to promote her because she's your best engineer and you'd lose her output in the current role — be honest about that internally before you walk into the room. Engineers can smell that motivation, and it will poison everything you say. If the gap is real, the conversation is clean. If the gap is partly a convenient reason to keep her where she is, fix that first.

The condition that would flip all of this: if she's actually closer to ready than you think and the real issue is that there's no director seat open. That's a different conversation — one about organizational constraints, not capability. Which one is it?