VoC → CTx Tree

Overview

The VoC → CTx tree translates unstructured customer statements into measurable requirements. Starting from the Voice of Customer (VoC), needs are identified, broken down into drivers, and finally converted into Critical-to-X requirements (CTQ, CTC, CTD) — measurable properties a process or product must fulfill.

Voice of Customer (VoC): Original customer statements — verbatim, unsorted, often emotional. Sources include interviews, complaints, surveys, returns. This level is not interpreted, only recorded.

Need: The expectation behind the statement — condensed and depersonalized. "I wait forever for my food" becomes "fast delivery". Several VoC statements can merge into one need.

Driver: Concrete properties of the process or product that address the need. "Fast delivery" becomes e.g. "processing time", "shipping time", "inventory availability".

Critical-to-X (CTQ, CTC, CTD): Measurable, specified requirements — usually Critical-to-Quality (CTQ), Critical-to-Cost (CTC), or Critical-to-Delivery (CTD). Example: "Delivery time ≤ 30 min in 95% of cases". With target, tolerance, and measurement method.

The tree connects the emotional customer world with the number-driven process world. Without this translation, VoC stays a mood snapshot; with it, it becomes a specification.

Approach

• Collect VoC statements — verbatim where possible, from multiple sources.
• Group statements and condense into needs.
• Derive drivers per need — what in the process determines the experience?
• Formulate one or more CTx requirements per driver — with measure, target, and tolerance.
• Validate with customers or stakeholders — do the CTx really capture what was meant?
• Prioritize — not every requirement matters equally. Kano model or weighting helps.

Pitfalls

Jumping to solutions: "Food arrives too late" instantly becomes "buy a new delivery service". First derive need and driver cleanly — the solution comes at the end, not the beginning.

VoC interpreted instead of quoted: Rephrasing statements loses the original tone. Stay verbatim at the VoC level — condensation belongs at the need level.

CTx without a measure: "Fast delivery" is not a CTx requirement but a wish. A true CTx has a number, a unit, and an acceptance criterion.

One source dominates: If only the loudest complaints are analyzed, the picture is biased. Also interview satisfied customers and sample across the whole customer base.

All needs weighted equally: Some requirements are basic (must be met), others are delighters (positively surprise). Without prioritization, effort spreads onto the unimportant.

No customer validation: The tree is a hypothesis until it has been mirrored back. Verify at least the most important CTx with customers or their representative (sales, support).

Examples

This module ships with the following example datasets — load any of them in the app with a single click.

Available in the following cycles

• DMAIC: Define
• DMADV: Define
• 8D: D2 — Describe the Problem