Not Every Goodbye is a Failure

I've watched a lot of people come into and go out of organizations.

Some left by choice. Some were shown the door. Some walked out with a smile and a plan, genuinely excited about what was next. Some left with tears in their eyes, and not always the ones you'd expect. I've seen people leave a job they loved and people leave a job that had quietly worn them down for years.

Change is hard. But after watching enough of these transitions, I've stopped assuming that a departure means someone failed. Parting ways doesn't have to mean burned bridges or hurt feelings. Sometimes it's a mismatch between what an employee needs and what the organization is willing or ready to provide.

That's a more generous frame than most retention conversations allow. It's also the easiest excuse in the world for a leader who hasn't been paying attention.

The slow decline nobody schedules

There's research from Leadership IQ that tracked engagement against tenure across more than 30,000 employees, and the pattern is uncomfortable. In an employee's first year, roughly 37% are highly engaged. By year five, that's down to about 22%. Over the same stretch, the share of deeply disengaged employees roughly doubles.

Nobody plans that. No organization sits down in a strategy meeting and decides to let its people slowly check out over four years. It just happens, the way most bad outcomes happen, through a thousand small omissions.

Because year one gets attention. There's onboarding. There's a manager checking in. There are conversations about growth and development and where this might go, because everything is new and the questions are natural.

By year four, nobody's asking. The person knows the job. They do it well. They've stopped requiring management. And that competence becomes the reason they get overlooked.

Three of Gallup's Q12 engagement items live right in that gap: someone at work encourages my development, someone has talked to me about my progress in the last six months, I have opportunities to learn and grow. The engagement cliff isn't a mystery. It's what happens when attention stops.

The word that does all the work

So when is a departure genuinely a mismatch, and when is it a failure wearing a nicer outfit?

The test I keep coming back to is intention. A real mismatch happens when an employee needs something the organization has knowingly and intentionally decided not to provide.

A firm that has deliberately stayed small and flat doesn't have a promotion ladder. That's a real choice with real tradeoffs they've accepted on purpose. A company that decided to be fully in person because they believe people learn the work by being near it has made a call. A nonprofit that can't match corporate pay knows exactly what it can't offer and why.

None of those organizations are wrong. And the person who needs the thing on the other side of that choice isn't wrong either. They should go get it. That's a mismatch, and it can end with a handshake and a referral.

Now compare that to the organization with no career path because nobody ever built one. No development conversations because managers are underwater. No clarity about advancement because leadership avoids the topic and hopes it doesn't come up.

When that company loses someone, "it just wasn't a fit" is a story it tells itself.

The difference is whether a leader can name the choice and the tradeoff out loud before the person resigns. If you can only articulate it in hindsight, it wasn't a decision. It was neglect with better vocabulary.

The conversation most leaders won't have

The honest version of this requires saying it clearly, but a lot of leaders won't.

Someone asks about a path to promotion. They get "let's keep the conversation going." Then they get it again six months later. Two years pass. The manager doesn't want to lose them and doesn't want the hard conversation, so the answer stays permanently blurry.

That ambiguity is the actual failure. Not the absence of the role.

Telling someone directly, "that's not something we're planning to build here, so let's talk honestly about what that means for you," is more respectful than eighteen months of maybe. It usually buys you a better ending. Sometimes it buys you more time, because people stay longer when they trust what they're being told.

Engagement isn't a program you install

The other half of this is attunement, and it's where most engagement work quietly goes wrong.

Organizations tend to treat the Q12 like a checklist to roll out uniformly across a team. But those items are relational, not programmatic. "Someone encourages my development" means a stretch assignment for one person and protected focus time for another. "Recognition in the last seven days" means public praise for one person and a quiet note for someone who would rather sink into the floor than be applauded in a staff meeting.

A manager running the same play on twelve people will genuinely believe they're doing engagement work while half the team feels unseen.

This is why I spend so much time on strengths with the leaders I work with. Not because a CliftonStrengths report is magic, but because it gives a manager language for a question they otherwise have to guess at: what does this person actually need to do their best work, and is that still true this year?

Because people change. The role that fit someone perfectly at year one may have slowly reshaped itself by year four until it barely touches what energizes them. Nobody notices, because the work still gets done. That drift is often what's underneath the numbers, and it's fixable if someone catches it in time. It usually costs a conversation and a role adjustment, not a resignation.

Wanting to keep people is not a plan

Of course organizations want to keep their best people. Everyone wants that. Nobody in leadership has ever said otherwise.

But wanting is not a strategy, and retention is not passive. It doesn't happen because the culture is good or the benefits are competitive or people seem happy enough in meetings. It happens because someone close to each person is paying enough attention to notice when something has shifted, and is willing to ask about it before the answer becomes a resignation letter.

The exit interview is a receipt. You're finding out what someone needed at the exact moment you can no longer provide it.

The stay conversation is the version that actually works, and it's not complicated. What's energizing you right now? What's draining you? What do you want to be doing a year from now that you're not doing today? And then the part that takes courage: an honest answer about whether that's available here.

Sometimes the answer is yes, and you've just re-recruited someone who was drifting.

Sometimes the answer is no, and you've just given someone the clarity to make a good decision instead of a resentful one.

Both of those are better than the version where a good person quietly checks out for eighteen months and then leaves angry.

Not every goodbye is a failure. But you only get to say "it was just a mismatch" if you were paying close enough attention to see it coming.