We Thought We Knew What Customers Wanted: A Clinic's Voice-of-the-Customer Reckoning
A regional outpatient clinic — call it Meadowbrook — came to an improvement project in 2021 convinced of one thing: their problem was waiting-room time. Staff had heard the complaints for years. They had even bought new seating. So when they launched a Lean Six Sigma effort, the assumed goal was obvious: shave minutes off the wait. Then they actually captured the voice of the customer, and the assumption fell apart.
Voice of the Customer, or VOC, is the structured practice of gathering what customers actually need and value, then translating those often-vague statements into measurable, critical-to-quality requirements. It is not a satisfaction survey bolted on at the end. In a DMAIC project it belongs in Define and Measure, because if you misread what 'good' means to the customer, every downstream improvement optimizes the wrong thing.
Gathering the real voice
Meadowbrook had been listening to the loudest signal — front-desk complaints — and treating it as the whole picture. We widened the inputs deliberately, which mattered all the more with hybrid staffing and patients wary of in-person time during recovery from the pandemic:
Short structured interviews with a cross-section of patients, not just the ones who complained at the desk.
Reviews of existing channels they already had — phone notes, online feedback, no-show reasons — that nobody had read systematically.
Frontline staff debriefs, since reception and nurses hear comments that never reach a form.
A small set of follow-up calls to patients who had quietly stopped coming back.
The raw VOC was messy, as it always is. Patients said things like 'I never know what's happening,' 'I felt rushed,' and 'I took a half-day off for a five-minute appointment.' None of that is a measurable requirement yet. The skill is in the translation.
Turning vague words into critical-to-quality requirements
We used a simple discipline: take each customer statement, find the underlying need, then define a critical-to-quality (CTQ) characteristic you can actually measure. A few examples from Meadowbrook:
'I never know what's happening' becomes a need for communication during the visit, with a CTQ of how often patients receive a status update and how clearly the next step is stated.
'I felt rushed' becomes a need for adequate clinical time, with a CTQ on minutes of actual face time with the clinician, not total visit length.
'I took a half-day off' becomes a need for predictable scheduling, with a CTQ on the gap between appointment time and the patient actually being seen.
Here is where the assumption broke. Wait-room minutes mattered far less than predictability and being told what was going on. A patient who waited twenty minutes but was kept informed rated the visit higher than one who waited eight minutes in silence. The team had been about to spend its capacity reducing the wrong number.
Why this saved the project
Because the CTQs were grounded in real customer voice rather than internal assumption, the Measure and Analyze phases pointed somewhere useful. The clinic put in simple status updates and tightened scheduling predictability instead of chasing raw wait time. Satisfaction rose, and quiet drop-offs fell, without the expensive throughput overhaul they had nearly committed to.
The lesson is not subtle, but it is easy to skip under pressure: do not let a confident internal belief stand in for the voice of the customer. Gather the voice deliberately, translate it into measurable CTQs, and let those — not your assumptions — define what the improvement is for. A team that knows precisely what 'good' means to its customer rarely improves the wrong thing.
If your team is improving a service without being certain you have heard your customers correctly, XNM's strategic advisory can help you capture that voice and turn it into requirements worth measuring.