Voice of the Customer (VOC) is one of the foundational tools in Lean Six Sigma, and often one of the most under-used, because it’s easy to assume you already know what customers want rather than going and finding out. For Ops leaders sponsoring improvement work, and for HR and L&D teams deciding what a Lean Six Sigma investment should actually build capability in, VOC is often the difference between a programme that pays for itself and one that produces well-executed improvements nobody outside the business notices.

This article explains what Voice of the Customer is, how customer insight can be gathered and translated into measurable requirements, why it matters in improvement projects and some of the key considerations to keep in mind when using it effectively. 

Voice of the Customer is the structured process of capturing customer needs, expectations and feedback, and translating them into clear, measurable requirements that can guide improvement work.

The “customer” here isn’t limited to the end consumer. In Lean Six Sigma, VOC can apply equally to internal customers, such as the next team or department in a process, and external customers, such as the people or organisations ultimately buying the product or service.

Either way, the principle is the same: improvement should be driven by what matters to the person receiving the output, not by assumptions made internally.

VOC data generally falls into two categories:

• Explicit feedback is what a customer tells you directly, such as a complaint, survey response, interview comment or review.
• Implicit feedback is what a customer’s behaviour tells you, whether they say anything or not. This could include return rates, changes in ordering patterns, repeat contacts with customer service or a drop in repeat purchases.

Looking at both is an important part of Voice of the Customer analysis. A customer might tell you that everything is fine, while their behaviour or other operational data suggests there is an issue that hasn’t been raised directly.

Relying on explicit feedback alone can therefore miss a lot. Plenty of customers who are dissatisfied never say so directly. They may simply stop buying, switch suppliers, reduce their orders or quietly work around a problem.

In some cases, the most telling piece of VOC data is a customer who used to buy from you and no longer does.

There isn’t one single method for collecting Voice of the Customer data. The most useful approach will depend on the type of customer and the process being investigated.

Common VOC methods include:

• Customer interviews to explore needs, expectations and experiences in more detail.
• Surveys and questionnaires to gather feedback from a larger number of customers.
• Complaints and customer service data to identify recurring issues or points of friction.
• Reviews and feedback to understand what customers value or find frustrating.
• Sales and account management feedback where teams have regular conversations with customers.
• Observation and customer behaviour to identify what customers do, rather than relying only on what they say.
• Operational data such as returns, repeat orders, cancellations, delivery performance or support contacts.

The aim isn’t simply to collect as much feedback as possible. It’s to gather relevant information from reliable sources and look for patterns that help explain what customers need.

Different sources can also tell different parts of the story. Bringing them together can give improvement teams a more complete picture than relying on a single survey, complaint or conversation.

VOC can reveal a gap between what customers need and what they are currently experiencing. That gap can provide a starting point for improvement.

The opportunity might be obvious, such as repeated complaints about late deliveries. In other cases, it may be less direct, such as a change in buying behaviour, an increase in support requests or customers developing workarounds to compensate for a problem.

The important point is that VOC helps the team investigate what matters to the customer first, before deciding what needs to be improved.

This can prevent teams from focusing on internal measures simply because they are easy to see or because a particular problem has become the loudest issue within the business.

To put this into context, let’s take an example from a materials supplier who has just received the following feedback from one of its manufacturing customers:

“Order quality has been consistently good, no complaints here.”

On the surface this feedback looks positive but separately the account manager notices that this customer’s order pattern has changed: they’ve started placing smaller, more frequent orders over the past few months, instead of the larger monthly orders they used to place.

The verbal feedback was positive, but the behaviour tells a different story. 

This also highlights an important point about communication between teams and departments. The account manager may be the first to notice a change in customer behaviour, while colleagues in sales, customer service, operations or quality may have different pieces of the picture. Bringing these insights together can help the business understand what is really happening from the customer’s perspective, rather than relying on one source of feedback alone.

Raw VOC data isn’t specific enough to act on directly. A signal like “orders have shifted to smaller, more frequent batches” needs to be translated into something a team can actually design, measure and improve against.

