Submit one anonymized process dataset — get a founder-reviewed SPC + capability report.Limited to first 10 users

Founder-reviewed SPC + capability report

Introduction

A capable product is the intersection of twenty conversations, not one. New Product Introduction (NPI) programs that miss a launch date, blow a Cpk target at PPAP, or trigger a field corrective action almost always trace back to a Voice that was never formally heard. Customers told you what good looks like; the process never told you whether you could deliver it; the supplier never told you what they could hold; regulators never confirmed you could ship it; and operators on the line never told you that the work instruction did not match reality.

In Lean Six Sigma, every one of those conversations has a name. They are the Voices of: Voice of the Customer (VOC), Voice of the Business (VOB), Voice of the Process (VOP), Voice of the Employee (VOE), Voice of the Market (VOM), Voice of the Engineer (VoEng), Voice of the Supplier (VOS), Voice of the Regulator (VOR), Voice of the Technology (VOT), Voice of the Data (VOD), Voice of the User (VOU), Voice of the System (VOSy), Voice of the Factory (VOF), Voice of the Value Stream (VOVS), Voice of the Risk (VORisk), Voice of the Customer's Customer (VOCC), Voice of the Program (VOPg), Voice of the Environment (VOEnv), and Voice of the Standard Work (VOSW). Senior manufacturing, NPI, and product development engineers — and the Black Belts who support them — must hear all of them, weigh them against each other, and resolve conflicts with data rather than with seniority.

This article defines each Voice, explains why Voice of the Process (VOP) outranks Voice of the Customer (VOC) when the two collide, maps each Voice to a DMAIC phase and to the analytical evidence that should be produced, distills a RASCI ownership model across the Product Development → NPI → Sustaining lifecycle, and gives you a Voice-driven gate-review playbook you can apply to your next program.

The twenty Voices that govern a product program

Each Voice answers a different engineering question. Treat them as independent inputs that must be triangulated, never as synonyms.

VOC — Voice of the Customer

Direct, external customer needs and value expectations, expressed or observed

Product Management

Interviews, surveys, NPS/CSAT, complaints, warranty, ethnography, Kano

CTQ tree, Kano model, prioritized requirement spec

VOB — Voice of the Business

Enterprise needs for profitability, growth, and strategic fit

Finance and Executive Sponsors

Business case, ROI/IRR, price corridor, capacity plans

Approved charter, gate scorecard, investment envelope

VOP — Voice of the Process

Measured performance and capability of processes as-is or to-be

Manufacturing Engineering

Time-ordered process data, control charts, capability studies

SPC charts, Cp/Cpk/Pp/Ppk, control plan

VOE — Voice of the Employee

Frontline operator insights on safety, ergonomics, quality, and flow

Frontline Supervisors, HR, EHS

Gemba walks, kaizen events, JHAs, near-miss reports, skills matrices

PFMEA inputs, ergo risk register, improved standard work

VOM — Voice of the Market

Competitive dynamics and macro trends shaping customer value across the market

Marketing and Strategy

Win/loss analysis, competitive teardowns, analyst reports, pricing intelligence

Positioning brief, pricing model, segmentation map

VoEng — Voice of the Engineer

Engineering-derived requirements, constraints, and technical judgments translating customer needs into feasible, testable specifications

Design and Systems Engineering

QFD/HoQ HOWs, DFMEA, simulations, prototypes, tolerance stack-ups

Engineering specs, verification plans/results, design records

VOS — Voice of the Supplier

Supplier capability, capacity, compliance, and delivery performance

Supplier Quality Engineering

PPAP/FAI status, IMDS, lead times, quality history, audits

Supplier Cpk, scorecard, approved supplier list, control plan

VOR — Voice of the Regulator

Requirements arising from laws, standards, and audits

Regulatory Affairs and Quality

ISO 13485, IATF 16949, FDA QMSR, AS9100, AIAG core tools, audit reports

DHF, PPAP package, regulatory traceability matrix, certifications

VOT — Voice of the Technology

Feasibility and readiness of technologies and architectures to meet requirements

Engineering, Architecture, Systems

TRL scores, prototypes, simulations, constraints

Concept selections, design limits, technical roadmap

VOD — Voice of the Data

Objective evidence from measurements, tests, and analytics

Data, CI, IE, QA, Ops, Finance

SPC trends, DOE results, MSA, telemetry, dashboards

Validated conclusions, control limits, dashboards

VOU — Voice of the User

Real-world use context, usability, misuse, and serviceability

UX/HFE, Service, Dealers, Safety, Engineering

Contextual inquiry, field rides, service tickets, telemetry

Use cases, HFE requirements, service design inputs

VOSy — Voice of the System

Interactions and constraints across subsystems and interfaces

Systems Engineering, PD, ME, QA

Interface control docs, tolerance stacks, scans, system DFMEA

Interface control docs, integration test plans

VOF — Voice of the Factory

Buildability, repeatability, safety, and cost in production

ME, Operations, QA, EHS, IE

DFM/DFA, work instructions, J/F lists, line balance, time studies

Manufacturing plan, validated WI, PPAP, safe standard work

VOVS — Voice of the Value Stream

End-to-end flow performance from suppliers to customer

Lean/CI, Ops, Supply Chain, Logistics

Lead time, inventory, dock-to-dock, supplier OTD

Future-state map, pull plans, heijunka box

VORisk — Voice of the Risk

Aggregate risk picture across design, process, safety, schedule, and supply

QA, EHS, PD, ME, PMO, Ops

DFMEA/PFMEA, bow-tie/fault tree, incidents, audits

Risk register, countermeasures, control plans

VOCC — Voice of the Customer's Customer

Downstream channel needs (dealer or end-user of our B2B customer)

B2B Product, OEM partners, Dealers, Sales

