CTQ Tree Template
A root cause technique that drills from a problem to its underlying cause by asking Why five times.
What is a CTQ Tree Template?
A CTQ (Critical to Quality) Tree Template provides a structured visual framework for translating high-level customer needs into specific, measurable quality characteristics — creating a clear link between customer voice and process performance.
When to use a CTQ Tree Template
Use it in the Define phase after gathering Voice of the Customer data. The CTQ Tree feeds directly into your data collection plan and sets the performance standards you will measure in the Measure phase.
Who should use a CTQ Tree Template
- Green Belts and Black Belts — translating Voice of the Customer data into measurable project requirements in the Define phase
- Quality managers — establishing measurable quality standards from customer requirements for process design
- Product and service designers — linking customer needs to specific, testable design specifications
- Project sponsors — validating that the project's success metrics genuinely reflect what customers care about
How to use a CTQ Tree — step by step
-
1Write the problem statement at the top
Start with a clear, factual problem statement. 'Machine stopped' or 'Customer received wrong item' — specific, observable, factual. Vague problems produce vague root causes.
-
2Ask 'Why did this happen?' — Why 1
Write down the first-level cause. This is usually a symptom or a direct cause — not yet the root. Examples: 'Machine overheated', 'Wrong item was picked'.
-
3Ask 'Why did that happen?' — Why 2
Challenge the previous answer. Keep the team focused on causes, not blame. If the answer is 'human error', push further — why did the human make the error?
-
4Continue to Why 3, 4 and 5
Keep going until you reach a cause that is systemic — a missing process, a failed control, a gap in training or a design flaw. The number five is a guide, not a rule.
-
5Check the logic by reading upward
Read the chain back to front: 'Because of X, Y happened, which caused Z.' If the logic holds, you have a valid chain. If it breaks, revisit the step where it breaks.
-
6Identify the actionable root cause
The root cause is the deepest level where a corrective action can prevent recurrence. Document it clearly — this feeds your Improve phase solution design.
-
7Validate before acting
Do not jump to solution immediately. Check whether data or observation confirms the root cause is real and significant before committing resource to fixing it.
Worked example — NHS Outpatient Appointment CTQ Tree
A patient experience team translated 'I want a convenient appointment' into three quality drivers (accessibility, timing, communication) and six CTQs — including 'appointment offered within 10 working days of referral' and 'waiting time in clinic under 20 minutes'.
Common mistakes — and how to avoid them
Using internal language instead of customer language. CTQ names should reflect what the customer cares about, not internal process metrics. 'Customer waits less than 10 minutes' beats 'SLA compliance rate'.
Setting performance standards without customer data. Performance standards must be based on what customers actually require — not what the process currently achieves or what the team thinks is reasonable.
Creating too many CTQs. More than 5–6 CTQs dilutes project focus. If everything is critical, nothing is. Prioritise ruthlessly.
Not validating CTQs with customers. A CTQ tree built without customer validation is an assumption tree. Always check your CTQs with real customers before committing to them as project measures.
Tips for getting better results
Start with verbatim customer quotes. Direct customer quotes are more powerful starting material than team summaries. They reveal the emotional drivers behind the logical requirements.
Link each CTQ to a specific process step. A CTQ that can't be linked to a process step can't be improved. The linkage forces you to check that the CTQ is actionable.
Use the CTQ tree to challenge scope creep. If a proposed project deliverable doesn't connect to a customer CTQ, it is probably scope creep. The CTQ tree is your scope filter.
Advanced Toolkit Packs — available now
Structured, ready-to-use template packs designed for real improvement work. Pick the pack that matches your project and get started straight away.
Process Improvement Starter Pack
A starter pack for identifying improvement opportunities, measuring baselines and planning action.
Root Cause Analysis Toolkit
A practical RCA toolkit for defining problems, finding causes, validating evidence and creating action.
A3 Template Pack
A clean A3 problem-solving pack for concise, visual improvement thinking and follow-through.
