Why Your Best Employee Might Quit (And What You Actually Miss)

I had a direct report named Jordan who I thought I was managing well. He hit every deadline. He never came to me with drama. He figured things out on his own and came to 1:1s with clear updates. In my head, he was the easy one. The one I did not need to worry about.

He resigned on a Tuesday in October. Nine months into my first management role.

I was blindsided. I thought I had done right by him. I had given him the interesting projects. I praised him in team meetings. I told him I was happy to write a reference whenever he needed one someday. What I had not done was ask him what he actually wanted from his career. Not once. I assumed the interesting work was enough. I assumed that because he never complained, he was content.

His last day, we had a real conversation. He said something that I have thought about probably once a week since: "I didn't feel like there was a path here. I didn't know what I was working toward."

I had given him work. I had not given him a future.

The engaged ones leave quietly

The people who are disengaged usually make noise. They push back in meetings, miss deadlines, come to you with complaints. They are visible. You know they are struggling.

The people who are highly capable tend to exit differently. They are too professional to check out visibly, so they do their jobs, stop raising their hand for extra work, update their LinkedIn profile, and wait until they have somewhere better to go. By the time they hand in their notice, they have been mentally checked out for months.

Gallup research on employee engagement consistently shows that the top drivers of voluntary turnover are not pay and benefits. They are a lack of career development, feeling disconnected from the mission, and not having a strong relationship with their manager. The capable people leave because the job stopped growing with them. The ones who stay despite being disengaged? They are the ones without options.

"The best people are always the hardest to keep. Not because they are the most demanding, but because they are the most aware of what they could have elsewhere."

When Jordan left, he had already been offered something better. He told me he had not even been looking aggressively. Someone reached out, and when he thought about whether to entertain it, he did not have a good reason to say no.

What You Miss When Someone Never Complains

I thought Jordan was fine because he was performing. But performance and engagement are not the same thing. Someone can execute their job well and still be drifting away from you.

The signals I missed with Jordan were there. I just did not know to look for them.

He had stopped bringing ideas to our 1:1s around month six. Early on, he would come in with observations about our processes, questions about how decisions got made upstream. That stopped. I registered it as him settling in, becoming more efficient. It was actually him disengaging.

He stopped volunteering for cross-functional work. We had a few company-wide initiatives that needed reps from different teams. Jordan had raised his hand for the first two. He did not for the third. I did not follow up on why.

He started giving shorter answers. Not curt, just more contained. Our 1:1s went from forty-five minutes to thirty. I thought he had gotten better at preparing. He had stopped investing in the relationship.

Common mistake: Treating your highest performers as self-managing systems instead of people who need just as much intentional development as anyone else. Maybe more, because they can see the ceiling faster.

The three questions that retention actually depends on

After Jordan left, I spent some time reading and thinking about what I had missed. I came across a framing in Liz Wiseman's Multipliers that stuck with me. Wiseman distinguishes between managers who use people's intelligence and managers who grow it. The ones who grow it keep people. The ones who just use it eventually run out of what makes the person want to stay.

I was using Jordan's capacity. I was not helping him build toward anything.

The questions I now try to ask every direct report at least quarterly:

What are you hoping to get better at in the next six months? Not what are you working on. What do you want to develop. There is a real difference. One is about the job. The other is about them.

Is there anything you are working on that feels like a waste of your time? This one surfaces resentment before it calcifies. People rarely volunteer that they think a project is pointless. They will answer this question honestly if you ask it directly.

Do you feel like you have enough visibility into where things are headed? Jordan told me he did not have a path. This question gets at that. If someone does not feel like they can see the road ahead, they start looking for a different road.

Try this week: In your next 1:1 with your highest performer, skip the status update entirely and ask one of these questions instead. Take notes. If you get a surprising answer, sit with it before responding. The instinct is to reassure. What they need is to feel heard first.

What a Career Conversation Actually Looks Like

I used to think career conversations required some kind of formal framework. A special meeting, a structured template. I would put it off because I did not know how to run one.

A manager I worked with early in my career handled it differently. She worked it into normal 1:1s, one question at a time. She did not call it a career conversation. She would just ask, in the middle of a regular check-in: "If this goes well for you, what do you see yourself doing in two years?" Then she listened. She wrote it down. She came back to it.

That is it. You do not need a program. You need the question and the follow-through.

The follow-through is where most managers fail. You ask the question once and do not connect it to anything. You don't bring it up when an opportunity surfaces. You don't reference it when giving assignments. The question feels hollow because nothing changes after you ask it.

"Asking someone what they want and then not connecting it to anything they work on is worse than not asking. It teaches them that the conversation is performative."

When Jordan told me he felt like there was no path, I think what he was really saying was that I had never asked him what the path was supposed to look like. And even if I had, I had no record of it and no system for following through.

The part about pay

I want to be honest here: sometimes people leave for money. That is real and it happens. But in my experience, pay is usually the stated reason when the real reasons are harder to articulate. "I got a better offer" is easier to say in an exit conversation than "I stopped feeling like my work mattered here."

I am not saying compensation doesn't matter. It does. But if someone's career is growing, if they feel visible and valued, if they have a clear sense of where they are headed, they are much less likely to entertain a recruiter on LinkedIn just because the message is flattering.

Retention is mostly about making the job worth staying in. The money question usually comes later.

Kim Scott writes in Radical Candor about the difference between people who are on a "steep growth trajectory" versus those who are in a role that fits them well long term. Her argument is that both need management, just differently. The people on the steep trajectory need regular challenges and clear signals that the organization is invested in them. If they stop feeling that, they go find it somewhere else.

Jordan was on a steep trajectory. I was managing him like he was settled.

What I Changed

After Jordan left, I did a few things differently.

I started keeping notes from career conversations in the same place as 1:1 notes. Not a separate document I would never look at, but right in the same thread. So when we talked about goals, I could see what someone had said three months ago.

I started tracking a simple thing: when did I last have a real forward-looking conversation with each direct report? Not status. Not feedback. Something about where they are going. If it had been more than six weeks, I flagged it.

I stopped assuming that high performance meant high engagement.

One of my direct reports told me a few months after I started doing this: "I don't know what changed but these conversations feel different. Like you're actually keeping track." She had no idea I had started a simple note-taking habit. She just felt it.

I built Cadence partly because of situations like Jordan. I kept losing the thread between conversations. I would have a meaningful discussion about what someone wanted, and then two months later I had no record of it and we were back to status updates. I wanted a tool that made the continuity automatic, so I could focus on the conversation instead of trying to remember what we talked about last time.

The work itself matters. But so does knowing that someone is paying attention to where you are headed. Jordan deserved that. I just figured it out too late.

Know what your team actually needs before it's too late.

Cadence helps you track the conversations and goals that matter — in 1:1s, team meetings, and everything in between. Catch what you would have missed. 14-day free trial.