Kaizen event: meaning, steps and a 3-5 day agenda

A kaizen event is a focused workshop, usually three to five days long, where a small cross-functional team improves one process. The team studies how the work runs today, tests changes and leaves with a new standard way of working.

People also call it a kaizen workshop or a kaizen meeting, although a meeting alone rarely changes anything. This guide covers what a kaizen event is, who takes part and a day-by-day agenda. It also covers measuring results and the mistakes that waste the week.

Key takeaways

A kaizen event is a short, scoped workshop that changes one process, not a general brainstorm.

It complements daily kaizen and does not replace it.

A written charter with a clear scope and a measurable target decides most of the outcome.

The work starts before day one with data and ends after the final day with a 30-day follow-up.

Most failures come from vague scope, missing owners and no follow-up, not from the workshop itself.

What is a kaizen event?

A kaizen event is a time-boxed improvement workshop in which the people who do the work redesign a process with support from others. The word kaizen is Japanese and is usually translated as change for the better.

The event format is a common way to apply kaizen in lean organizations. It is the same idea as everyday improvement, compressed into a few days with a clear target and full attention. See the kaizen method page for the wider practice.

Kaizen event vs daily kaizen vs kaizen blitz

A kaizen event is a planned workshop, and daily kaizen is a continuous habit. A kaizen blitz is a shorter, faster version of an event. The terms overlap, so check what a team means when it uses them.

Daily kaizen means small ideas from frontline staff, tried and adopted within days. Masaaki Imai's 1986 book Kaizen: The Key to Japan's Competitive Success helped spread this view of improvement as everyone's daily job.

A kaizen blitz usually means one or two days aimed at a narrow problem. A full event runs three to five days and tackles a whole process step or work area. Both sit inside the wider practice of continuous improvement.

When should you run a kaizen event?

Run a kaizen event when one process has a clear problem and a known owner. The fix should need several people in the same room. Good candidates are long changeovers, slow order handling, repeated rework or a messy work area.

Skip the event when the problem is not understood, the cause sits outside the team's control or a quick daily fix would do. Events also fail when the people needed cannot be released from their jobs for the full period.

Say a changeover takes 40 minutes and blocks a whole line. That is a good event topic because it is specific, measurable and owned by one area.

Who takes part: kaizen event team roles

A kaizen event team of six to ten people covers a sponsor, a leader, a facilitator, process members and an outside viewpoint. Every role should be named in the charter before the week begins.

The sponsor is a manager who approves the scope, clears obstacles and attends the final report-out. The team leader owns the result and keeps the group on the target.

The facilitator guides the method and the pace, without owning the answers. Process members do the work every day and know where it breaks. One or two outsiders, such as someone from a neighboring team, ask the questions insiders have stopped asking.

How to scope a kaizen event and write the charter

Scope a kaizen event with one process, one start point, one end point and one measurable target. Write them in a one-page charter. A tight scope makes a useful week more likely.

A charter normally holds the problem statement, the process boundaries, the baseline, the target, the team and the dates. It also lists what is out of scope.

An illustrative charter might read: reduce changeover on line 3 from 40 minutes to 25 minutes within the event week, without new equipment. The SMED method often supplies the tools for a goal like this.

A typical kaizen event agenda, day by day

A typical five-day kaizen event agenda moves from understanding, to analysis, to trial, to standardizing, to reporting out. A three-day event compresses days one and two, and days three and four.

Day 1: training and current state. Review the charter, teach the basic tools and walk the process at the gemba. Record the baseline with time observations and a simple process map.

Day 2: analysis. Identify waste, list causes with a 5 Whys or a fishbone diagram and rank improvement ideas by effort and impact.

Day 3: design and trial. Pick the changes, make quick low-cost trials on the real process and use a PDCA cycle to check each one.

Day 4: refine and standardize. Adjust what the trials showed, write the new standard work, update visual controls and train the people who will use them.

Day 5: report out. Present the before-and-after results to the sponsor and the wider area, and agree the open actions with names and dates.

Kaizen event steps: before, during and after

The steps of a kaizen event fall into three phases: preparation, the event week and follow-up. Most of the work that decides success happens outside the week itself.

Before: choose the process, draft the charter, collect baseline data, book the team and the room, and gather supplies for quick trials. Brief the area so nobody is surprised.

During: follow the agenda, test changes on the real process and keep a visible action list. Daily short reviews with the sponsor keep decisions fast.

After: hold the report-out, assign owners to open actions, confirm the new standard is in use and track the measures. Many events stall at the follow-up step.

How to measure kaizen event results

Measure a kaizen event by comparing one or two charter measures before and after, using the same method and the same period lengths. Pick measures the team can count, not opinions.

Common choices are cycle time, changeover time, defects, walking distance, work in progress and lead time. A change to a 25-minute changeover only counts if the 40-minute baseline was measured the same way.

Check again after 30 and 90 days, because early gains often fade. Record any side effects too, such as a faster step that pushes a queue to the next one.

The 30-day follow-up list

A 30-day follow-up list keeps the new way of working in place after the team returns to normal duties. Review it weekly with the sponsor and leader.

Week 1: finish every open action and confirm each has a named owner. Post the new standard work at the process.

Week 2: observe the process at the gemba and check that people follow the standard. Fix confusing steps straight away.

Week 3: re-measure the charter targets and compare them with the baseline and the event-end result.

Week 4: hold a short review, record what was learned and decide the next improvement. Then add the process to your regular daily management routine so it keeps being checked. A kaizen software tool can track the actions if a spreadsheet is not enough.

Common kaizen event mistakes

The most common kaizen event mistake is a vague scope, such as improve the warehouse, which no team can finish in a week. Narrow it until a target and a boundary are obvious.

Other frequent mistakes are running without baseline data and filling the team with managers instead of operators. Jumping to solutions early and skipping follow-up are common too.

A further mistake is treating the event as the whole program. Events work well alongside daily habits, as described in the guide to 5S and kaizen and the wider view in lean continuous improvement.

Frequently asked questions