What Is Continuous Improvement? The Process, PDCA, Methods and Examples (2026)

Continuous improvement (CI) is the habit of making work better in many small, tested steps, carried out mostly by the people who do that work, instead of waiting for a rare big project. The continuous improvement process is the loop that keeps it going: spot a problem, try a change on a small scale, check what happened, and make the change the new standard if it worked. That loop is the PDCA cycle (Plan, Do, Check, Act).

Kaizen is the Japanese word most people use for the same idea, KVP (kontinuierlicher Verbesserungsprozess) the German one, and ISO 9001 clause 10.3 requires every certified quality management system to improve continually.

What does continuous improvement mean?

Three things separate it from ordinary firefighting.

• The steps are small. A tool moved closer to where it is used, a clearer label, one field removed from a form. Each change is cheap to try and cheap to undo.
• The people doing the work lead it. Masaaki Imai, who took kaizen to a Western audience, defined it as improvement that never stops and involves everyone, managers and workers alike (Kaizen Institute). The Lean Enterprise Institute calls improvement led by specialist engineers, far from daily operations, a failure mode.
• It never finishes. Every change that works becomes the new standard, and the standard is the starting point for the next change.

The raw material is the improvement idea: someone on the line, in the warehouse or at the counter noticing that something could work better.

Where does continuous improvement come from?

Many pages say Deming brought kaizen to Japan and invented PDCA. The documented history is different, and Deming himself rejected the name PDCA.

Year	What happened
1939	Walter Shewhart draws specification, production and inspection as a loop instead of a line. His book is edited by W. Edwards Deming.
1950	Deming teaches an eight-day seminar on statistical quality control for JUSE, the Japanese Union of Scientists and Engineers. His design, make, sell, redesign loop becomes the “Deming wheel”.
1951	Japanese executives recast the wheel as Plan, Do, Check, Act. The Lean Enterprise Institute credits JUSE.
May 1951	Toyota’s Creative Idea Suggestion System starts, modelled on Ford’s suggestion system after a Toyota director trained at Ford.
1985	Masaaki Imai founds the Kaizen Institute.
1986	Imai’s book Kaizen: The Key to Japan’s Competitive Success takes the word global. Deming presents his own version of the cycle in Out of the Crisis.
1990	Deming writes to Ronald Moen: “be sure to call it PDSA, not the corruption PDCA”.
1993	Deming’s final version, the PDSA cycle (Plan, Do, Study, Act), appears in The New Economics.
2015	ISO 9001:2015 clause 10.3 requires certified organisations to continually improve their quality management system.

Sources: Ronald Moen, Foundation and History of the PDSA Cycle; 75 Years of Toyota; Kaizen Institute; Lean Enterprise Institute, PDCA.

Two corrections follow. Kaizen is not Deming’s invention: it is the Japanese word for improvement, and Toyota’s best-known channel for employee ideas was modelled on Ford’s. And PDCA is not the version Deming taught. He preferred “study”, warning audiences, Moen records, that the English word “check” can mean to hold back. On the shop floor, both run the same way.

How does the continuous improvement process work?

Almost every CI programme runs on the PDCA cycle, whatever it calls it.

Step	The question	What comes out	The usual mistake
Plan	What is the problem, what causes it, what will we try?	A problem statement, a likely cause, one change to test, a measure	Fixing before anyone has watched the problem happen
Do	Does the change work on a small scale?	A trial on one line, shift or team for a fixed period	Rolling out everywhere, so nothing can be compared
Check	What happened compared with before, and why?	Before-and-after data, and what the team learned	Skipping it because the change feels better
Act	Keep, adjust or drop?	An updated standard, or a new Plan	Never writing the change into the standard, so it fades

A worked example. A packaging line stops whenever a label roll runs out, because someone has to walk to the store for a new one.

• Plan: the stop log records it as “label change”. The hypothesis: nobody can see a roll is about to run out, and spares are too far away. The change: two spare rolls in a marked spot at the line, and a coloured mark near the end of each roll that means “call for a refill”.
• Do: one line, one shift, two weeks.
• Check: compare label-change stops with the two weeks before, and ask the operators what got in the way.
• Act: if the stops fell, the spare-roll spot goes into the standard work and the other lines copy it. If not, back to Plan.

No consultant, budget or steering committee needed. That is what makes it continuous improvement.

