Capturing the Voice of the Customer: A Practical How-To for Process Improvement Teams

Every Lean Six Sigma project starts with the same question: what does the customer actually need? The answer is rarely obvious, often contested, and almost always more nuanced than the initial project brief suggests. The Voice of the Customer (VOC) is the structured process of finding out -- and the Critical-to-Quality (CTQ) tree is the tool for translating what you find into measurable process requirements.

In 2022, VOC is more important than ever. Labour shortages have reduced the capacity of service delivery teams, inflation has compressed budgets, and customers -- whether citizens using a government service or contractors managing a capital project -- are less tolerant of process failures than they were before the pandemic disrupted their expectations. The following is a practical how-to for teams running VOC as part of a DMAIC project.

How to Gather VOC Data

• Structured interviews: one-on-one conversations with customers following a semi-structured guide. Most reliable for understanding the "why" behind needs. Aim for 8 to 12 interviews per major customer segment. Record with permission or take detailed notes; the exact words customers use matter.

• Surveys: efficient for quantifying how widely a need is shared, but poor at revealing new needs you did not already know to ask about. Use surveys to validate findings from interviews, not to replace them.

• Complaint and incident data: systematic review of complaints, service failures, and incidents is one of the most underused VOC sources. It captures the needs that customers are already telling you about -- but through a different channel. In public-sector projects, access requests, appeals, and ombudsman referrals are equivalent sources.

• Observation: watching customers interact with your process reveals needs they cannot articulate. Shadowing a contractor completing a procurement form or observing a clerk processing an application often surfaces requirements that no interview or survey would catch.

How to Build a CTQ Tree

1. Start with the raw VOC data -- the exact words. Group customer statements by affinity. Look for themes: speed, accuracy, ease of use, reliability, responsiveness. These themes become your quality dimensions.

2. For each quality dimension, define the driver. "Fast" becomes "permit application processed within five business days". "Accurate" becomes "zero errors on the issued permit". Be specific: a CTQ must be measurable.

3. For each driver, define the performance standard. "Processed within five business days" needs a specification limit: 95 percent of applications processed within five business days. This is the CTQ. Your process must be capable of meeting it.

4. Prioritise CTQs by customer impact and current process capability. Not every CTQ is equally important, and not every gap is equally severe. A CTQ where current performance is 60 percent against a 95 percent target deserves more attention than one where performance is 90 percent against a 95 percent target.

5. Use the CTQ tree to define your project scope. A DMAIC project should focus on one or two CTQs. A project that tries to address every customer need simultaneously is a programme, not a project, and it will not close.

XNM supports public-sector and capital-project clients in applying Lean Six Sigma process improvement methods, including VOC analysis and CTQ definition. Connect with XNM's strategic advisory team to discuss how VOC could ground your next improvement initiative.