What Is Kaizen? Meaning, Principles, Examples and How to Apply It
What kaizen means, the principles behind it, kaizen events and focused improvement, a step-by-step way to run one with PDCA, examples from a factory, an office and customer service, and the mistakes that stop it working.
Find the root causes in your own feedback, free
Share an export of your tickets, reviews or survey comments. We send back the top root causes within 48 hours on business days. No sales call.
Quick answer
Kaizen is a Japanese word that means improvement, or change for the better. In business it means continuous improvement: many small, steady changes made by the people who do the work, tested with data and then made the new standard. A kaizen cycle usually follows PDCA: plan a small change, do it, check the result, act by standardising it or trying again.
Most improvement programmes fail in the same way. A big project starts with energy, delivers a report and a few changes, and six months later the old problems are back. Kaizen takes the opposite route: instead of one large leap, it makes improvement a daily habit, in small steps, owned by the people closest to the work.
This guide explains what kaizen means, the principles behind it, the main types (daily kaizen, kaizen events and focused improvement), a simple way to run a kaizen with PDCA, three worked examples and the mistakes that quietly kill it. The examples are illustrative.
What does kaizen mean?
Kaizen combines two Japanese words: kai, change, and zen, good. Together they mean improvement, or change for the better. In everyday Japanese it is an ordinary word; in management it came to mean a philosophy of continuous improvement.
The idea is closely associated with the Toyota Production System, where operators are expected to improve their own work, and it was popularised outside Japan by Masaaki Imai's 1986 book Kaizen: The Key to Japan's Competitive Success. Today kaizen is part of lean management and is used well beyond factories: in hospitals, banks, software teams, call centres and customer service.
Three things make kaizen different from a normal improvement project:
- Small steps, not big leaps. A change that takes a day and costs little is tried now, instead of waiting for a budget.
- Everyone takes part. The people doing the work suggest and test changes, not only managers or consultants.
- It never ends. Each improvement becomes the new standard, and the next improvement starts from there.
The principles of kaizen
You will find many lists of kaizen principles. The ones that matter in practice:
- Go to the gemba. Gemba means "the real place": the line, the counter, the call queue, the checkout page. Problems are understood where work happens, not in a meeting room.
- Start from facts and data. Measure the problem before changing anything, so you can tell whether the change helped.
- Find the root cause. Fix why the problem happens, not only what it looks like. Tools such as 5 Whys and the fishbone diagram help here.
- Remove waste. Lean thinking names three enemies: muda (waste, such as waiting, rework and unnecessary movement), mura (unevenness) and muri (overburden).
- Standardise what works. A good change that is not written into the standard disappears when people change shifts.
- Respect people. Kaizen asks people for ideas and gives them time to test them. Blame kills suggestions.
- Think from the customer. Improvement is measured by what the next process, or the end customer, experiences.
Types of kaizen
- Daily kaizen. Small improvements made as part of normal work, often collected through a suggestion system or a short daily meeting at the board.
- Kaizen event (kaizen blitz). A short, focused workshop, often a few days long, where a cross-functional team improves one process: they observe it, measure it, change it and standardise the result.
- Focused improvement (kobetsu kaizen). One of the pillars of Total Productive Maintenance (TPM): a small team attacks a specific, chronic loss, such as a machine with frequent stops or long changeovers, using structured problem-solving.
- Kaizen vs kaikaku. Kaikaku means radical change, such as redesigning a whole line. Most organisations need both: kaikaku occasionally, kaizen every day.
How to run a kaizen, step by step
Kaizen follows the PDCA cycle (plan, do, check, act). A practical version:
- Pick one problem. Choose something the team sees every day and that matters to customers or costs: rework, waiting, a recurring complaint. A Pareto chart helps you pick the few problems that cause most of the pain.
- Go and see, then measure. Watch the process where it happens and record a baseline: time, errors, complaints, whatever describes the problem.
- Find the root cause. Ask why until you reach a cause you can act on, and check it against the data.
- Plan a small change. Prefer changes you can try this week, cheaply, and undo if they do not help.
- Do: test it. Try the change on one line, one shift or one team first.
- Check the result. Compare with the baseline. Did the problem shrink? Did anything else get worse?
- Act: standardise or try again. If it worked, update the work instruction, checklist or system setting and share it with similar teams. If not, go back to the root cause.
The free PDCA template walks a team through these steps with a filled-in example, and the lessons learned template helps record what you learned for the next cycle.
Kaizen examples
Kaizen in a factory
A packaging line loses time every time it switches to a different product. The team films a changeover and sees that operators spend much of it walking to fetch tools and the next batch of materials. Small changes follow: a tool board next to the machine, materials prepared while the line is still running, and a short checklist for the changeover. The new routine becomes the standard, and the team picks the next biggest loss.
Kaizen in an office
An accounts team keeps correcting invoices sent back by customers. Sorting a month of returned invoices shows most errors come from two missing fields. The team adds the fields to the order form, makes them mandatory and adds a two-line check before sending. Returned invoices are counted again a month later to confirm the change worked.
Kaizen in customer experience
Customer comments about late deliveries keep rising. Reading them by topic shows the main complaint is not the delay itself but not knowing where the parcel is. The team tests a small change for one region: an automatic message when a parcel is delayed, with a new delivery estimate. Complaints about "no information" fall in that region, so the message becomes standard everywhere, and the team moves on to the next topic in the feedback.
Kaizen, lean and Six Sigma
| Approach | Main question | Typical step size |
|---|---|---|
| Kaizen | How can we make this a little better today? | Small, continuous |
| Lean | Where is the waste in the flow of value? | Small to medium |
| Six Sigma | How do we reduce variation and defects? | Project-based (DMAIC) |
| Kaikaku | Should we redesign this from scratch? | Large, occasional |
They are not rivals. Lean and Six Sigma programmes use kaizen as their everyday engine; kaizen borrows their tools for measuring and finding causes.
Common kaizen mistakes
- Treating kaizen as a campaign. A suggestion drive that runs for a month and stops teaches people that improvement is temporary.
- Ideas without follow-up. If suggestions disappear, people stop making them. Answer every idea, even with a no.
- Skipping the measurement. Without a baseline, nobody knows whether a change helped.
- Fixing symptoms. A workaround that hides the problem is not an improvement.
- Not standardising. The improvement lives in one person's head and leaves with them.
- Ignoring the customer's view. Internal metrics improve while customers keep complaining about the same thing.
Where customer feedback fits in kaizen
In service businesses, the best source of kaizen topics is what customers already tell you: complaints, support tickets, survey comments and reviews. The trouble is volume. Thousands of comments are hard to read, so teams improve what they happen to hear about, not what affects the most customers.
This is the part Pivony helps with. Pivony brings tickets, NPS surveys, call centre transcripts, app reviews and other feedback into one place, groups what customers say by meaning, and overlays your segment and operational data, so you see which issue, which segment, which channel and since when, based on all of your feedback rather than a sample. Watching the same feedback after a change also gives your check step a customer-side signal. The kaizen itself, with its owners and standards, stays with your team.
Related reading
- Pareto chart: how to find the vital few problems
- 5 Whys root cause analysis, with CX examples
- Fishbone analysis: a guide for CX teams
- Corrective vs preventive action: a practical CAPA guide
- Free PDCA template
- Free 5 Whys template
Next step
Download the free PDCA template and run your first kaizen cycle from the filled-in example. If your next improvement topic starts in customer complaints, request a free root cause audit on a sample of your tickets, reviews or survey comments, or book a demo.
Frequently asked questions
What does kaizen mean?
Kaizen is a Japanese word made of kai (change) and zen (good). It means improvement, or change for the better. In business it stands for continuous improvement through many small, steady changes made by the people who do the work.
What are the main principles of kaizen?
Go to the place where the work happens (gemba), start from facts and data, find the root cause, remove waste, standardise what works, respect and involve people, and judge improvements by what the customer experiences.
What is a kaizen event?
A kaizen event, or kaizen blitz, is a short and focused workshop, often a few days long, in which a cross-functional team observes one process, measures it, changes it and standardises the result.
What is the difference between kaizen and PDCA?
Kaizen is the philosophy of continuous improvement; PDCA (plan, do, check, act) is the cycle most teams use to run each improvement. A kaizen usually goes through one or more PDCA cycles.
What is the difference between kaizen and lean?
Lean is a management system focused on removing waste from the flow of value. Kaizen is the everyday improvement habit inside it: small, continuous changes made by the people closest to the work.
See root causes on your own feedback
Book a 15-minute demo, or get a free RCA in 48 hours with no sales call.
Related articles
Free quick scan
See your top complaint themes in 24h