How is continuous improvement different from kaizen, lean, Six Sigma and a suggestion scheme?

They overlap, and the borders are argued over. This is the common usage:

Term	What it is	Who drives it	Typical form
Continuous improvement	The umbrella: any organised habit of improving in small, repeated steps	Everyone, with managers making time for it	PDCA, improvement boards, huddles
Kaizen	The Japanese name and philosophy behind CI; in the West also a workshop format	Teams at the workplace, led by frontline managers and operators	Daily kaizen, kaizen events
Lean	A management system built on Toyota’s methods: flow, pull, removing waste	Line managers, coached by lean specialists	Value stream maps, 5S, standard work
Six Sigma	A project method for reducing variation with statistics	Trained specialists on selected projects	DMAIC: define, measure, analyse, improve, control
Suggestion scheme	A standing channel, with rules and often rewards, for any employee’s proposals	Individual employees; assessors decide	Forms, deadlines, rewards
Idea management	Collecting, deciding on and following up ideas across teams and sites, usually in software	A programme owner and line managers	Idea challenges, triage, tracking

Kaizen has its own guide: what kaizen is and how it works. For the suggestion channel, see the employee suggestion scheme guide; for the wider process, what idea management is.

How is continuous improvement different from innovation?

ISO 9001 draws the line itself: the note to clause 10.1 lists continual improvement as one kind of improvement, next to correction, corrective action, breakthrough change, innovation and re-organisation. Lean has a word for the big jump, kaikaku: radical improvement, in contrast to step-by-step kaizen.

A practical test: if the team that proposed a change can trial it on its own budget within weeks, it is continuous improvement. If it needs a business case, a project team or a decision above the site, it is innovation or a capital project, and needs a different route. Both arrive through the same channel, so the skill is routing, which the guide to prioritising ideas covers. The four types of innovation covers the bigger end.

Which continuous improvement methods and tools are there?

According to Moen, PDCA and the seven basic quality tools (check sheet, histogram, Pareto chart, fishbone diagram, graphs, scatter diagram, stratification) became the foundation of kaizen in Japan. Most programmes today use a mix of these:

Method	What it does	Use it when
PDCA / PDSA	The loop for testing any change	Always; the other tools sit inside it
5 Whys	Asks “why” until you reach a cause you can act on	The symptom is obvious, the cause is not
Ishikawa (fishbone)	Sorts possible causes: people, machine, method, material	The team disagrees about the cause
Pareto chart	Ranks problems by frequency or cost	You have more problems than time
5S	Sort, set in order, shine, standardise, sustain	Time goes on searching for tools and parts
Gemba walk	Leaders go where the work happens to see and ask	Managers know the process mainly from reports
Improvement board	Problems, owners and due dates, reviewed weekly	A team needs a rhythm for its own improvements
A3 / 8D	One-page problem solving (A3), or eight steps for complaints and recurring defects (8D)	A problem crosses teams, or a customer wants a formal answer
Kaizen event	A cross-functional team redesigns one process, commonly over five days	A process needs rework, not a tweak
Quality circle	A small group from one area meets regularly on its own problems	You want improvement as a standing team habit

The gemba walk checklist has the questions and a follow-up template.

What are examples of continuous improvement?

None of these is dramatic. That is the point.

• Production: tools and material for the next product are staged beside the machine before the current run ends, so changeovers start on time.
• Quality: after repeated rework on mirrored parts, a guide pin on the fixture makes the part fit only one way round.
• Maintenance: a picture card for a two-minute daily check of oil levels and leaks catches problems at shift start, not at breakdown.
• Safety: a pallet stack that forced forklifts and pedestrians into one aisle is moved, and the walkway repainted.
• Logistics: the fastest-moving items are re-slotted nearest to dispatch, based on last quarter’s pick lists.
• Energy: a monthly leak-tag round on the compressed air system.
• Office: the purchase request form is cut to the fields purchasing actually reads.

For thirty more, see process improvement ideas and cost-saving ideas for manufacturing.

What does ISO 9001 require for continual improvement?

Clause 10.3 of ISO 9001:2015 says the organisation must continually improve how suitable, adequate and effective its quality management system is, using the results of analysis and evaluation and the outputs of management review to decide where. The standard is built around PDCA, but clause 10.3 names no method: kaizen, an improvement board or a suggestion scheme can all provide the evidence. In practice, be able to show a trail: what the data and the management review said, which improvements you chose, and what happened.

