Quality performance indicators provide evidence about outcomes or conditions relevant to the organisation’s quality priorities. They are useful when they help someone recognise a meaningful change and decide what to do. A number displayed every month is not automatically a useful indicator, and a favourable trend does not explain its own cause.
The quality planning guide connects indicators with objectives and targets. This article focuses on selection and interpretation rather than a universal list of measures every QMS must report.
Begin with the management question
Identify the decision the evidence should support. An organisation may need to understand whether inputs are ready, whether released outputs meet criteria or whether capability is becoming less dependent on one individual.
Those questions need different evidence. A training completion count cannot establish every competence outcome, while an on-time delivery percentage cannot explain report usability or the effort needed to achieve the date.
The quality objectives examples show how intended results guide evidence selection. Avoid starting with available software fields and then inventing a reason that every field belongs on the quality dashboard.
Distinguish outcomes and influencing conditions
Outcome indicators describe what happened, such as accepted outputs, recurring problems or customer experience. Other indicators describe conditions believed to influence later outcomes, such as input readiness or available competent cover.
An early signal is useful when there is a credible mechanism and the relationship is examined. Do not label a measure predictive solely because it is collected before the output. A completed checklist can occur early without meaningfully reducing exposure.
Use the two views together. A stable outcome with deteriorating capability may require investigation before a visible failure. An improved activity count without a corresponding benefit may indicate that the selected activity is not influencing the intended mechanism.
Write a definition that survives a handover
Specify the unit counted, population, period, source and exclusions. For rates, explain numerator and denominator. Identify who maintains the measure and who interprets it.
A fictional consultancy measures assignments requiring essential clarification after acceptance. It defines acceptance and essential information so staff do not classify ordinary questions inconsistently. A case with several clarification messages may count once if the intended unit is the affected assignment.
Record limitations. Missing cases, late entry and changed source systems can distort the result. A precise percentage should not conceal uncertainty in the underlying records.
Balance performance and practical consequences
Use complementary evidence where a narrow target could distort behaviour. Reducing completion time may be valuable, but not if difficult cases are deferred or customers receive unsuitable outputs. Review quality, workload and relevant recipient experience together.
A small indicator set with clear purposes is often more useful than a comprehensive-looking pack nobody can interpret. Add a measure when it addresses an important gap in the decision, not merely because another organisation reports it.
The KPI examples guide provides defined sample measures and balancing questions. The examples should be adapted to the work rather than adopted as an automatic dashboard specification.
Interpret trends with context
A change in rate can reflect the process, work mix, reporting method or population. Explain material differences before comparing periods. Counts and rates can both be informative: counts show actual cases and workload, while rates help relate the cases to exposure.
A low number of complaints does not prove high satisfaction. Customers may have difficulty reporting, or the represented group may exclude important users. Likewise, more recorded defects can follow stronger detection rather than worse production.
Review relevant cases and alternative explanations. Correlation can suggest an enquiry, but it does not alone establish that a particular management action caused the observed movement.
Define the response to a signal
An indicator should have someone responsible for interpreting it and a route to a decision. A threshold may prompt investigation, while an important event can justify attention even before a numerical boundary is crossed.
| Definition element | Practical question |
|---|---|
| Purpose | Which decision does this evidence support? |
| Population | What work is represented or excluded? |
| Context | What changed besides the measured result? |
| Response | Who investigates or decides when it matters? |
Do not confuse an investigation trigger with proof that a process is unacceptable. Use the applicable requirements and supporting evidence for that conclusion.
Review whether the indicator remains useful
Ask users what changed because they saw the information. If the measure repeatedly stays favourable while operational problems persist, examine its scope, definition and relevance. If it prompts unnecessary alarm, reconsider interpretation and response rules.
Retire or revise a measure through an understandable decision. Preserve enough history to explain comparisons and earlier management choices. A revised definition should not silently rewrite previous performance.
An effective indicator supports honest judgement about the system. It helps people see results, uncertainty and practical constraints, with a clear connection to objectives and decisions rather than reporting activity for its own sake.
Keep a measure distinct from its visual presentation. A dashboard colour summarises a rule; it does not replace the underlying evidence or the judgement needed to understand an unusual case. Make the definition and supporting records accessible to the person expected to act.