
Is this your first time reading The Patient Experience Strategist?
Welcome! If a colleague forwarded you this issue, we’re glad you’re here. Don't miss out on future insights. Join our community of healthcare leaders who are navigating the future of care. Get these strategies delivered directly to your inbox every week.
Subscribe Now and Get the Full Experience
The Question to Ask Your Frontline Staff Tomorrow
There is a question that takes about ten seconds to ask, that almost no one in the C-suite asks, and that tells you more about your operational health than your last quarter of survey results.
Here it is.
"Did the last technology we deployed save you time, or add steps?"
That is it. Ten seconds.
You can ask it at the front desk. The contact center. The scheduling team. The MA in the exam room before the provider walks in. The discharge planner. The biller. Anyone who touches the patient or the patient's record on the way through your system.
If they answer quickly and specifically, you have functional alignment between your technology and your operational reality. That is rare. Celebrate it.
If they hesitate, look at their colleague before answering, soften their face, or laugh in a way that is not really laughing, you have a Provider Enablement gap. That gap is the thing your survey scores will not catch until the staff member has already given notice, and probably not even then.
This week is about that gap. Why it shows up. What it costs. And the diagnostic question I want you to take into your operation tomorrow.
What Your PX Peers Are Actually Saying
A theme has been showing up consistently in conversations with patient experience leaders over the last quarter. The verbatims sound like this:
“Our frontline staff want to deliver great experiences, but they’re constrained by systems, processes, and time pressures.”
“Burnout is impacting patient experience. We can’t separate staff experience from patient outcomes anymore.”
“We need to simplify workflows so staff can focus more on patients and less on administration.”
Read those slowly. Notice what they have in common.
They’re not complaints about staff. They’re not complaints about patients. They’re complaints about the operational system the staff have been asked to deliver care inside of.
This is the part most surveys can’t see. Patients can like your nurse and still leave you, because your system made it hard for that nurse to do the thing they were trained to do. The nurse can love her job and still resign at year three, because the system kept adding steps every time it added a tool.
The patient experience metrics measure the output. The capacity of the people delivering care determines whether that output is sustainable.
Provider Capacity Is the Trust Infrastructure
When I first built the Trust Algorithm, I measured five signals from the patient’s vantage point. Accessibility. Resolution. Continuity. Proactivity. Recovery. Can patients reach you. Do problems get solved. Do they feel known. Do you reach out before they have to. Do failures become loyalty.
Those five signals still hold. What I’ve learned, mostly from executives who took the assessment and told me what was missing, is that none of them happen by themselves.
Every single one of those signals is delivered by a person, on a screen, on a phone, in an exam room, at a desk. If that person doesn’t have the tools, the context, the authority, or the time to deliver the signal, the patient feels the gap. Not as a technology complaint. As a trust complaint.
That’s the part worth sitting with. Provider capacity isn’t a back-office concern. It’s the infrastructure that builds patient trust. And patients feel its absence at every stage of the journey, even when they can’t name what’s missing.
Walk through the journey with me.
On Accessibility, a patient calls in. Your access channels are open. The IVR works. The agent picks up. The agent then has to toggle between four screens to find a single appointment, and the patient sits there listening to the keyboard. The patient doesn’t know the agent has four screens. The patient knows it took eleven minutes to do something that should have taken two. Accessibility isn’t failing because the door is locked. It’s failing because the room behind the door wasn’t set up for the work.
On Continuity, the patient has been seen twice already this year. She calls in for the third time. The agent asks her to repeat why she was here last time. The patient repeats it. She’s patient about it. She’s also quietly updating a story in her head about whether this place actually knows her. Continuity isn’t about whether the data exists somewhere. It’s about whether the person serving the patient can see it without asking the patient to be the database.
On Resolution, the patient has a billing question that touches both insurance and the practice. The agent can answer the practice side but has to escalate the insurance side. The patient is told someone will call back. Nobody calls back, because the agent doesn’t have the authority to put the ticket somewhere it won’t fall through. The patient does not experience this as a routing problem. The patient experiences this as nobody around here can actually solve anything.
On Proactivity, the patient has a care gap that the system flagged six weeks ago. The outreach call list exists. It sits in a queue. The team that owns the queue is short-staffed, and the queue surfaces names in a format that takes three minutes per call to prep. So the calls don’t get made. The patient never gets the outreach. The system has the capability and lacks the capacity. The patient experiences this as nobody noticed.
On Recovery, the patient complains. The frontline staff member who hears the complaint doesn’t know whether she can offer anything, refund anything, or even commit to a follow-up. She has to ask. She waits a day for the answer. The patient waits with her. By the time the answer comes back, the patient is no longer angry. The patient is gone. Recovery isn’t failing because nobody cared. It’s failing because the person who cared first didn’t have the authority to act on it.
Five signals. One pattern. The system can promise the signal. Only the provider can deliver it. And when the provider can’t, the patient feels the gap as a trust gap, even if she calls it something else when she leaves.
Why the Question Works
When I ask a staff member whether the latest technology saved them time or added steps, I’m not asking about the technology. I’m asking whether the person closest to the patient has the capacity to do the thing the patient needs done.
When a frontline staff member hesitates on the question, what she’s telling you, without saying it, is that the path from problem to resolution has more steps now than it did before the tool arrived. The tool was bought to remove steps. It added them. That hesitation is the diagnostic finding.
The same question maps to every signal.
For Continuity, ask: when a patient calls in, how long does it take you to see what they were treated for last time? If it’s more than fifteen seconds, your Continuity signal looks fine from the patient side and is failing inside the system. The patient is repeating her history because your staff have no other way to find it.
For Accessibility, ask: when a patient can’t get through one channel and shows up in another, can you see they tried already? If not, your access looks open and the patient is starting over every time she switches lanes.
For Proactivity, ask: who owns the follow-up call list this week, and what is preventing them from making the calls? The answer is almost never “we choose not to.” The answer is almost always “the queue doesn’t surface them in a usable way.”
For Recovery, ask: when a patient complains, how long does your staff have to wait to know whether they can resolve it themselves or escalate? If it’s more than a day, your Recovery signal is being delivered late by a system that asks staff to wait for permission to care.
Five signals. Five questions. Ten seconds each.
Run those questions through your operation, write down what you hear, and you will have a more accurate picture of your trust capacity than your last patient survey will give you.
What This Costs You
Healthcare contact center agent turnover costs $10,000 to $20,000 per agent to replace. That’s the all-in cost: recruitment, hiring, onboarding, ramp time, lost productivity, error remediation, and the cost of the experienced agent’s institutional knowledge walking out the door.
A 100-agent center running at 40% annual turnover is spending $600,000 to $800,000 a year just to keep the same headcount. That money is already in your budget. It’s allocated to refilling chairs, not building capacity.
Now layer in the McKee study from Massachusetts General. Researchers correlated physician burnout with CG-CAHPS scores and found significant correlation on five of the twelve patient experience measures. The strongest correlation was on whether patients felt they got a routine care appointment. The relationship was strongly negative, statistically significant, and survived their controls.
Then the Salyers meta-analysis. Eighty-two studies, more than 210,000 providers across 32 countries. Provider burnout correlated negatively with patient satisfaction across the entire dataset. Not in some studies. Across the literature.
The point isn’t that staff burnout matters. Every executive already knows that. The point is that the absence of provider capacity shows up first in operational signals you can measure today, before it shows up in HCAHPS, before it shows up in turnover statistics, and long before it shows up in the income statement.
The ten-second question is a leading indicator. The survey results are a lagging indicator. The income statement is the latest indicator. Most organizations are running their patient experience strategy off the latest indicator and wondering why the trend lines don’t move.
Where the Capacity Gets Built
Closing the capacity gap isn’t a technology purchase. It’s an operational discipline that the technology is supposed to serve. Three principles do most of the work.
First, consolidate the screens so the person closest to the patient isn’t doing system integration in her head. Every toggle is a tax on her attention and on the patient’s time. The right tech stack disappears into the workflow. The wrong one is the workflow.
Second, push authority to the point of contact. If a frontline staff member can hear a complaint and can’t act on it, you’ve designed a system that asks the patient to wait while the staff member asks permission to care. Give the person who hears the problem the smallest credible amount of authority to solve it. Train her on what’s in bounds. Let her act.
Third, surface what staff need in a format that respects the time they have. A call queue that takes three minutes per call to prep is a queue that won’t get worked. The follow-up that doesn’t happen isn’t a discipline problem. It’s a presentation problem. The data was there. The format made it unusable.
Three principles. None of them require a new platform. All of them require somebody to walk the floor and decide that the workflow serves the staff, not the other way around.
What I Saw From Both Sides
I’ve sat on both sides of the gurney.
I’ve been the executive responsible for a contact center where the metrics looked good and the staff were exhausted. I walked the floor, watched the agents toggle between five systems to answer one patient question, and knew on the way back to my office that the dashboard wasn’t telling the truth.
I’ve also been the patient. Sitting in the exam room. Watching the MA try three times to log into the same screen. Watching her apologize for the system, then apologize for the apology, then ask me a question she should have been able to see the answer to.
The thing I learned, looking at the same problem from both sides, is that the staff member apologizing for the system is the system’s most important warning light. When that apology becomes routine, you’ve crossed from a capacity issue into a culture issue. Once it’s cultural, it takes years to repair. Until then, you’ll keep recruiting people into a system that quietly tells them every day that the work matters less than the workflow.
And the patient on the other side of that exam room? She isn’t writing it up on her survey. She’s deciding whether she comes back.
What This Means for You
Whether you have a dedicated PX team or you’re the executive carrying patient experience alongside three other portfolios, the work is the same this week.
Walk to the front desk, the contact center, or the scheduling team. Ask the five questions. Write down what you hear. Score it 1 to 5 on whether the technology and authority your staff have are supporting the trust the patient is supposed to experience.
That’s a provider capacity self-assessment. It works at any organizational size. With a PX team in place, you can act on what you hear at scale. Without one, you can still act on what you hear in the operation in front of you. Either way, the data lives on the floor, not in the dashboard.
If you want a structured starting number, the Trust Tax calculator quantifies what the gap between the trust your patients are supposed to experience and the capacity your operation actually has is costing you in patient leakage, agent turnover, and revenue. It takes about three minutes.
Calculate Your Trust Tax: https://patientexperiencestrategist.com/trust-tax
The calculator won’t fix the gap. Nothing fixes a capacity gap in three minutes. What it will do is give you a number on what your operation is spending to absorb the gap, so you can have a real conversation about what to do with that money next quarter.
One Last Thing
Reply to this email with the answer your staff gave when you asked the ten-second question. I read every reply. The patterns in those answers are how I keep the Voice of the PX Leader map honest. Your operational reality is the most useful data I get.
Until next Wednesday,
Let’s get to work,
Ebony
Ebony Langston is the founder of The Patient Experience Strategist™ and a fractional Chief Experience Officer for healthcare organizations rebuilding patient trust as a margin strategy. She has 20+ years of operations experience inside Fortune 100 healthcare organizations and writes weekly for the C-suite executives and PX leaders working to translate patient experience from a cost line into a revenue engine.