Continual or continuous? ISO says “continual”. ISO 9000:2015 defines continual improvement as a recurring activity to enhance performance: repeated steps with pauses to check and standardise, not an unbroken flow. In everyday use the words mean the same, and “continuous improvement” is far more common.

Who does continuous improvement?

Everyone, but not in the same way.

• Operators and team members spot problems, suggest changes and run most trials.
• Team leaders run the weekly board, protect time for trials and answer every idea.
• A CI coordinator or facilitator coaches methods, runs kaizen events and keeps the records.
• Managers remove obstacles, fund what is too big for a team, and go to the gemba themselves.

In Germany the works council has co-determination rights over the principles of suggestion schemes and of self-directed group work, and over technology that can monitor performance (section 87(1) nos. 12, 13 and 6 of the Works Constitution Act), so CI there is often governed by a works agreement. The employee-driven continuous improvement playbook covers the people side in depth, and getting frontline workers to share ideas covers teams without a desk.

How do you start a continuous improvement process?

Start smaller than feels right.

1. Pick one area and one problem people there already complain about.
2. Agree the rhythm: where problems get written down, who looks at them, how often. A fifteen-minute weekly board review is enough.
3. Promise a response time and keep it. An idea that gets no answer is the last one that person sends.
4. Run the first loops on small, visible problems, and write every result that works into the standard.
5. Show the results where the team works, then widen to the next team or site.

The playbook above includes a 90-day pilot plan, and The Idea Program Toolkit has templates for each stage.

Why do continuous improvement programmes stall?

The Lean Enterprise Institute lists the usual failure modes: counting kaizen events instead of results in safety, quality, delivery and cost; gains lost as people drift back to the old way; frontline workers left out; and specialists leading instead of the people doing the work. The other classic is silence: ideas go in and nothing comes back. Our guide on why continuous improvement programmes stop working covers the four places ideas stall and a 90-day reset.

How do you know continuous improvement is working?

Track a few numbers monthly against your own previous quarter, not another company’s benchmark:

• Participation: the share of people who raised at least one idea in the last twelve months.
• Time to first response: days until the person who raised an idea hears what happens next.
• Implementation rate: the share of accepted ideas actually implemented.
• Time to implement: days from acceptance to the new standard.
• Results: the safety, quality, delivery or cost measure each change was meant to move.

The first two predict the programme’s future; the last one pays for it. How to measure an idea programme has definitions and a reporting template.

Do you need software for continuous improvement?

Not to start. One team with a whiteboard can run CI well, and a spreadsheet is fine for a single site. Software earns its place when improvement crosses shifts, teams or sites: ideas get lost between the night shift and the morning meeting, two plants solve the same problem twice, or an auditor wants the record.

Then you need something operators can use from a phone, that gives every idea an owner and keeps the record of what was implemented. Hives is one option built for this (how it works for continuous improvement). For a neutral look at the options, read continuous improvement software for manufacturing, and if your kaizen still runs on paper, how to digitise your kaizen process.

Frequently asked questions

What is continuous improvement in simple terms?

Getting a little better at your work every week, in small steps you test before you keep. The people who do the work find the problem, try a change, check whether it helped, and make it standard if it did.

Is continuous improvement the same as kaizen?

Nearly. Kaizen is the Japanese word and the philosophy that made the idea famous; continuous improvement is the usual English term. In Western companies “kaizen” also names a format, the multi-day kaizen event. The guide to kaizen covers the differences.

How many steps does the continuous improvement process have?

PDCA has four: Plan, Do, Check, Act. Five- and seven-step models are the same loop cut finer, usually by splitting Plan into defining, measuring and analysing the problem. Six Sigma’s DMAIC is the best-known five-step version.

What are the principles of continuous improvement?

There is no official list. Most sources share five: improve in small steps, involve the people who do the work, go and see the problem where it happens, test before you keep, and make every gain the new standard.

What does a continuous improvement manager do?

They run the programme rather than making the improvements: coaching teams in PDCA and 5 Whys, facilitating kaizen events, keeping ideas moving and reporting results. In German companies the roles are often called KVP-Koordinator and KVP-Moderator.