Why Staff Turnover Is Often an Operations Problem, Not a People Problem

A staff member leaves. Leadership reflects on it and lands on some version of: it was the wrong fit. A new hire is brought in. A few months later, the same conversation happens again.

At some point it’s worth asking whether the common denominator is the organization, not the people moving through it.

The Comfortable Explanation

Attributing turnover to fit, attitude, or work ethic is understandable. It’s also hard to argue with, because it centers on individuals who are no longer there to offer a different account.

What it doesn’t explain is why the same friction keeps appearing with different people - why the role that was hard to fill is hard to keep filled, why the same complaints come up in exit conversations that leadership assumed were isolated incidents.

If the problem keeps happening with new people, it’s worth looking at what those people were walking into.

What It Looks Like on the Ground

The operational problems that drive turnover don’t usually get too much attention.

A new clinical assistant receives one set of instructions from the practice manager and a different set from the lead provider. A front desk employee learns the scheduling system from whichever coworker happens to have a free moment that week - which means they learn it differently than the person hired before them, and differently again from the person hired after. Two staff members handle the same intake process in two different ways because nobody has written down which way is correct.

None of these things feel like emergencies, but they accumulate. And the people navigating them daily, who try to do their jobs well without a clear foundation to work, from get tired of it faster than leadership usually expects.

By the time someone submits their notice, the decision has usually been forming for a while.

Where It Tends to Begin

In many organizations, retention problems start long before an employee decides to leave. They often begin during onboarding.

Not onboarding in the sense of paperwork and a first day tour. Onboarding in the sense of: does this person actually know what they’re responsible for, how to do it, who to ask when they’re unsure, and what good performance looks like in this specific organization?

When that foundation is missing, inconsistent, or dependent on whoever happened to have bandwidth that week, new hires spend their early weeks filling in the gaps themselves. They develop workarounds. They make assumptions. They occasionally make mistakes that feel, to them, like failures, and feel, to leadership, like signs that the hire wasn’t the right fit.

Sometimes the hire genuinely wasn’t. But often, the hire never had a real chance.

A useful test is simple: could you describe your onboarding process in writing right now? What it actually looks like for every person who comes in? If that’s difficult to answer, the gap is probably affecting retention in ways that aren’t fully visible yet.

The Communication Problem Nobody Names

The other operational driver of turnover is one that rarely gets identified as such, because staff don’t usually describe it that way.

They describe it as not knowing what’s going on, not feeling like they’re in the loop, finding out about changes after the fact, getting feedback inconsistently - a lot of it when something goes wrong, very little of it otherwise.

What they’re describing is a communication structure that’s reactive rather than consistent. Information moves when there’s a problem or when someone thinks to share it, not through any consistent practice. Expectations get stated once, verbally, and assumed to be retained. A policy changes, and the people it affects find out in different ways, at different times, with different levels of context for why.

Over time this creates a particular kind of low-grade disorientation. Staff can’t quite articulate what’s wrong, but they feel less and less grounded in the organization. Eventually, a job that offers more clarity starts to look appealing - not because the pay is better, but because it could be less exhausting.

Growth Accelerates All of It

Organizations in growth phases that are adding staff, expanding services, taking on more volume - tend to experience a concentrated version of these problems.

What worked informally at a smaller scale stops working as the team grows. The onboarding that the office manager handled personally when there were six employees doesn’t hold up when there are sixteen and the office manager is stretched thin. The communication that happened naturally in a small space becomes inconsistent as more people are involved and more is happening at once.

Leadership often senses that something is off: the organization feels harder to manage than it used to, that staff seem less settled, that turnover has picked up. The explanation that surfaces most often is that growth is just hard, or that the pace is demanding, or that some people couldn’t keep up.

That’s sometimes true. But more often, the people who leave during growth phases were undone by trying to operate in an environment that was scaling faster than its internal structure could support.

Questions Worth Asking Before the Next Hire

If turnover is a recurring issue, the instinct is usually to focus on the hiring process - better screening, clearer job descriptions, more rigorous interviews. Those things matter. But they don’t change what a new hire walks into.

Before posting the next role, it’s worth sitting with a few operational questions:

What does the first 30 days actually look like for someone new - not in theory, but in practice? Is it consistent, or does it depend on who’s available?

When expectations aren’t being met, is it possible the expectations were never clearly stated in the first place?

When the same issue has come up with more than one person, has anyone looked at whether the issue might be in the process rather than the people?

What does a staff member do when they’re uncertain about something? Is there a clear answer to that question, or do they figure it out on their own?

The answers don’t always point to operational gaps. But when they do, they tend to explain a lot.

The Actual Cost

Turnover is expensive in ways that are easy to undercount. There’s the time spent recruiting and interviewing. The cost of training someone new. The period of reduced capacity while a role is vacant or while a new hire is still finding their footing. The institutional knowledge that leaves with each departure. The effect on the staff who stay, absorb extra work, watch colleagues cycle through, and draw their own conclusions about the organization.

Treating all of that primarily as a hiring problem means continuing to invest in bringing people in while leaving unchanged the environment they’re stepping into.

The more useful question, in most cases, isn’t who to hire next. It’s what the organization looks like for the people already there - and whether it’s actually set up to keep them.

Lonczak Group works with clinics, practices, and healthcare organizations on operational structure and implementation. Engagements are tailored to the size, pace, and needs of each organization. Learn more at lonczakgroup.com.