Process Performance Monitoring as the QMS Nervous System
Without process performance data, management operates on intuition. A manager observing that a production line is slower than usual is reacting to a visible symptom, not managing by fact. Process KPIs provide early warning of quality degradation long before customer complaints arrive. The link between process KPIs and quality objectives is direct: if your quality objective is zero customer complaints and your process KPI for inspection first-pass yield drops from 99% to 97%, you know a complaint is coming. Process monitoring is the mechanism by which data drives management decision-making.
Clause 9.1 Requirements for Process Monitoring
Clause 9.1 requires organizations to monitor and measure processes, determine conformity of products and services, ensure customer satisfaction, and monitor QMS performance and effectiveness. Organizations must determine what needs to be monitored, what methods to use, and when to analyze and evaluate results. The standard requires the results of monitoring and measurement to be analyzed and evaluated, and the results communicated to management review. Many organizations collect process data but never analyze it. Data without analysis is just recording; analysis without communication is knowledge kept secret. The complete requirement includes collection, analysis, and communication.
Designing Process KPIs
The right number of KPIs per process is three to five. More than five becomes overwhelming and dilutes focus. Each core process (Sales/Requirements Review, Design, Production, Service Delivery, Supplier Management, Customer Support, Internal Audit, Corrective Action) should have its own small set of KPIs that reflect the critical success factors for that process. Distinguish between leading and lagging indicators. A leading indicator (design first-pass acceptance rate) predicts future outcomes. A lagging indicator (customer complaint rate) reports on past performance. Use both: leading indicators allow intervention before problems; lagging indicators confirm that leading indicators are working. Always design KPIs that process owners can actually influence. A KPI that depends on external factors beyond the process owner's control creates frustration and disengagement.
Process KPI Examples by Sector
| Process | KPI | Target | Measurement Source | Frequency |
|---|---|---|---|---|
| Sales/Requirements Review | Requirements review completion rate | 100% before commitment | CRM / review log | Monthly |
| Design and Development | First-pass design acceptance rate | >90% | Design review records | Per project |
| Production | First-pass yield rate | >98% | Inspection records | Daily/Weekly |
| Service Delivery | On-time completion rate | >95% | Project management system | Monthly |
| Supplier Management | Incoming inspection rejection rate | <2% | Incoming inspection records | Monthly |
| Customer Support | Complaint resolution within SLA | >95% | CRM / helpdesk | Monthly |
| Internal Audit | Audit completion vs. schedule | 100% | Audit program | Quarterly |
| Corrective Action | CA closure within agreed timeframe | >90% | CA register | Monthly |
The Process Performance Dashboard
Bring all KPIs together in a single management view. Use traffic light (RAG: Red, Amber, Green) status to show at a glance which processes are performing. Show trend charts, not just point-in-time values. The dashboard should be the primary input to management review, not a supplementary report. When a KPI is Red, the dashboard should highlight that and ensure it is discussed at management review. A process performance dashboard that is created for audit purposes and then ignored between audits is overhead, not management.
| KEY IDEA | A process KPI that nobody checks is not a KPI — it is data collection overhead. Design KPIs that are reviewed at least monthly by the process owner and at least quarterly at management review. KPIs that do not drive decisions should be eliminated. |
Escalation When Targets Are Missed
Define an escalation protocol: Who is notified when a target is missed? By when? What investigation is triggered? What temporary controls are implemented while investigation is ongoing? The difference between a one-time miss and a trend deterioration matters: a single KPI miss might be random variation; a trend of misses signals a systemic issue. Escalation processes prevent KPI misses from becoming chronic performance degradation.
Connecting Process KPIs to Continual Improvement
Systematic analysis of KPI trends identifies improvement opportunities. A KPI that persistently underperforms despite corrective actions signals a systemic issue requiring process redesign. Presenting improvement investments to management review for approval ensures that continual improvement investments connect to data and are resourced appropriately. The improvement register should contain improvement initiatives derived from KPI analysis.
| IMPORTANT | Trend data is more valuable than point-in-time snapshots. A KPI at 97% this month tells you little. A KPI trending from 99% → 98% → 97% → 96% over four months tells you a process is degrading and intervention is required. Auditors look for trend analysis in management review records, not just current values. |
| BITLION INSIGHT | Indonesian organizations often start their QMS with too many KPIs — measuring everything that can be measured rather than what matters for quality outcomes. Start with three to five KPIs per core process, establish monitoring discipline, then expand. A small number of KPIs that are consistently monitored and acted upon delivers more quality improvement than a comprehensive dashboard that is reviewed twice a year. |