Methodology
A worked example of the Voice of Customer tool, using a fictional freight operator. Five customer segments, five measurable requirements, and the trap that catches most teams on their first capture.
A customer will never tell you they need delivery before six on a Friday at ninety eight percent reliability. They will tell you that if it is not on the shelf Friday morning, they have lost the weekend.
Those two sentences mean the same thing. Only one of them can be measured, tested, or put in a contract. Voice of Customer is the tool that gets you from the first to the second without losing what the customer actually said.
This walkthrough uses Kembla Freight Services, a fictional regional freight operator invented for this guide. The segments, the numbers and the complaints are made up. Every screenshot is the real tool.
The national retail accounts said it in a survey of sixty four responses. If it is not on the shelf Friday morning we have lost the weekend.
Keep that sentence. It is the thing you will read out when someone proposes a solution that arrives at ten on Friday and wonders why the customer is unhappy.
The translation sits beside it. Delivery before six on Friday, on ninety eight percent of loads. That is a critical to quality requirement. It has a time, a threshold and a unit, so it can be measured next week and argued about with data rather than opinion.
Regional wholesalers want to know a load is late before the driver is late. Cold chain clients reject a whole pallet over a broken seal. Small business shippers are ringing three times for a proof of delivery. Freight forwarders would like a rate card.
The priority column is doing real work here. Three segments are Must Have. One is Should Have. The rate card is Nice to Have, and it came from a workshop with seven forwarders.
That last row matters precisely because it is low priority. Capturing it stops it reappearing in three months as an urgent request with no history behind it. It is in the register, it is ranked, and the ranking is evidenced.
Service appears twice, from small business shippers and from forwarders. Delivery, Visibility and Quality appear once each.
Be careful here, and this is the trap. A raw theme count is not a priority order. Service leads on count, but both of those records are the lower priority ones. The single Quality record from cold chain is a Must Have with six months of rejection data behind it.
Read the theme count and the priority column together. Frequency tells you what is common. Priority tells you what is expensive to get wrong.
Every record has a measurable requirement. Every record cites evidence. More than two sources are represented. Themes are classified.
The evidence column is the one that earns its place at a tollgate. Sixty four survey responses. Eleven interviews. Six months of rejections. One hundred and forty eight complaint records. Seven forwarders in a room.
None of those are large samples on their own. Together they are five independent lines of sight on the same operation, which is considerably stronger than one big survey.
The interpretation groups the themes, restates the critical requirements and names the gaps. On this capture it did what a good reviewer does, which is ask about the customers who are not in the register.
It is reading five rows. It has no access to your revenue by segment, your contract terms, or which of these customers is about to leave. Those are yours to bring.
Use it to catch what you missed, then go and fill the gap with evidence rather than with a better sounding sentence.
It will not tell you which customer matters most. Five segments, five sets of needs, and no revenue attached to any of them. A Must Have from a segment worth two percent of your book is not the same as a Must Have from the segment carrying your margin. The tool does not know that and will not warn you.
It will not check your sample. Sixty four survey responses is a number you typed. Whether those sixty four are representative of the segment, or just the sixty four who were annoyed enough to reply, is your judgement to defend.
It will not tell you a requirement is achievable. Seal integrity failures at two hundred parts per million is what the customer wants. Whether your process can hold it is a Measure and Analyse question and the answer may be no.
It will not capture what customers cannot articulate. People describe the problem they noticed. They rarely describe the one they have adapted around. Observation and complaint data exist to catch those, which is why two of the five records here came from rejection and complaint analysis rather than from asking.
Where this goes next is the Define phase. Your Must Have requirements become the goal statement, the priority column decides scope, and the verbatim column is what you read out when a proposed solution drifts away from what anyone actually asked for.
RDMAICS, A3, Just Do It and Kaizen projects with the full Lean Six Sigma toolset, AI interpretation and tollgate presentations built from your real evidence.
5S Workplace Design converts a confirmed root cause into five concrete future-state actions with owners and dates. This guide walks through the tool's built-in sample case and shows how to size the gain before you commit to the change.
Read the article
Batch-Size Optimisation takes a diagnosed cause and turns it into a change you can pilot with a number attached. This guide walks through the tool's built-in sample data, from four candidate batch sizes to a single recommended answer.
Read the article
Setup Reduction / SMED takes a diagnosed cause and turns it into a change you can test. This guide walks through the tool's built-in sample data, task by task, and shows how to read the result before you spend anything.
Read the article