Academy » Lean Foundations

Lean Foundations — Lesson 8: Kaizen: Small Improvements That Add Up

Lean Foundations · 5 min read · 06.10.2026

The eighth lesson of the Lean Basics series. Behind you are the tools that give production a system: 5S, value stream, SMED, standards, kanban, TPM. Today we add the engine that keeps them moving. We'll cover what kaizen is and what it isn't, why small improvements add up faster than large projects, and how to get a kaizen event and daily improvement running on your shop floor. At the end there's an exercise — a Friday morning is all it takes.

Kaizen is a change for the better that every worker can manage every day

Kaizen comes from Japanese: kai means change, zen movement toward the better. It's not a project or an investment. It's small, everyday improvements from the people who do the work. A machine operator walks their workstation a hundred times a month; a manager does it once — and with an escort. Whoever is closer to the work sees more problems and more solutions.

An example from a machining operation. A rack of fixtures stood three meters from the machine, and the operator walked to it twenty times per shift. Moving it next to the machine saved 6 seconds per piece. At 900 pieces a day, that's 90 minutes a day and over 300 hours a year. Cost: half a day of work and four bolts.

Kaizen doesn't replace big changes — innovation and investment have their place. But in one thing it beats them: it doesn't wait for a budget. While an investment waits for next year's planning cycle, you can have your first improvement done by Monday morning.

An improvement that doesn't become a standard will be forgotten by the shop within a month.

In lesson five the rule was: a standard is a starting point, not a goal. Kaizen is how that starting point moves forward.

Why small improvements add up faster than large projects

The math is simple. A 30-second improvement per piece at 400 pieces a day saves 200 minutes a day. At 220 working days, that's nearly 730 hours a year — 91 days of one person's work. And that's a single improvement at a single workstation.

The greater power lies elsewhere. Standards work like the ratchet in a socket wrench: they move forward and never slip back. An improvement written into standard work doesn't get lost — a year later it's still there, and further improvements build on top of it. The results of large projects often erode once the project team leaves. A standard that the operator adjusted themselves, that operator will also defend.

The mechanism is called small-scale PDCA. Plan a change for one day, try it, measure it, then write it up or revert it. You can complete the whole cycle in a week. In projects at Foreast, we see that three such cycles a month in one team deliver more than a six-month project with the same goal.

Two speeds: the kaizen event and daily kaizen

A kaizen event lasts three to five days and tackles one theme — material flow, workstation layout, operator walking. The team has six to eight people: operators, a foreman, a process engineer, someone from quality. The iron rule: anything that can be tested by Friday gets tested by Friday. The prototype is built from whatever is on the shop floor — plywood, adhesive tape, an unused rack. The expensive solution comes only after the cheap one has proven its worth.

In a press shop, our team rearranged the pickup point and the cart route during one event. Operator walking dropped from 1.9 km to 0.8 km per shift, and the press waiting for material disappeared. Investment: zero.

Daily kaizen runs between events. An idea board by the line, a 15-minute walk once a week. Every suggestion gets an answer within seven days — even if the answer is no. Rejecting an idea without a word of explanation is the fastest way to kill the system.

Measure the number of implemented ideas per worker per year. World-class plants talk in tens. In most companies where our projects begin, the figure is below one. The difference isn't in the people. It's in whether the person with an idea has somewhere to take it.

Management's role: ask “what's slowing you down?”, not “why are you behind?”. Give the team a small budget — say, €150 per improvement without approval. Praise implemented ideas, not just the accounting effect. Even a rejected experiment is information.

This Week's Exercise

Pick one workstation and an operator who has worked there for at least a year. Stand to the side for twenty minutes and observe. Then ask three questions: What slows you down the most? What would you change first? What do you search for most often?

From the answers, choose one improvement you can complete in two hours for less than €50. Measure the before and after: seconds per piece, meters walked, number of searches. Write the change into the workstation standard. If you have an idea board, pin up the result with a before-and-after photo.

Key Takeaways

  • Kaizen means small, cheap, fast improvements from the people doing the work — they don't wait for a budget or a project.
  • The math of small things: 6 seconds per piece at 900 pieces a day is over 300 hours a year.
  • Always write the improvement into the standard — it works like a ratchet that holds the gains in place.
  • Measure implemented ideas per worker per year and respond to every suggestion within seven days.

Kaizen doesn't look impressive — a rack moved, a box relocated, a standard updated. That's exactly why it works. If you'd like to roll out the Lean Basics series and further lessons to your whole team, check out our e-learning offering. The next lesson will cover visual management — a shop floor that shows the problem by itself, before anyone has to report it.


Quiz — test your knowledge


« Lesson 7  |  Lesson 9 »

« Back to the academy