CTQ Tree (Critical to Quality)
Turn vague customer needs into things you can measure. A CTQ tree breaks each broad need into its drivers and then into specific, measurable Critical-to-Quality requirements with targets, giving your project concrete goals to hit.
Build a CTQ Tree →What is a CTQ Tree?
A CTQ (Critical-to-Quality) tree is a structured diagram that translates broad, often vague customer needs into specific, measurable requirements. It works from left to right: a general need branches into the drivers that shape it, and each driver branches into measurable CTQ characteristics with targets.
The tree bridges the gap between what customers say and what a project can act on. A need such as fast service is not directly measurable, but breaking it down might yield drivers like short wait and quick resolution, which become measurable CTQs such as wait time under two minutes and first-contact resolution above ninety percent.
CTQ trees are a core Define-phase tool. They take the output of Voice of Customer work and convert it into the quantified requirements that the rest of the project will measure, analyze and improve against, ensuring the team targets what customers actually value.
In plain terms: Customers say things like 'I want it fast' or 'it should be reliable', which you can't measure directly. A CTQ tree breaks each of those down step by step until you reach hard numbers you can actually track, like 'delivered within 48 hours' or 'fails less than 1 in 1000 times'.
How It Branches
Need
The broad customer requirement, usually stated in the customer's own words, such as reliable or easy to use.
Drivers
The factors that shape whether the need is met. Each need branches into a few drivers that make it more concrete.
Measurable CTQs
Each driver branches into specific, measurable requirements with a target and unit, the quantities the project will track.
Key Formulas
What Makes a Good CTQ
A CTQ is only finished when it is measurable. If you cannot state how you would measure it and what target counts as success, the branch needs to go one level deeper. Vague CTQs cannot be tracked or improved.
Every CTQ should trace clearly back to a customer need. The tree structure makes this traceability visible, so anyone can see which requirement came from which need, which keeps the project anchored to real customer value rather than internal assumptions.
Assumptions & Validation
Valid Customer Needs
The starting needs come from genuine Voice of Customer input.
If violated: Gather VOC first; needs invented internally bias the tree.
Full Decomposition
Each need is broken down until the leaves are measurable.
If violated: Add another level for any CTQ that is not yet measurable.
Faithful Translation
CTQs preserve the intent of the original need.
If violated: Validate translated CTQs against what customers meant.
⚠️ Check assumptions first
A CTQ tree fails when the team stops decomposing too early, leaving CTQs that sound specific but cannot actually be measured, or when it substitutes internally convenient measures for what the customer meant. Keep branching until every leaf is a measurable characteristic with a target, and trace each one back to a real customer need so the requirements reflect customer value, not internal assumptions.
When NOT to Use CTQ Tree
Gathering Needs
To collect and organize raw customer input first, use Voice of Customer and affinity diagrams.
Prioritizing Requirements
To rank the resulting CTQs, use the Kano model or a prioritization matrix.
Deploying Requirements
To link CTQs to technical characteristics, use the House of Quality.
Industry Applications
Requirement Definition
Translate customer needs into measurable project requirements in the Define phase.
Metric Selection
Derive the specific metrics a project will baseline and improve.
Design Inputs
Provide measurable CTQs as inputs to a DMADV design project.
Service Standards
Turn service expectations into measurable service-level targets.
Frequently Asked Questions
What is a CTQ tree?
A CTQ tree is a structured diagram that translates broad customer needs into specific, measurable Critical-to-Quality requirements. It works from a general need, through the drivers that shape it, down to measurable characteristics with targets. Its purpose is to convert what customers say, which is often vague, into quantified requirements the project can actually measure, analyze and improve against.
What does CTQ stand for?
CTQ stands for Critical-to-Quality. A CTQ is a specific, measurable characteristic of a product or process that is important to the customer, such as delivery time, defect rate or response time. CTQs are the quantified expression of customer requirements, and defining them clearly is essential because they become the metrics the project targets throughout its phases.
How is a CTQ tree different from Voice of Customer analysis?
Voice of Customer analysis gathers and organizes raw customer needs, often in the customer's own words. A CTQ tree takes those needs and systematically breaks them down into measurable requirements. VOC is about collecting and understanding needs; the CTQ tree is about translating them into concrete, quantifiable targets. The two are sequential steps, with VOC feeding the CTQ tree.
How do I know when a CTQ is specific enough?
A CTQ is specific enough when it can be measured objectively and has a defined target. The test is whether two people using the same definition would record the same value. If a requirement cannot be measured, for example easy to use with no defined metric, the branch needs to be decomposed further until it yields a measurable characteristic such as number of steps to complete a task.
Why is traceability important in a CTQ tree?
Traceability means every measurable CTQ can be traced back to the customer need it came from. The tree structure makes this visible, which keeps the project anchored to genuine customer value. Without traceability, teams risk optimizing metrics that are convenient to measure but disconnected from what customers actually care about, which is a common way improvement projects lose their way.
How does a CTQ tree fit into a Six Sigma project?
The CTQ tree is a core Define-phase tool. It takes the customer needs identified through Voice of Customer work and converts them into the measurable requirements that the Measure phase will baseline and the rest of the project will improve. By producing quantified, traceable CTQs early, it ensures the whole project targets characteristics that matter to the customer.
Turn Customer Needs Into Measurable Targets
Break broad needs into specific, measurable CTQs. Free during Beta.
Build a CTQ Tree →