What is it, and why use it?
A Critical-to-Quality Characteristic (CTQC) tree connects a customer need to drivers and measurable requirements. A driver describes what contributes to the need; an operational definition explains exactly how a requirement will be measured.
It turns vague requests such as “make it faster” into measures that two observers can apply consistently. It helps a team agree what success means before collecting data.
Explore the CTQC Builder features and local-file workflowWhen to use it
Use it when customer language is broad, teams disagree about a measure, or an improvement needs a clear acceptance requirement.
When another tool fits better
Use a SIPOC first if the process boundaries are unclear. Use a Data Collection Plan after the definition is agreed; a CTQC tree does not collect observations.
Before you start
- A specific customer or stakeholder and their own description of the need.
- A process boundary, candidate measurement source and agreed units.
- People who can test whether the definition is reproducible.
Use fictional or approved non-sensitive information. Do not include patient details or proprietary records in practice worksheets.
Step-by-step in CI Tools
Enter Customer / stakeholder and Voice of customer. Add a customer need that preserves the customer’s meaning.
Add drivers beneath the need. Select a driver and choose Add Operational Definition; several measures can belong to one driver.
Enter the metric, definition, unit, numerator and denominator where applicable. State inclusion/exclusion rules, source, frequency and ownership.
Use Visual Tree to inspect the relationships or Structured Table to review definitions. Test each definition on the same small set of fictional records with two observers.
Resolve disagreements before transferring reviewed copies to Data Collection or Control Plan. Save the editable worksheet to your computer.
Make an operational definition reproducible
Write the event being counted, eligible population, unit, observation method and timing. For a rate, define numerator and denominator separately. A formula describes arithmetic; it does not establish whether the underlying records are trustworthy. Test borderline cases and document the decision.
Completed worked examples
Demonstrations only: all organizations, observations, targets and results below are fictional. They are not clinical instructions or universal performance standards.
Healthcare operations — fictional
Outpatient reception timeliness
Starting information: A fictional clinic wants a predictable check-in. The customer says “I want to know when I will be ready.”
- Need: predictable arrival
- Driver: timely check-in
- Measure: queue wait in minutes
The definition below specifies how to measure the driver reproducibly.
| Need → driver | Predictable arrival experience → timely check-in |
|---|---|
| Metric | Minutes from joining reception queue to completed check-in |
| Rule / target | Include scheduled arrivals during staffed hours; flag waits above 10 minutes |
What the result means: The definition identifies both timestamps and the population. Ten minutes is a fictional locally chosen requirement, not a clinical or industry standard.
General business — fictional
Invoice response clarity
Starting information: A fictional supplier helpdesk wants reliable responses to invoice queries.
- Need: clear payment information
- Driver: useful response
- Measure: working hours to response
An acknowledgement alone does not satisfy this fictional definition.
| Need → driver | Clear payment information → timely first useful response |
|---|---|
| Metric | Working hours from receipt to a response that answers the question |
| Population | Invoice queries received on staffed weekdays; exclude duplicates |
What the result means: A receipt acknowledgement does not count as a useful response. The team must agree how a working hour is counted before comparing shifts.
Practise in a separate worksheet
Open the tool’s built-in synthetic sample as a new editable worksheet. It may differ from the worked demonstrations above. It never replaces an existing worksheet. Save any work you want to retain to your computer.
Open built-in practice worksheetYou’ll be asked to log in if needed. No worksheet is created just by reading this page.
Common mistakes and how to avoid them
- Writing “quick service” as a measurable definition: specify start, end and unit.
- Using a percentage without defining its denominator: name eligible cases and exclusions.
- Treating a target as a statistical control limit: customer requirements and process variation answer different questions.
Interpret the result
A complete-looking tree is a measurement hypothesis, not evidence that the process meets the need. Review missing fields and check whether independent observers agree. Retain the original customer wording alongside the measurable interpretation.
Record the assumptions and unanswered questions alongside the result. Use the relevant local review process before making operational decisions.
Credible further learning
These independent educational resources explain the methods. They do not endorse CI Tools Suite. Some external resources have their own access requirements.
- ASQ: Quality tools and templates (external resource)
- IHI: Quality Improvement Essentials Toolkit (external resource)
Resource links reviewed 29 October 2026. Our interface instructions and fictional examples are original CI Tools learning material.
Put the method into practice
Start a new worksheet, use the guide beside your work and keep an editable .citools copy on your computer.
Try This ToolChoose another tool