This is where Critical to Quality (CTQ) trees can help.

A CTQ tree breaks a broad customer signal down into the underlying need, and then into a specific, measurable requirement. The aim is to turn what the customer values into something the improvement team can monitor and work towards.

In the materials example above, that might look like::

A practical way to build this out is to work through a short sequence:

1. Gather VOC data from a range of reliable sources, not just one.
2. Identify recurring themes across that data, rather than reacting to a single comment.
3. Translate each theme into a specific, measurable CTQ statement.
4. Prioritise CTQs based on impact and feasibility.
5. Feed prioritised CTQs into the project scope, so improvement work is aimed at what genuinely matters.

VOC isn’t a one-off step completed just at the start of a project, done well, it should run through every stage of how your improvement project is planned, carried out and checked.

Scoping the Problem

VOC shapes the problem itself, identifying which customer group is affected and what they actually need, rather than what you assume they need.

Setting a Starting Point: 

The measurable requirements drawn from VOC become the metrics the project tracks, with a clear baseline recorded before any change is made.

Understanding what’s driving it

Patterns in VOC data help prioritise which issues are having the biggest impact on your customer satisfaction, rather than the issue that’s loudest or easiest to fix.

Making the Change

Proposed solutions are checked against the customer requirements they’re meant to address, and validated with customers wherever possible before being rolled out fully.

Keeping it in Place

VOC data collection continues after implementation, allowing the team to confirm that the improvement is delivering the intended outcome for customers and make adjustments if their expectations change over time. 

Treating VOC as a continuous input, rather than something gathered once at the outset, is what keeps improvement work genuinely customer-led from start to finish.

A few beliefs consistently get in the way of good VOC practice, even in teams that want to do it well.

“Customers won’t give us feedback.” Often, this is less about customers being unwilling and more about not being asked in a structured way, or only being asked at the very end of a process when it’s too late to act on what’s said.

“We already know what they want.” Internal assumptions can be a poor substitute for actual customer input, particularly when the feedback is inconvenient or contradicts what a team has already decided to build.

“Feedback is only useful once, at the start.” Customer needs shift over time, and a CTQ that was accurate a year ago may no longer reflect what matters most today.

Beyond these misconceptions, practical obstacles are common too: feedback channels that are unclear or inconsistent, VOC data that sits in one team without reaching the people running improvement projects, and conflicting feedback from different customer groups that never gets properly prioritised.

None of these are reasons to abandon VOC. They’re reasons to build it into the process deliberately, rather than treating it as something that happens informally.

Getting Voice of the Customer right gives improvement teams a clearer understanding of what customers genuinely need, rather than relying on assumptions or internal priorities.

If that understanding is inaccurate or incomplete, a project can focus on solving the wrong problem or improving something that customers don’t value.

Used effectively, VOC helps teams prioritise improvements that have a meaningful impact on the customer while giving them a clear basis for measuring whether a change has delivered the intended outcome.

It can also improve communication between teams and departments by creating a shared understanding of what the customer needs and what the business is trying to achieve.

For organisations using Lean Six Sigma to build internal improvement capability, understanding VOC is an important part of developing a structured approach to problem solving.

Employees need to be able to gather genuine customer insight, interpret different sources of feedback and data, distinguish between explicit and implicit signals, translate customer needs into measurable requirements and use those requirements throughout an improvement project.

Voice of the Customer is a core tool taught across CQM’s Lean Six Sigma commercial and apprenticeship programmes from Yellow Belt through to Black Belt level, where learners build the skills to gather genuine customer insight, distinguish explicit from implicit signals, and translate both into measurable requirements for sustainable structured improvement activity.  

It’s taught as part of the wider structured problem-solving approach that runs through a Lean Six Sigma project, giving learners the confidence to define improvement projects around what genuinely matters. 

If you’re an Ops, HR or L&D leader weighing up how Lean Six Sigma training could strengthen improvement capability in your organisation, we’d be happy to have an open, no-pressure conversation.

Get in touch with our team using the contact form below.

Back to top