There is a specific kind of organizational knowledge that rarely surfaces in a technology review. It belongs to the people closest to the work – front desk staff, medical assistants, billing coordinators – the ones who interact with your technology systems dozens of times a day and have long since figured out which parts work and which parts do not.
It is not that these people are excluded from the conversation. Many of them are consulted by management. Some of them have raised issues before. The problem is that somewhere along the way, they stopped – because nothing changed when they did. And now, if you ask them how things are going, there is a good chance you will hear “fine.”
It is the closest thing to ground truth your practice has about how your technology is actually performing. And it takes real effort to surface it.
The Gap Between the Dashboard and the Floor
Leadership tends to evaluate technology from a distance. Uptime reports. Invoice amounts. The absence of major incidents. If the systems are running and nobody has escalated a crisis, the assumption is that things are working.
That assumption misses a lot.
The systems may be running and still be generating significant friction for the people using them every day. A login process that adds three steps nobody designed intentionally. A platform that works fine on paper but is slow enough in practice that staff have developed informal workarounds to get through their day. A tool that was implemented eighteen months ago and adopted by about half the team, with the other half quietly doing things a different way.
None of that shows up in an uptime report. None of it triggers an escalation. It just exists as background friction – absorbed by your staff, invisible to leadership, and quietly affecting productivity, morale, and patient experience.
What Gets Lost When Nobody Asks
The cost of not asking is harder to see than the cost of a system outage, but it is just as real.
Workarounds become institutional. When staff develop informal ways around a technology problem – because the formal way is too slow, too unreliable, or too confusing – those workarounds become habit. They get passed on to new hires as “how we do it here.” The original problem never gets reported because everyone has adapted to it. By the time leadership becomes aware of it, the workaround is so embedded that fixing the underlying issue requires untangling months or years of informal process.
The reason this happens is not always that nobody is listening. Often it is that staff raised the issue, got told it was “on the roadmap” or “coming in the next release,” and waited. Then raised it again. Then stopped raising it. Vendor promises have a way of training people out of complaining. The resignation that sets in is quiet – it does not look like frustration, it looks like acceptance. That is the signal that is hardest to see from a distance.
Purchasing decisions get made without the right information. A practice considering a new platform, or evaluating whether to renew a current one, should know how the people using it every day actually feel about it. Do they find it intuitive or frustrating? Does it fit the actual workflow or force them to work around it? Is there a competing tool that staff have heard about or used elsewhere that might be a better fit? Vendors will tell you what they want to sell you. Your staff will tell you what you actually need. That intelligence exists in your organization. If nobody is asking for it, it does not make it into the technology decision.
Good staff leave for reasons that could have been addressed. Technology friction is not the top reason people leave jobs, but it is a real one – particularly in healthcare, where administrative staff are already operating under significant pressure. When the tools do not work well and nobody in leadership seems aware of or interested in the problem, it communicates something about how much their daily experience is valued. That is a retention issue with a straightforward solution.
What Asking Actually Looks Like
This does not require a formal program or a technology committee. It requires a habit – and a willingness to dig past the first answer.
The simplest version is a direct question asked on a regular basis – quarterly, at minimum – to the staff who interact most with your technology environment. Not “are there any IT issues?” which invites a binary answer. Something more specific: what is taking longer than it should? What have you figured out how to work around? If you could change one thing about the tools you use every day, what would it be?
The important thing is not to take “everything is fine” at face value. Staff who have been told “it’s coming” enough times have learned not to bother. The first answer is often the polished one. The useful answer usually comes when you push a little further – when you ask about a specific workflow, a specific tool, a specific moment in their day that feels slower than it should.
Those questions surface different information than a help desk ticket does. A ticket gets submitted when something breaks. These questions get at the friction that exists before anything formally breaks – the slow, the clunky, the confusing, the abandoned. That is where the useful signal lives.
The other version is structured – a brief technology experience survey that goes to front desk, clinical support, and billing staff on a regular cadence. Not long. Not burdensome. Five questions, twice a year, with results that actually inform technology decisions. The value is not just in the answers. It is in the signal it sends that leadership is paying attention to the daily experience of the people doing the work.
Closing the Loop
Asking is only half of it. The other half is what happens with the answers.
Staff who raise concerns and see nothing change learn quickly that the exercise is performative. That is worse than not asking, because it actively erodes trust. If you are going to ask, you need a mechanism for doing something with what you hear – even if “doing something” sometimes means explaining why a change is not feasible right now. That transparency matters. “We heard you, we looked into it, here is where things stand” is a very different message than silence.
The practices that do this well treat staff technology feedback the same way they treat patient experience feedback: as real data, worth collecting systematically, worth acting on when the signal is clear, and worth acknowledging even when the action is limited. The information is already in your organization. The only question is whether you have built a way to surface it – and whether you are treating technology as the strategic lever it actually is.
HealthSpaces is a co-sourced technology partner built exclusively for independent specialty physician groups. We help practice leaders understand how technology is actually performing – not just on paper. Connect with our team to learn more.
