CTQ Tree Alignment Calculator
Test whether your Critical to Quality tree actually holds together. Enter the customer need, the drivers beneath it and the CTQ requirements under each driver. The calculator scores alignment at every level, checks each CTQ is measurable and shows you which branch to fix.
🎯 What this calculator does
A CTQ tree breaks a broad customer need into drivers, then breaks each driver into measurable requirements. Most teams draw the tree and move on. Nobody checks whether the branches actually connect. This calculator does that check for you.
You enter the customer need, the drivers that sit under it and the CTQ requirements that sit under each driver. The tool scores two things. First, how strongly each driver supports the customer need. Second, how well each CTQ measures its own driver. It then tests whether each CTQ is genuinely measurable, because a requirement without a number and a target is an opinion.
The output is a single tree score out of 100, a rating band and a list of the exact branches that need rework. You are not guessing which part of the tree is weak. You are told.
📐 How each component is scored
Structure (20 points). Rewards 3 to 5 drivers and at least 2 CTQ requirements under each driver. Too few drivers means the need is not decomposed. Too many means you have built a wish list.
Driver alignment (30 points). Compares the wording and the underlying concept of each driver against the customer need. Shared terms score. Shared concept families such as speed, cost, accuracy, safety or availability also score.
CTQ alignment (25 points). Same comparison, run between each CTQ requirement and its parent driver.
Measurability (25 points). Each CTQ earns points for containing a number, a comparison operator such as at least or no more than, and a unit such as hours, percent, ppm or millimetres. Vague wording without a number loses points.
📋 How to use it
- Open the Calculator tab and load a sample dataset if you want to see the scoring in action first.
- Write the customer need in the words the customer used. Keep it to a short phrase such as "Fast and reliable delivery".
- Add 3 to 5 drivers. Each driver answers one question. What has to be true for this need to be met?
- Add 2 or 3 CTQ requirements under each driver. Each one answers a different question. How will we measure this driver?
- Write every CTQ with a number, an operator and a unit. "Order picked and packed within 4 hours" scores. "Faster picking" does not.
- Click Analyse CTQ tree. The tool switches to the Results tab and scrolls you to the top.
- Read the branch table. Rework anything rated Fair or Weak, then run it again.
- Download the Excel report and attach it to your project charter as evidence the tree was validated.
📊 Rating bands
| Tree score | Band | What it means | What to do next |
|---|---|---|---|
| 80 to 100 | Strong | Drivers track the need, CTQs measure their drivers and every requirement carries a number. | Lock the tree. Move to baseline data collection. |
| 65 to 79 | Solid | The logic works. One or two branches are loose or one CTQ is soft. | Fix the flagged branches, then proceed. |
| 50 to 64 | Fair | Real gaps. Some drivers do not track the need, or several CTQs cannot be measured. | Rework before you collect any data. |
| Below 50 | Weak | The tree does not decompose the need. Measuring it would waste the project. | Go back to the Voice of Customer data and rebuild. |
✅ Aligned against ❌ misaligned
✅ Aligned driver
Need: Fast and reliable delivery. Driver: Order processing speed. Processing speed sits directly inside delivery speed, so the branch carries weight.
❌ Misaligned driver
Need: Fast and reliable delivery. Driver: Employee engagement. Engaged staff may help, but the link is indirect and unmeasurable at this level.
✅ Aligned CTQ
Driver: Product durability. CTQ: Mean time to failure at least 10000 hours. Time to failure is the definition of durability, and it carries a number.
❌ Misaligned CTQ
Driver: Product durability. CTQ: Customer satisfaction score at least 4.0. Satisfaction is downstream of durability, so it measures the wrong thing.
⚠️ Common mistakes
- Writing the customer need in internal language. "Improve fulfilment KPIs" is not a customer need. "Get my order in two days" is.
- Using solutions as drivers. "New warehouse software" is a solution. "Pick accuracy" is a driver.
- Repeating the same driver twice with different words. The calculator flags drivers that overlap heavily.
- Writing CTQs without a target. "Reduce cycle time" gives the team nothing to hit.
- Jumping two levels at once, so the CTQ measures the customer need instead of the driver above it.
💡 Pro tips
- Read each branch aloud as a sentence. "Fast delivery is achieved by order processing speed, which is measured by processing time under 2 hours." If it does not read cleanly, the branch is broken.
- Cap the tree at 5 drivers. A tree with 9 drivers is a project that never closes.
- Every CTQ needs three parts. A metric, an operator and a target. Check for all three before you run the analysis.
- Pull driver wording from the Voice of Customer verbatims. Customer language keeps alignment high naturally.
- Ask the process owner to sign off the tree before baseline data collection starts. Rework after data collection costs weeks.
- Rerun the calculator after every rewrite. The score movement tells you whether the edit helped.
🧭 Where this fits in DMAIC
The CTQ tree belongs in the Define phase. You build it after the Voice of Customer work and before the project charter is signed. It converts customer language into the measurable requirements that the Measure phase will baseline and the Control phase will monitor.
Run this calculator as the last step of Define. The Excel export gives you a dated record that the tree was validated, which is useful at tollgate reviews.
🧮 Build your CTQ tree
Load a sample dataset to see how the scoring behaves, then replace it with your own tree.
🎯 Customer need
📈 CTQ tree analysis
Build your tree in the Calculator tab to see results here
Nothing to analyse yet
Open the Calculator tab, load a sample dataset or enter your own customer need, drivers and CTQ requirements, then click Analyse CTQ tree.
What is a CTQ tree?
A Critical to Quality tree is a Define phase tool that turns a broad customer need into requirements you can measure. It has three levels. The customer need sits at the top. Drivers sit beneath it and describe what has to be true for the need to be met. CTQ requirements sit under each driver and state the metric, the operator and the target.
The tree matters because customers speak in outcomes and processes run on numbers. A customer says they want quick service. A process needs a target such as first response within 15 minutes. The tree is the bridge between the two.
Why alignment beats completeness
A full tree with weak logic is worse than a small tree with tight logic. If a driver does not track the customer need, every hour spent measuring it is wasted. If a CTQ does not measure its driver, the improvement will show on a chart and never reach the customer.
This calculator scores those two links separately so you can see exactly where the logic drops. A tree can score well on driver alignment and badly on CTQ alignment, which tells you the decomposition is right but the measures are wrong.
What makes a CTQ requirement measurable
Three parts. A metric that names what you are counting. An operator such as at least, no more than, within or plus or minus. A target with a unit. "Dimensional tolerance within plus or minus 0.1 mm" has all three. "Better tolerances" has none of them.
The calculator tests every requirement for these parts and reports a measurability percentage. Anything under 50 percent needs rewriting before you baseline it.
Frequently asked questions
How many drivers should a CTQ tree have?
Three to five works best. Fewer than three usually means the customer need has not been broken down. More than five spreads the project too thin and makes the charter hard to close.
What is the difference between a driver and a CTQ?
A driver names what has to be true, such as pick accuracy. A CTQ states how you will measure it, such as pick accuracy at or above 99.5 percent. Drivers are qualitative. CTQs carry numbers.
Can a CTQ tree have more than three levels?
Yes, complex needs sometimes need a fourth level. This calculator scores the standard three level tree, so for deeper trees run each sub branch as its own analysis with the sub driver set as the customer need.
How does the calculator score alignment?
It compares shared wording between levels and also compares the underlying concept family, such as speed, cost, accuracy, safety or availability. Two phrases with no shared words can still score highly if they describe the same concept.
What score should I aim for before starting the Measure phase?
Aim for 80 or above. Anything at 65 to 79 is workable once you fix the flagged branches. Below 65, rework the tree before you spend money on data collection.
Can I export the results?
Yes. The calculator generates a branded four sheet Excel workbook with a summary, your tree inputs, the branch by branch analysis and the recommended actions.
