Define the system and unit of analysis
Specify process, population, product, time window, boundaries and aggregation level. Without a defined unit of analysis, measures and comparisons may represent different phenomena.
TECHNICAL GUIDE · STRUCKEL TOOLS
VOC-01 · Continuous improvement
CTQ / VOC Tree
Converts the voice of the customer into drivers and measurable critical requirements, reducing the risk of turning vague needs into arbitrary solutions.
VOC · CTQ · necessidades · direcionadoresFormulários Struckel
01
MANAGEMENT QUESTION
The problem the tool must make decidable.
Before opening a form, define the question that must be answered. A management tool is useful when it reduces ambiguity, exposes assumptions and makes clear which decision will be made from the evidence produced.
VOC-01How can customer language be converted into measurable requirements without jumping directly to a team-preferred solution?
Continuous improvement requires separating opinion from evidence and turning a broad problem into a sequence that can be observed, tested and revised. The tool creates value when it starts from an explicit current condition, applies criteria before concluding and ends with a verifiable decision — not merely a completed document.
Use it when you need to reduce variation, solve recurring problems, test changes, prioritize causes or preserve learning beyond the meeting in which it was produced.
02
METHOD ARCHITECTURE
Technical construction: from operational definition to evidence.
A tree starts from a broad need or concept and decomposes it through explicit relationships. Each level should answer a different question, avoiding the jump from a generic voice directly to a convenient metric.
Define criteria before evaluation
Translate abstract concepts into operational definitions, scales, classification rules and data sources. Criteria should exist before the result to reduce retrospective interpretation.
Preserve traceability
Link each conclusion to data, observations, assumptions and owners. When a score is used, retain its components; when a hypothesis is used, record how it will be tested.
Review the tree bottom-up: does a measure truly represent the requirement above it? Are two branches duplicating the same need? Are there important drivers without measurable characteristics?
03
WORKED EXAMPLE
How the method behaves in a real situation.
“I want fast service” is not a CTQ. A tree can translate it into “time to start service” and “total resolution time,” with operational definitions and targets grounded in customer evidence and capability rather than internal convenience.
The example is intentionally specific. Numbers illustrate the reasoning and are not universal benchmarks: limits, scales and targets must be defined for the process being analyzed.04
MEASUREMENT AND INTERPRETATION
What to observe so the document does not become mere form filling.
Measures should serve reasoning. Whenever possible combine outcome, process and contextual evidence. For time series, look for patterns and variation rather than only point-in-time before/after comparisons.
01VOC need
02drivers
03measurable CTQ
04operational definition
05LSL/USL or target when applicable
Consistency test
Ask whether another person, using the same definitions and evidence, would reach a similar interpretation. If the answer depends heavily on individual judgment, refine the operational definition, scale or data source.
05
LIMITATIONS AND GOVERNANCE
The tool supports decisions; it does not replace judgment, context and validation.
Established method/tool in professional and academic literature; exact implementation should be tailored to context.
A CTQ tree structures translation; it does not prove importance. Priorities should be supported by customer evidence and, where relevant, QFD/Kano methods.
Define an owner, review frequency, official data source and condition for reopening the decision. Link actions to deadlines and indicators, hypotheses to tests, and risks to treatment and follow-up.
DefinitionEvidenceInterpretationDecisionReview
06
METHODOLOGICAL BASIS
References for deeper study of the method.
The references below support the methodological family or principle used. Struckel’s digital implementation operationalizes application, documentation and traceability; it does not change the conceptual limits of the original sources.
AKAO_QFD
Akao Y. Quality Function Deployment: Integrating Customer Requirements into Product Design. Productivity Press; 1990.
KANO
Kano N, Seraku N, Takahashi F, Tsuji S. Attractive Quality and Must-Be Quality. Journal of the Japanese Society for Quality Control. 1984;14(2):39–48.
ASQ_SIPOC
Open reference American Society for Quality. SIPOC+CM Diagram — Quality Resources.
USE IT IN PRACTICE
Turn the method into a document ready for real work.
Struckel Forms offers a free way to structure this methodology with guided fields, contextual help and print/PDF preparation. Use the tool to organize reasoning; use consulting when the challenge requires design, implementation, facilitation or executive follow-up.