Menu
Voice of the Customer (VOC): Turning What Customers Say into What You Build

Voice of the Customer (VOC): Turning What Customers Say into What You Build

Voice of the Customer (VOC) is the structured capture of customer needs in their own words, then translated into measurable requirements. Learn VOC collection methods, how to structure the data, and how it feeds CTQs and improvement projects.
Voice of the Customer (VOC): Turning What Customers Say into What You Build

Voice of the Customer (VOC) is the disciplined practice of collecting what customers actually need and expect, in their own words, and translating it into requirements a factory can measure and act on. It is the raw material of quality: before you can decide what to build, control, or improve, you have to know what the customer values, and you have to capture it without distorting it through internal assumptions. VOC is the front end of nearly every serious quality method, and getting it wrong means optimizing a process toward the wrong target.

Why VOC is harder than it looks

The trap in VOC is that customers speak in outcomes and feelings, not specifications. They say a package is "annoying to open," a finish "looks cheap," or a delivery is "always late." None of those is directly buildable. At the same time, engineers are tempted to skip straight to solutions they already have in mind. VOC exists to slow that jump down: first capture the need faithfully, then translate it, and never let the translation quietly rewrite what the customer said. The output of good VOC is a set of customer needs you can trace back to a real source.

How to collect the voice of the customer

No single channel captures the full picture, so VOC combines several:

  • Interviews: one-to-one conversations that reach the "why" behind a stated need, ideal for depth.
  • Surveys: structured questions that quantify how widely a need is held across a population.
  • Complaints and warranty data: unsolicited, brutally honest signals about where the product fails in the field.
  • Direct observation: watching customers actually use the product, which surfaces needs they never articulate.
  • Field and sales feedback: the patterns your front-line people hear repeatedly.

Reactive sources like complaints tell you what already went wrong; proactive sources like interviews and observation tell you what customers want next. A strong VOC program uses both.

Structuring the raw voice

Raw VOC is messy, so it is usually organized with an affinity diagram, grouping many individual statements into themes, and then ranked for importance. A common next step is the Pareto analysis logic of separating the few needs that dominate satisfaction from the many that barely move it. The goal is a short, prioritized list of themes, each still anchored to real customer language, ready to be translated into engineering terms.

From VOC to measurable requirements

VOC only becomes useful on a shop floor once it is translated into something measurable. That translation is exactly the job of critical-to-quality (CTQ) characteristics: a vague need such as "the seal never fails" becomes a seal-width target with a tolerance. Before any of that, framing the process you are improving with a SIPOC diagram keeps the VOC pointed at the right customers and outputs. In a DMAIC project VOC sits at the very start of the define phase, because everything measured, analyzed, and controlled downstream is judged against what the customer said mattered. Once requirements exist, a control plan and, where failure is a risk, a structured FMEA keep the process honest against them.

Where Fabrico fits: closing the loop with real production data

VOC is human work, and Fabrico does not run your interviews or build your affinity diagrams. Where Fabrico matters is the other half of the loop: proving whether the line is actually delivering what the customer asked for. Once VOC has been translated into measurable characteristics, Fabrico's real-time OEE and production monitoring captures the machine and output data behind them, including on machines with no PLC through computer-vision monitoring, and it tracks scrap rate so a drift away from a customer-critical characteristic shows up immediately rather than in a warranty claim months later. Its CMMS keeps the equipment behind those characteristics maintained. The customer tells you what good looks like; Fabrico gives you the honest data that shows whether you are hitting it.

Common VOC mistakes

Teams distort VOC in familiar ways. They translate needs into specs too early and lose the original voice. They rely on a single channel, usually complaints, and miss the needs of quiet satisfied customers. They survey the wrong population. And they treat VOC as a one-time project rather than a continuous input that should update as customers and markets change. Kept faithful and ongoing, VOC is the compass every other quality tool steers by.

Frequently Asked Questions

What is the difference between VOC and a CTQ?

VOC is the customer's need stated in their own language, such as "it should not leak." A CTQ is the measurable characteristic that need translates into, such as a specific seal compression with a tolerance. VOC is the input; CTQs are the engineered, measurable output of translating it. You need the VOC first, or the CTQ risks measuring the wrong thing.

Which VOC collection method is best?

There is no single best method. Interviews give depth, surveys give breadth, complaints give honesty, and observation surfaces unspoken needs. A sound VOC program combines several so that no single channel's blind spot dominates the picture.

Does Fabrico collect voice-of-customer data?

No. VOC gathering is a human research activity. Fabrico is a real-time OEE monitoring and CMMS platform, so its role is downstream: once VOC has become measurable characteristics, Fabrico provides the accurate production data that shows whether the line is actually meeting them.

Want to see whether your line is delivering what customers asked for, in real time? Book a Fabrico demo and watch live OEE and scrap data become the proof behind your voice-of-customer work.

Latest from our blog

Hour-by-Hour Boards: Catching a Bad Shift While It Can Still Be Saved
Read now
Hydrostatic Pressure Testing: Proving Containment Before Service Does
Read now
Plant Winterization: Freeze Protection as a Scheduled Campaign
Read now
Dead Leg Management: The Pipework Nobody Flows Through
Read now
Define Your Reliability Roadmap
Validate Your Potential ROI: Book a Live Demo
Define Your Reliability Roadmap
By clicking the Accept button, you are giving your consent to the use of cookies when accessing this website and utilizing our services. To learn more about how cookies are used and managed, please refer to our Privacy Policy and Cookies Declaration