When customer expectations and organisational priorities point in different directions, the answer is not to choose one voice and silence the other. The stronger approach is to understand what each voice is saying, translate the requirements into measurable Critical to Quality (CTQ) characteristics, and use process data to design a sustainable solution.
In the realm of Lean Six Sigma, three perspectives guide this work:
- Voice of the Customer (VOC): What customers need, expect, and value.
- Voice of the Business (VOB): What the organisation must achieve to remain viable, compliant, and competitive.
- Voice of the Process (VOP): What the process is actually delivering, based on evidence and data.
When these voices disagree, the winner should be neither the customer nor the business in isolation. The winner should be the best-informed decision: one that protects essential customer requirements while improving the economics and capability of the process.
Understanding VOC, VOB, and VOP
Voice of the Customer: What matters to the market
VOC captures customer expectations in both direct and indirect forms. Direct sources may include interviews, surveys, complaints, service reviews, focus groups, and support tickets. Indirect sources include repeat-purchase data, abandonment rates, warranty claims, and customer behaviour.
Customers may express needs broadly:
- “I need reliable delivery.”
- “The service must be accurate.”
- “I want a fast response.”
- “The product should work correctly the first time.”
These statements are valuable, but they are not yet precise enough to manage operationally. Lean Six Sigma practitioners translate them into measurable CTQs, such as:
- 99% of orders delivered by the promised date
- Less than 1% invoice error rate
- Customer support response within four business hours
- First Pass Yield above 98%
VOC establishes the performance requirements that define customer value.
Voice of the Business: What the organisation must sustain
VOB represents the organisation’s strategic, financial, regulatory, and operational requirements. It may include:
- Cost reduction
- Revenue and margin targets
- Capacity improvement
- Compliance obligations
- Risk reduction
- Employee capability
- Market competitiveness
- Return on investment
VOB is not simply a demand to reduce spending. Its fundamental purpose is to clarify the conditions required for the organisation to serve customers sustainably.
For example, a business may need to reduce fulfilment cost by 8%, increase throughput by 15%, or maintain a gross margin above 30%. These targets create necessary boundaries for improvement decisions.
Voice of the Process: What the data reveals
The voice of the process is the process speaking through its performance data. It describes what is happening: not what customers hope will happen or what leaders would prefer to happen.
Typical VOP measures include:
- Cycle time
- Defect rate
- Process capability
- Throughput
- First Pass Yield
- Rolled Throughput Yield
- Waiting time
- Rework
- Variation
- Cost per transaction
VOP helps answer a critical question: Can the current process consistently meet the CTQs defined by the customer and business?
A process may have an average cycle time of 22 minutes, for example, but individual observations may range from 12 to 49 minutes. The average alone does not reveal whether the process is stable or capable. Control charts, capability analysis, and stratified data provide a more reliable view.
A practical example: cost reduction versus quality expectations
Consider a healthcare claims processing team. Customers: patients, providers, and insurers: expect claims to be processed accurately and promptly.
The three voices
VOC:
Providers expect 98% of clean claims to be processed within five business days, with an error rate below 1%.
VOB:
The organisation wants to reduce processing cost from $5.80 to $4.90 per claim, generating annual savings of approximately $540,000 across 600,000 claims.
VOP:
Current process data shows:
- Average processing time: 7.2 business days
- First Pass Yield: 92.4%
- Rework rate: 7.6%
- Cost per claim: $5.80
- 95th-percentile processing time: 13 business days
Leadership initially proposes removing a manual verification step and reducing staff review time. The change could lower direct labour cost by approximately $0.70 per claim, apparently exceeding the savings target.
However, a pilot produces a different result:
- First Pass Yield falls from 92.4% to 88.1%
- Rework rises from 7.6% to 11.9%
- Average processing time increases to 8.4 days
- Provider complaints increase by 26%
- Total cost rises to $6.10 per claim when rework and escalations are included
The proposed cost reduction satisfies a narrow interpretation of VOB but violates VOC and exposes the organisation to higher total cost. The process data demonstrates why.
The right response is not to preserve every existing activity. Instead, the team should investigate the root causes of rework and identify whether the verification step can be redesigned, automated, or targeted to high-risk claims.
How CTQs align the three voices
CTQs provide the bridge between strategic intent, customer expectations, and operational performance.
A useful CTQ alignment table might look like this:
| CTQ | VOC requirement | VOB requirement | VOP baseline | Improvement target |
|---|---|---|---|---|
| Processing time | ≤ 5 days for clean claims | Support capacity at current headcount | 7.2 days average | ≤ 5 days average |
| Accuracy | ≥ 99% | Avoid compliance exposure | 97.1% | ≥ 99.2% |
| Cost per claim | Value reliable service | ≤ $4.90 | $5.80 | ≤ $4.90 |
| First Pass Yield | Minimal follow-up | Reduce rework cost | 92.4% | ≥ 98% |
This table makes trade-offs visible. It also prevents the team from optimising one metric at the expense of the entire system.
A CTQ should normally include:
- A measurable characteristic
- A customer or business requirement
- An operational definition
- A specification limit or target
- A measurement method
- An owner responsible for monitoring it
The goal is not to make every requirement perfect. The goal is to distinguish essential requirements from preferences, then focus improvement effort where it creates the greatest combined value.
Using DMAIC to resolve disagreement
Lean Six Sigma’s DMAIC framework provides a disciplined way to balance VOC, VOB, and VOP.
1. Define: establish the real problem
In Define, collect VOC and VOB information before selecting a solution. Create a clear business case, problem statement, project scope, and goal statement.
For the claims example, the project goal might be:
Reduce average clean-claim processing time from 7.2 to 5 business days, improve First Pass Yield from 92.4% to at least 98%, and reduce total cost per claim to $4.90 or less by the end of Q4.
A strong business case financial calculator can help quantify the financial opportunity, while the CTQ Tree Alignment Calculator can structure customer requirements.
2. Measure: establish a trustworthy baseline
Measure the process before debating solutions. Define the data carefully:
- What counts as a clean claim?
- When does processing time begin and end?
- How is an error classified?
- Are rework and escalation costs included?
- Which claim types should be analysed separately?
A measurement system that combines financial data, customer feedback, and operational performance gives a balanced baseline.
3. Analyse: identify root causes
During Analyse, compare VOP performance with VOC requirements and VOB priorities. Use tools such as:
- Pareto charts
- Process maps
- Value Stream Mapping
- Cause-and-effect diagrams
- Hypothesis tests
- Regression analysis
- Control charts
- Stratification by claim type, payer, employee, and error category
The team may discover that 72% of rework comes from three input fields, while high-risk claims represent only 18% of total volume. That insight supports a targeted verification approach rather than removing verification from every claim.
4. Improve: design a solution that satisfies all three voices
An effective improvement may include:
- Automated validation for common data-entry errors
- Risk-based manual review
- Standardised work for complex claims
- Better information requirements at intake
- Error-proofing at the source
- Daily monitoring of First Pass Yield and processing time
Suppose the pilot delivers these results:
- First Pass Yield: 98.6%
- Average processing time: 4.8 days
- Rework rate: 1.4%
- Cost per claim: $4.72
- Provider complaints: down 31%
This solution meets the customer’s quality requirement, achieves the business cost target, and demonstrates improved process capability.
5. Control: prevent the balance from drifting
A solution is not complete when the pilot succeeds. The Control phase protects the gains.
Build a control plan that monitors:
- CTQ performance
- Customer complaints
- First Pass Yield
- Rework
- Cost per transaction
- Processing time
- Compliance exceptions
Use a dashboard that displays VOC, VOP, and VOB measures together. If cost per claim improves while error rates exceed specification limits, the change is not successful. If customer satisfaction remains high but the process requires unsustainable overtime, the improvement also requires further attention.
A five-step framework for balancing VOC and VOB
When priorities conflict, use this practical framework:
-
Identify the non-negotiables.
Separate regulatory, safety, reliability, and essential customer requirements from optional features. -
Translate expectations into CTQs.
Replace general statements with measurable targets and specification limits. -
Expose total cost, not just direct cost.
Include rework, returns, complaints, delays, escalation, compliance exposure, and lost business. -
Use the voice of the process to locate leverage points.
Look for variation, bottlenecks, waiting, defects, and unnecessary handoffs before cutting resources. -
Test changes against all three voices.
A successful improvement must protect customer value, support business sustainability, and remain stable in the real process.
Who wins when they disagree?
The short answer is: the CTQ-driven decision supported by reliable process data.
VOC defines what customers value. VOB defines what the organisation must sustain. VOP reveals the current reality and identifies where improvement is possible. None of these perspectives is complete on its own.
Professionals pursuing Six Sigma training learn to connect these voices through DMAIC, data analysis, process capability, and structured problem-solving. For foundational awareness, the Yellow Belt course helps team members support improvement projects and understand how customer and business requirements become operational measures.
The most effective organisations do not treat cost and quality as permanent opponents. They use Lean Six Sigma to remove the waste and variation that make them appear to conflict in the first place.
Build the capability to balance customer expectations, business priorities, and process performance: pursue accredited Lean Six Sigma training and professional certification today.
Kaizen. Kai-Care. Kai-Done. ( Lean Six Sigma)
