I recently worked through a workforce retention challenge as part of a consulting engagement proposal. The organization, the industry, and the specifics stay confidential — but what the diagnostic surfaced is too useful to keep to myself.
The presenting problem was turnover. Entry-level roles. High volume, high cost, persistent. The kind of problem that shows up in every budget conversation and gets treated as a staffing issue — which means the response is usually faster hiring, better job postings, maybe a sign-on bonus.
None of that is wrong, exactly. But none of it addresses what the data was actually saying.
Signal One: The Proxy Complaint
Exit interviews kept pointing to compensation. That’s almost always where the conversation starts. Pay is the safe answer — it’s concrete, it’s external, and it puts the blame somewhere that doesn’t require anyone in the organization to look at themselves.
But when you push past the surface — when you do actual listening sessions instead of just reading the forms — a different picture emerges. People weren’t leaving because of pay. They were leaving because no one made them feel like their work mattered enough to stay.
That’s not a compensation problem. That’s a belonging problem. And it has a different solution.
The distinction matters because organizations routinely spend money on the proxy complaint while the actual problem keeps compounding. You can adjust compensation and still hemorrhage people — because the raise doesn’t address the thing that was actually broken. The person who felt invisible doesn’t suddenly feel seen because their hourly rate went up.
For managers: the next time someone on your team raises a complaint about something concrete — workload, tools, scheduling — it’s worth asking what might be underneath it. Not to dismiss the surface concern, but to understand whether there’s something else they’re trying to tell you that they don’t quite have language for yet.
Signal Two: The Invisible Path
The second thing the diagnostic surfaced: people weren’t just leaving because they felt unseen. They were leaving because they couldn’t see forward.
Career pathways existed — technically. But they were either invisible to the people who needed them or so disconnected from daily reality that they might as well not have existed at all. Nobody had shown people the map. And in the absence of a map, people draw their own conclusions — usually that there isn’t one.
This is a fixable problem. But fixing it requires more than creating a document and putting it in the onboarding folder. Visibility of path has to be active. It has to be part of the conversation a manager has with a new hire in their first two weeks — not 18 months in when the person is already halfway out the door.
The organizations that do this well don’t just tell people where they can go. They show them, specifically, what it looks like to get there — and then they stay in the conversation as people move toward it. The map plus the ongoing relationship is what retention actually requires. Either one alone isn’t enough.
Signal Three: The Supervisor in the Middle
Here’s the signal that showed up most clearly — and the one that most directly implicates organizational design rather than individual behavior.
Supervisors, in most organizations, are the single most important variable in whether someone stays or leaves. The research on this is unambiguous. People don’t leave organizations. They leave managers. Or more precisely: they leave the experience of not being developed, not being seen, not being given useful feedback by the person who was supposed to be doing those things.
What the diagnostic made clear was that most supervisors in this situation weren’t failing because they didn’t care. They were failing because no one had given them the infrastructure to succeed. They’d been promoted because they were good at a technical skill. They’d been handed a team. And then they’d been largely left alone to figure out what managing people actually requires.
The organization was asking supervisors to develop their people while simultaneously providing no development for the supervisors themselves. That’s not a management failure. That’s a systems failure. And no amount of performance management or accountability pressure fixes a systems failure. It just makes people feel worse about something that was never fully in their control.
For anyone in a leadership role right now: if your supervisors aren’t having regular developmental conversations with their teams, the first question isn’t why aren’t they doing this? It’s what did we actually give them to work with?
The Part I Didn’t Expect
I’ll be honest about something. I went into this work expecting to find a training problem. Something the organization could solve by building a program, running a cohort, measuring at 90 days.
What I found instead was a systems problem that training can support but cannot solve. Three interconnected failures — people feeling invisible, paths staying hidden, supervisors operating without infrastructure — that had been producing the same outcome for years while the organization kept treating the symptoms.
That’s the diagnostic work I find most valuable. Not the program. The process of getting underneath the presenting problem far enough to see what’s actually driving it.
Turns out I could have kept going. That’s usually a sign you’re working on the right problem.
What This Means for Your Team
You don’t need a retention crisis to apply any of this. The same three signals show up in high-performing teams, in nonprofit organizations, in companies that have never done a formal diagnostic in their lives.
Someone on your team has a proxy complaint they haven’t fully voiced yet. Someone can’t see a clear path forward and is drawing their own conclusions. And somewhere in your organization, a supervisor is doing their best with a job they were never fully prepared for.
The data is there. It’s been there. The question is whether anyone is looking for it — and what they’re going to do when they find it.
Photo by Randy Tarampi on Unsplash