The Dormant Talent

Ask him what each person on his team needs to grow and he'll tell you, specifically. He's also done nothing about it in eighteen months. Knowing isn't the same as doing — and a manager who can name the gap and doesn't close it is a more complete failure than one who simply doesn't know.

Ask him what each person on his team needs to grow, and he'll tell you. Specifically. He knows who's ready for more scope, who needs a harder conversation about a blind spot, who's been quietly coasting and who's about to leave if nothing changes. He's right about all of it, every time you've checked.

He has also done nothing about any of it in eighteen months.

None of that fits the usual story. This isn't a manager who lacks the judgment to see what his team needs. He has exactly that judgment, in detail, on demand. What he lacks is any track record of acting on it. Two of his strongest people have left in the past year, both citing the same thing on the way out: no path, no movement, no real investment in where they were headed. His own performance reviews stayed strong the entire time. Whatever is being measured up top, it isn't this.


Knowing Is Not the Same as Doing

The instinct, once you've confirmed he genuinely understands what his people need, is to relax. At least he's not oblivious. At least the diagnosis is right, even if the follow-through is missing.

That instinct is the trap. A manager who can name the gap and doesn't close it isn't a partial success story. He's a more complete failure than one who simply doesn't know, because the absence of an excuse is itself diagnostic. You can develop someone's judgment. You can't develop someone into noticing what he's already noticing. The thing missing here isn't insight. It's the choice to spend his own time and standing on someone else's advancement instead of his own.

That distinction is what separates this from a capability problem. He sees the work fine. He's choosing not to do it, consistently enough that it's no longer a one-off lapse. It's the actual shape of how he manages.


Why His Numbers Stay Clean

Here's how it runs for years without anyone naming it: the manager's own performance metrics rarely capture what he's failing to do.

He hits his targets. His own output is strong. The teams he runs deliver. From above, that reads as a good manager, and from a narrow enough lens, it is. What doesn't show up in that view is the team member who's been ready for two years and never moved, the high-potential who quietly started interviewing six months before she gave notice, the pattern across roughly anyone he's managed: people develop in spite of him, not because of him, and the ones who can leave eventually do.

His personal stock stays high because nothing in how he's evaluated asks whether the people under him are getting better. By the time the cost shows up, it shows up as someone else's resignation letter, in a system that wasn't built to trace that letter back to him.


What Gives Him Away

He can articulate the development need precisely, for everyone, without prompting. This is the detail that distinguishes Dormant Talent from a manager who genuinely doesn't see the gap. The insight is real and specific. It just never converts into action.

The pattern holds across his entire team, not one difficult case. One person not advancing might be circumstance. Nobody advancing, year over year, while the manager can explain exactly why each of them should be, is a pattern about the manager, not about the people.

His own advancement and stability look fine. He's not struggling, not at risk, not under pressure himself. The neglect is specific to what he's supposed to be doing for other people, not a general sign of someone overwhelmed.


Why Nobody Confronts It

Most performance conversations are built around outputs, and his outputs look fine. There's no metric flashing red, no incident to investigate, no obvious complaint landing on anyone's desk before the resignation already happened. The evidence that something's wrong is distributed, a departure here, a stalled career there, each individually explainable, and distributed evidence is exactly the kind that never reaches critical mass in a single conversation.

There's also a harder truth underneath that: naming this requires telling someone who is, by every visible measure, a strong performer, that he's actually failing at a core part of the job. That's an uncomfortable conversation to start without very specific evidence, and the evidence that exists is scattered across exit interviews and stalled careers that nobody has been asked to connect into one picture.

So it doesn't get named. The team underneath him keeps absorbing the cost, the good ones keep finding their way out the door eventually, and he keeps getting credit for results that, on inspection, were produced in spite of how he manages rather than because of it.


The Conversation That's Overdue

This isn't a training problem, and treating it like one wastes time he doesn't need. He already knows what good development looks like. What's required is a direct conversation about the gap between what he can articulate and what he's actually done, with the specific evidence laid out rather than a general sense that something feels off. He needs to hear, plainly, that the standard he's being held to now includes whether his people are advancing, not just whether his numbers are clean.

What happens after that conversation is the real test. Some managers, confronted with the gap, close it once it's actually expected of them and measured. Others have been coasting on exactly this pattern for a reason, and the conversation reveals that the neglect was a choice serving him, not an oversight he simply hadn't noticed. Knowing which one you're dealing with takes one real attempt at accountability, clear expectation, clear measurement, clear timeline, and watching what he does once knowing is no longer enough of an excuse.

If a manager can tell you exactly what his team needs and has done nothing about it for a year or more, the conversation that's overdue isn't about his skills. It's about what he's actually been choosing to prioritize.

That conversation gets harder to have the longer his numbers stay clean.