Dealer meetings, channel feedback, warranty data

Channel requirements, dealer programs, QFD cascade

VOPg — Voice of the Program

Execution constraints and commitments across scope, time, cost, and quality

PMO, Functional leads, Execs

Integrated schedule, RASCI, RAID logs, capacity conflicts, gate decisions

Decisions, approvals, escalations, status, gated evidence

VOEnv — Voice of the Environment

Environmental performance and stewardship obligations

EHS/Sustainability, Regulatory, Ops, Supply Chain

SDS/IMDS, LCA, emissions/VOC, waste logs, permits

EHS approvals, sustainability KPIs, mitigations

VOSW — Voice of the Standard Work

Best-known-method documents and controls that ensure repeatability

Ops, ME, QA, IE, EHS, IT

WI/SOPs, training plans, check sheets, LPA/Kamishibai results

Released WI/SOPs, audit plan, LPA schedule

Why Voice of the Process outranks Voice of the Customer

This is the single most important hierarchy in product development, and the one most often inverted. Customers describe the target; the process describes the achievable. A specification that the process cannot hold is not a requirement — it is a defect waiting to happen.

A worked example clarifies the rule. A customer requests a clearance of 1.00±0.05 mm at the assembly. A short-run capability study on the current process shows a long-term Ppk = 0.78 against that tolerance. Three responses are possible:

Only option three is engineering. The discipline that forces it is to prove process capability before signing the requirement, not after. This is why Six Sigma Center frames VOP ahead of VOC in every workflow: capability is the truth that defines what the customer can actually be promised. When VOP and VOC stalemate — when a sales commitment and a manufacturing limit point in opposite directions — VOD (Voice of the Data) is the impartial referee: capability indices, hypothesis tests, and confidence intervals settle the argument with evidence rather than seniority.

The corollary holds for design. A tolerance stack-up that mathematically meets a requirement under worst-case assumptions, but whose contributing dimensions sit in the tail of the supplier's process distribution, will fail in production. VoEng without VOP and VOS is wishful drafting. Use a Gap Stack-Up analysis with Monte Carlo overlays to expose the gap between what the design assumes and what the suppliers will actually deliver — see our tolerance stack-up methodology for the underlying math.

Mapping each Voice to DMAIC and to an analysis module

Every Voice produces an evidence artifact, and every artifact maps to a DMAIC phase and to a recommended analysis. The table below is the operating contract a Black Belt should enforce on any NPI program.

VOC

Define

CTQ tree, Hypothesis Testing on customer-segment differences

Ranked CTQ list with measurable specs

VOB

Define and Control

Predictive Modeling on cost and demand, sensitivity analysis

Approved business case and gate scorecard

VOP

Measure and Analyze

SPC Monitoring, Process Capability (Cp/Cpk/Pp/Ppk)

Capability statement per CTQ

VOE

Measure and Improve

Gage R&R for operator-induced variation, Pareto on near-misses

PFMEA, training plan, ergo risk register

VOM

Predictive Modeling on adoption, Hypothesis Testing on segment uplift

Positioning brief, pricing decision

VoEng

Analyze and Improve

Gap Stack-Up (worst-case, RSS, Monte Carlo), DOE, Distribution & Normality

Tolerance allocation, design verification matrix

VOS

Measure and Control

Supplier Cp/Cpk, Hypothesis Testing on supplier-to-supplier means

Approved supplier list with control plan

VOR

Regulatory traceability matrix, Process Capability against safety-critical CTQs

DHF or PPAP submission

VOT

Define and Analyze

TRL assessment, DFMEA, system modeling, feasibility DOE

Concept selection, design limits, technical roadmap

VOD

All phases (decision and validation gates)

DOE, SPC, regression, Hypothesis Testing, Distribution & Normality

VOU

Use-case FMEA, task analysis, Hypothesis Testing on error rates

HFE requirements, service design inputs

VOSy

Tolerance analysis, interface DFMEA, system DOE

VOF

Improve and Control

PFMEA, line-balance studies, FPY trend with SPC

Manufacturing plan, validated WI, PPAP

VOVS

Value-stream mapping, lead-time Distribution & Normality, throughput SPC

VORisk

All phases (gated reviews)

DFMEA/PFMEA RPN trending, 5-Why, 8D, fault tree

VOCC

QFD cascade, journey mapping, Hypothesis Testing on attach rate

Channel requirements, dealer programs

VOPg

All phases (governance cadence)

Stage-Gate burn-down, RAID trend, on-time-gate Pareto

Gate decisions, approvals, escalations, status

VOEnv

Design and Control

LCA, emissions trend with SPC, regulatory traceability

EHS approvals, sustainability KPIs, mitigation plans

VOSW

LPA/Kamishibai audit Pareto, deviation-rate SPC

The pattern is intentional: VOC, VOM, and VOCC frame the Define phase; VOP, VOS, and VOD dominate Measure and Analyze; VoEng, VOE, VOU, VOSy, VOVS, and VOT drive Improve; VOR, VOB, VOF, VOSW, VOEnv, VORisk, and VOPg police the Control gate.

RASCI ownership across PD, NPI, and Sustaining

Voices fail when ownership is ambiguous. Distilled below is a senior-engineering RASCI for each Voice across the lifecycle. R = Responsible, A = Accountable, S = Supporting, C = Consulted, I = Informed. Two new accountable columns appear because the 20-Voice matrix demands them: EHS/Sustainability (owns VOEnv) and PMO/Program (owns VOPg and VORisk).

A, R

A practical rule: every Voice must have exactly one A at every gate. Two Accountables means no Accountable.

Twelve failure modes when a Voice is missed

Each of the cases below is drawn from common NPI failure patterns documented in industry post-mortems. Each is short by design — a senior engineer recognizes the shape immediately.