Why continuous improvement often stalls before the first improvement
The APQC findings are about management practices, not a shortage of ideas
Organisations frequently encourage employees to make improvements but provide no dependable way to turn observations into work that can be tested, implemented and sustained. That weakness matters more than the number of ideas collected. A suggestion system can fill a database while the same delays, errors and handoffs persist, especially when no one owns the process that crosses departmental boundaries.
APQC’s 2026 Process & Performance Management Priorities & Challenges research offers a useful description of the problem. Its survey of 156 process and performance management professionals, conducted in November 2025, found that process management and continuous improvement remained leading areas of attention. In APQC’s accompanying analysis, 51% identified creating a continuous improvement culture as a priority, 46% cited establishing a systematic approach to finding improvement opportunities, and 34% cited aligning improvement work across the organisation. These are reported priorities from a professional survey, not measured rates of organisational failure or proof that one intervention works (APQC, 2026).
The pattern suggests a practical question: when an employee finds waste in a process, what happens next? If the answer depends on individual enthusiasm, an annual innovation campaign or the goodwill of a nearby manager, continuous improvement is vulnerable to competing priorities. A more reliable system gives the observation a route to investigation, decision, testing and control.
Why department-by-department improvement can make the whole process worse
APQC also reports that 31% of relevant respondents prioritised mapping end-to-end processes and 30% prioritised moving from a function-based culture towards process thinking. This is important because a department can improve its own productivity while transferring effort to colleagues or customers. A faster approval team might push incomplete requests downstream; a procurement team might reduce its internal handling time by passing more supplier exceptions to finance.
Before choosing an improvement, define the process boundary from the first meaningful trigger to the outcome experienced by the customer. Name the decision points, handoffs, rework loops and queues, and distinguish work time from waiting time. Then identify who has authority to change the full process. The resulting map does not need elaborate notation. It needs to reveal which parts of the operation jointly determine cost, quality, time, risk and customer experience.
Figure 1. Selected continuous improvement priorities, APQC 2026 survey.
Build a simple improvement pipeline that people actually use
Give every opportunity a problem statement and a decision
A practical improvement pipeline starts with a consistent intake rule. Each candidate should identify the affected process, the observable problem, whom it affects and at least one baseline measure. “Automate expense claims” is a proposed solution; “one in four claims requires clarification before approval” is a testable problem statement, provided the figure comes from actual records. This distinction prevents teams from investing in an attractive solution before understanding the cause of the problem.
The next decision is whether to investigate now, park for later, route to the correct process owner or close with a recorded explanation. Compare opportunities using expected customer or operational value, evidence strength, implementation effort, dependencies and risk. Simple categories are often enough. What matters is a transparent decision and feedback to the person who raised the issue. Without that response, the organisation teaches people that raising problems is a poor use of their time.
Use Kaizen to make small changes measurable and repeatable
Kaizen works best as a routine of observing a real process, challenging a specific difficulty, testing a workable change and learning from its result. Consider an administration team that receives incomplete applications. Instead of immediately buying software, it could record the most frequent missing fields, test a clearer intake checklist with one channel, compare resubmission rates and review whether the checklist creates new customer difficulties. The aim is not to prove the first idea correct; it is to learn which intervention improves the whole service.
The Institute for Healthcare Improvement’s Model for Improvement provides a useful structure even outside healthcare: agree on an aim, choose measures, select a change and use Plan–Do–Study–Act tests to learn on a limited scale before standardising. For a simple claims process, useful measures could include median elapsed time, first-pass completeness, exceptions per 100 claims and hours spent handling rework. The same baseline and definitions must be maintained long enough to distinguish genuine improvement from normal variation (IHI, n.d.).
Training matters at this point because employees need more than encouragement. They need to distinguish symptoms from causes, draw a process boundary, collect usable evidence, compare alternatives and explain whether the trial worked. STEP Bootcamp is designed to develop these practical process improvement and Kaizen capabilities through live learning, assignments and individual feedback. Professionals who want to practise a complete problem-to-measurement method can explore the STEP Bootcamp process improvement training programme.
Make improvement part of normal management
Decide who owns the change and what will be measured after launch
An implemented idea is not necessarily an improvement. Before rollout, an owner should specify the new method, who will use it, the expected effect, how compliance will be monitored and the conditions that would trigger a rethink. Performance measures should include quality and risk as well as speed: faster service is not better if errors rise, difficult cases are neglected or employees must quietly recover the work after the measurement ends.
A short regular review can keep the improvement pipeline honest. Teams can examine fresh problems, the age of undecided opportunities, test results, realised value and changes that have slipped back towards the old way of working. Managers should also check whether the reporting burden exceeds the benefit. An improvement system becomes counterproductive when preparing the evidence consumes more effort than the improvement itself.
Build capabilities across the organisation, not in one specialist function
The stronger long-term position is to give employees a common method while leaving decisions close to people who understand the work. Leaders still need to coordinate dependencies and prioritise resources, but ordinary process owners should be able to run credible small improvements. In that sense, continuous improvement culture is the consequence of repeated, supported behaviour, not a slogan that precedes it.
For employers who need an organisation-specific approach, STEP Corporate Training can be customised in duration, schedule, curriculum and delivery to develop practical improvement skills across teams. The useful question is not how many people attended training, but whether they can consistently identify, analyse, improve and measure a meaningful process afterwards.
Leave a Reply