Continuous improvement is the ongoing, incremental improvement of processes and ways of working, driven mainly by the people who do the work. It is a standing habit rather than a project, and it assumes small compounding gains beat occasional large ones.
Why continuous improvement matters
Most organizations are better at launching change than at holding it. Deloitte’s 2026 Global Human Capital Trends found only 27% of leaders say their organization manages change effectively, while 85% call organizational adaptability critical and just 7% report leading well on continuous workforce growth.
The same gap shows up in technology. McKinsey’s State of AI report, published August 2026, found around 75% of high performers had fundamentally redesigned workflows against roughly 25% of everyone else, while only 37% of organizations attribute any EBIT impact to AI. The differentiator is process change, not tool adoption.
Gallup’s April 2026 research on AI adoption puts the same point from the employee side: about one in ten employees in AI-adopting organizations strongly agree AI has transformed how work gets done, while 65% say it improved their own productivity. Individual gains, unchanged processes.
The PDCA cycle
The core loop is plan, do, check, act. Its history is routinely misreported, so the accurate version is worth stating.
Walter Shewhart set out a three-step cycle of specification, production and inspection, and argued it should be bent into a circle, in Statistical Method from the Viewpoint of Quality Control (1939). W. Edwards Deming taught a version of it to Japanese engineers under JUSE in 1950, and Japanese practitioners condensed it into plan, do, check, act. Deming always called it the Shewhart cycle.
In The New Economics (1993) Deming replaced “check” with “study”, because check suggests verification rather than learning from a prediction. PDSA is his own correction, not a synonym.
Step
What it means
Where HR teams skip it
Plan
State the problem, the change and the predicted result
The prediction is left out, so nothing can be wrong
Do
Run the change small and contained
It launches organization-wide immediately
Study
Compare the result against the prediction
Replaced with a status update
Act
Standardise, adjust, or abandon
Nothing is ever abandoned
Kaizen, lean and Six Sigma
Kaizen (改善, change for the better) is the Japanese practice of continuous incremental improvement involving everyone. Masaaki Imai’s Kaizen: The Key to Japan’s Competitive Success (1986) is the work that brought the term into Western management. As practised inside the Toyota Production System, built by Taiichi Ohno, kaizen presupposes standardised work, since a process that is not stable cannot be improved, and it assumes the person doing the job is the person improving it. The Western time-boxed “kaizen event” is a later adaptation.
Lean comes from the same lineage. John Krafcik coined the term in Sloan Management Review in 1988, and Womack, Jones and Roos popularised it in The Machine That Changed the World (1990). Its five principles are value, value stream, flow, pull and perfection. The concept most transferable to HR is muri, overburden, which is what workload and burnout look like in lean terms.
Six Sigma was developed at Motorola in 1986 and scaled at General Electric from 1995. Its improvement cycle, DMAIC, is a descendant of PDCA with statistical rigour and a mandatory control phase. It suits transactional HR work such as payroll error rates and case resolution, and fits poorly to judgment-heavy work such as succession planning.
Continuous improvement vs transformation
Continuous improvement
Transformation
Change size
Many small compounding gains
Few large discontinuities
Who drives it
The people doing the work
Leadership and specialists
Cost and risk
Low, failures are cheap and local
High, failures are expensive and visible
Basis
An existing standardised process
Redesign or replacement
Failure mode
Plateau, or optimising a process that should not exist
Change fatigue and unrealised benefits
The two are complements. Transformation resets the level of performance, and continuous improvement is what holds the gain and prevents the reversion that follows most large programmes. See change management.
What makes it work
Standardise before you improve. Without a documented current state there is no baseline and no way to tell whether a change helped.
Give the improvement to the people doing the job. This is the part most programmes replace with a central team, and it is the part that produces the ideas.
Make error reporting safe. Amy Edmondson’s work on psychological safety (Administrative Science Quarterly, 1999) established the link, and the effect is measurable at scale. The 2025 NHS Staff Survey, published March 2026 from 766,285 responses, found only 59.3% of staff agree their organization treats people involved in an error fairly, and 67.3% agree action is taken to stop reported errors recurring.
Close the loop visibly. SHRM’s 2026 State of the Workplace, January 2026, found job satisfaction at 91% where workers see their organization effectively addressing workplace needs against 44% where they do not.
Adapt the plan as you go. Gartner’s March 2026 change management research found organizations that continuously adapt change plans based on employee feedback are four times more likely to achieve change success.
Cap the number of live improvements. Ten changes at once is a reorganization, not a kaizen cycle.
Measure the process, not the programme. Count cycle time, defect rate and rework, not workshops run.
How Engagedly helps
Continuous improvement needs a place where changes, owners and results are visible. Engagedly’s Performance Suite tracks improvement work as goals with check-ins, so a process change has a named owner, a stated target and a review date rather than living in meeting notes.
Engage & Listen adds the feedback side, which is where improvement ideas and early warnings come from. Pulse results segment by team, so you can see whether the people closest to a process think it got better.
Continuous improvement is the ongoing practice of making small, incremental improvements to how work is done, driven mainly by the people doing that work. It runs as a standing habit rather than a project, on the principle that compounding small gains beat occasional large ones.
What is the PDCA cycle?
PDCA stands for plan, do, check, act: state the change and predict its result, run it small, compare the result against the prediction, then standardise, adjust or abandon. It derives from Walter Shewhart’s cycle and was taught in Japan by W. Edwards Deming, who later revised check to study.
What is the difference between kaizen and continuous improvement?
Kaizen is the Japanese term and practice from which the Western concept of continuous improvement derives. In its original form inside the Toyota Production System it assumes standardised work and improvement by the person doing the job, which is stricter than how continuous improvement is often applied.
How is continuous improvement different from transformation?
Continuous improvement makes many small, low-risk changes to an existing process. Transformation makes a few large discontinuous changes that redesign or replace it. Transformation resets the performance level; continuous improvement holds and extends the gain afterwards.
Performance
