What It Actually Costs You to Ignore a Staff Concern

Most practice owners do not set out to dismiss their team. They are busy, they are stretched, and when a concern lands on their desk it often arrives at the worst possible moment, between patients, mid crisis, at the end of a day that was already too long. So it gets noted, acknowledged in the moment, shelved for later, and later, quietly, never comes. Nobody makes a decision to ignore their people. It usually happens in increments, one deferred conversation at a time, until the pattern is established and the damage is already done. The cost of that pattern is not abstract. It shows up in your accounts, your attrition rate, your team culture and eventually your business value, and it is one of the most commercially significant things a practice owner can get wrong, and it rarely appears on any report that would make the problem visible until it is well advanced.

When a staff member raises a concern and nothing happens, they do not simply move on. They draw a conclusion. The conclusion is not always dramatic, it is usually quiet and rational, this is not a place where my voice matters, and from that conclusion they make a series of smaller decisions, also quiet and also rational, about how much of themselves to invest going forward. They stop bringing ideas. They stop flagging problems early, because flagging problems early has taught them nothing changes. They do what is required and no more, because going beyond what is required has no apparent value in an environment that does not respond to input, and they start, at some point, looking at what else is available to them. You do not see any of this happening in real time. You see the outcome of it weeks or months later when the resignation arrives, or when you notice the team feels flat and you cannot quite identify why, or when a patient complaint surfaces that someone on your team saw coming and did not raise because they had already learned it was not worth raising. By the time the cost is visible, the cause is long past.

This is not anecdotal. Organisations that respond poorly to employee concerns face measurably higher turnover, and turnover in a clinical setting is expensive in ways that go well beyond recruitment costs. You lose institutional knowledge that took years to build, you lose patient relationships that were attached to that person, you lose the productivity of everyone who covers the gap while the role is vacant and while a new person finds their feet, and you absorb the cultural cost of a team that watched a colleague leave and drew their own conclusions about why. Conservative estimates put the cost of replacing a clinical staff member at between fifty and two hundred percent of their annual salary when you account for all of it properly. A practice losing two or three good people a year to a culture of unaddressed concerns is not just managing a people problem, it is funding a significant and entirely avoidable financial drain. Beyond attrition, unresolved concerns become compliance risks. In a clinical environment, staff who feel unheard about safety, process or governance issues do not always escalate internally when internal escalation has proven pointless, they go elsewhere, to the Health and Disability Commissioner, to WorkSafe, to professional bodies. The practice that ignored a concern in a Monday morning conversation can find itself managing a formal complaint six months later that could have been resolved in twenty minutes.

Addressing staff concerns well does not require a formal process for every conversation. It requires a culture where concerns are received properly and followed through consistently. Receiving a concern properly means the person raising it feels genuinely heard, not managed, it means you ask questions before you form a view, and it means you do not immediately defend the practice, the system or the decision being questioned. It means you treat the concern as information, which is what it is, rather than as a challenge to your authority or a problem to be contained. Following through consistently means the person who raised the concern knows what happened next, not necessarily that everything changed, not necessarily that they got the outcome they wanted, but that their concern was taken seriously enough to be investigated, considered and responded to. Even when the answer is that nothing will change and here is why, that response is worth giving. It closes the loop, and it demonstrates that the concern was real to you even if the resolution was not what they hoped for. The practices that handle this well share a common quality, they treat staff concerns as early warning systems rather than inconveniences. A concern raised internally is almost always better than the alternative, which is that the concern festers, grows and eventually surfaces somewhere outside the practice's control. The team member who brings you a problem is doing you a service, and the culture that makes that feel safe is one of your most valuable operational assets.

Culture alone is not enough. There needs to be a structure that makes it easy for concerns to be raised and impossible for them to be lost. That means a clear and genuinely accessible process for raising concerns, one that does not require a staff member to navigate a hierarchy they do not trust or complete documentation that makes the whole thing feel adversarial before it has even started. It means a documented response timeframe so that concerns do not simply disappear into a manager's inbox, and it means someone with actual authority to act is involved at the right point, not just a layer of middle management that can absorb a concern without it ever reaching the person who could do something about it. It also means that the person who raised the concern is never, in any way, made to feel the consequences of having done so. Nothing erodes a speak up culture faster than watching a colleague raise something and then finding themselves subtly sidelined, overlooked or made uncomfortable. That pattern does not have to be intentional to be damaging, it has to be visible to everyone watching, and in a small practice everyone is always watching.

If you are reading this and thinking about a concern that is currently sitting on your desk, or one that was raised three months ago and has not quite been resolved, or a team member who tried to tell you something once and has not tried again since, that is the place to start. Not with a formal process, with a conversation, one where you go back, acknowledge the concern was raised, ask how the person is feeling about it now and tell them honestly what has or has not happened since. It will feel uncomfortable if it has been a while. Do it anyway, because the discomfort of that conversation is a fraction of the cost of not having it.

The practices that retain good people, maintain strong cultures and avoid the compliance exposure that comes with unresolved grievances are not the ones that never have difficult concerns raised. They are the ones that respond to those concerns in a way that makes their people feel that raising them was the right thing to do. That is not complicated, but it does require deciding that your people's concerns are worth your time, and then consistently proving it.