Using Quality Tools and KPIs to Build Improvement Capability
A rework total can tell a manager that a process needs attention without explaining what to change. Quality tools help investigate that question; a KPI tracks performance against an objective and supports decisions. Learning how they work together makes improvement discussions more useful than choosing a chart simply because it looks persuasive.
The 7 QC Tools teaches methods for collecting and analysing process data, including check sheets, Pareto charts and control charts. KPIs, Objectives & Management Review focuses on defining measures, interpreting performance and turning review into decisions. Choose according to whether your next task is investigating a process, directing its performance or connecting both activities.
Use a check sheet to collect comparable observations
Imagine a hypothetical support team investigating tickets that require rework. One adviser counts every reopened ticket, another counts only repeat work on the original issue, and another counts requests needing extra approval. Combining those totals would conceal differences in the underlying definition.
A check sheet provides a structured way to record observations as they occur. For this exercise, the team agrees what qualifies as rework and records a ticket reference, category, date and relevant context. Categories might distinguish an incomplete initial answer, an incorrect action and missing information at handover. The sheet is a data-collection tool; it is not simply a checklist confirming that routine tasks were done.
Test the definitions against a few fictional ambiguous cases before collecting more data. Agree how to handle multiple problems on one ticket and how to avoid counting the same event twice. Otherwise, apparent changes in performance may reflect different counting habits rather than a different process.
Use a Pareto chart to decide where to investigate
A Pareto chart ranks categories by their contribution, making the largest recorded categories easier to see. Suppose incomplete initial answers account for the most rework tickets in the fictional data. That gives the team a starting point for investigation. It does not establish that employees lack knowledge or that a training course is necessarily the answer.
The team might examine whether the approved answer guide is unclear, information is unavailable or a new product creates unfamiliar questions. The chart prioritises attention; further evidence is needed to explain the cause. A rare but serious error may also deserve action even when its bar is small, so frequency should not become the only decision criterion.
Keep the basis of comparison visible. A busy shift can record more errors while having a lower error rate. Different product mixes can also distort a simple comparison. Check denominators and conditions before treating a category or team as the source of the problem.
Use a control chart to examine variation over time
A control chart retains the order of observations and uses statistically determined limits to help distinguish ordinary process variation from signals that deserve investigation. It answers a different question from the Pareto chart: does the process appear stable over time? The NIST explanation of control charts describes this monitoring purpose.
For the rework exercise, a suitable chart could examine the proportion of qualifying tickets requiring rework over successive periods. The analyst must choose a chart and sampling approach appropriate to the data, including changes in ticket volume. Adding arbitrary red and green lines to a time plot does not create a valid control chart.
Control limits describe process behaviour; they are not management targets or customer specifications. A stable process may still deliver too much rework. Conversely, a point below the target does not establish sustained improvement. NIST distinguishes control and specification limits; keeping them separate helps reviewers avoid confusing predictability with acceptable performance.
Define a KPI that supports a management decision
The team's KPI might be the percentage of qualifying tickets closed in a given month that reopen for the same issue within an agreed observation window. Define the numerator, denominator, exclusions, data source and reporting delay. The team must allow that window to close before comparing completed cohorts fairly.
The objective could be to reduce avoidable repeat work while maintaining satisfactory resolution. Management then reviews the KPI alongside the investigation. If unclear handover information is supported as a cause, it might approve a revised handover process, assign an owner and agree how to check the result. The KPI tracks the outcome; the quality tools help explain where to intervene and whether the resulting pattern is convincing.
Watch the incentives. Rewarding low reopening rates alone could encourage staff to discourage customers from reopening unresolved tickets. Include the service outcome in the discussion and make definition changes visible. A better-looking number is not enough if the customer's problem remains.
Choose learning for the contribution you need to make
An analyst preparing a rework investigation needs to justify collection rules, tool choice and interpretation. A process owner preparing management review needs to connect evidence with a decision, resources, ownership and follow-up. Course completion supports this development but does not certify the organisation or establish competence for every analytical assignment.
See the quality and improvement training hub for related learning, or discuss training for your improvement team. Enrol in The 7 QC Tools to learn how to collect, prioritise and interpret process data, or choose KPIs, Objectives & Management Review to turn defined measures into accountable management action.