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.

Two common event types: 5S and Six Sigma events

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.

Is this a kaizen event problem? Five checks

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.

Filled in, that charter fits on one page. Problem: changeovers on line 3 take 40 minutes on average and happen 3 times a shift, so the line loses 2 hours a shift. Scope: from the last good part of one product to the first good part of the next, on line 3 only. Out of scope: new equipment, changes to the product mix. Baseline: 40 minutes, the average of 6 changeovers timed in the two weeks before the event. Target: 25 minutes by the end of the week. Team: the line 3 team lead as leader, two operators, one setter, one maintenance technician, a quality technician and an engineer from line 1. Sponsor: the production manager. Dates: Monday to Friday, with the report-out at 2 pm Friday.

Add decision rules to the charter. Say what the team can change on its own during the week and what needs the sponsor's approval. Settling this up front saves hours of waiting on day 3.

A typical kaizen event agenda, day by day

The changeover event, day by day: a worked example

Here is how the line 3 charter above might run through the week. The numbers are illustrative.

Day 1. The team reviews the charter, learns the SMED steps, then films one real changeover. Played back, it lasts 41 minutes and has 54 separate steps. The team writes each step on a card with its time.

Day 2. The team sorts the cards. 18 minutes of the 41 are external work done while the line is stopped: fetching the next tooling, finding the right wrench, filling in the setup sheet. Another 8 minutes go on bolts that need many turns, and 6 minutes on trial runs to get the first part right.

Day 3. The team tries changes on the real line. A changeover cart now holds the next tooling and every tool needed, prepared while the line runs. Two of four bolts become quick clamps made in the maintenance shop. The second trial changeover takes 29 minutes.

Day 4. A fixed stop block replaces trial-and-error alignment, and the third and fourth trials take 24 and 26 minutes. The team writes the new standard work for the setter and operators and trains the other shift's setter.

Day 5. The report-out shows 41 minutes before and 25 minutes as the average of the last two trials, which meets the target. Open actions: replace the last two bolts (maintenance, 2 weeks), add the cart to the 5S audit (team lead, 1 week), and re-time changeovers at 30 days (team lead).

The report-out itself fits on one page: the charter target, the before and after times, a photo of the cart, the open actions with owners and dates, and one line on what the team would do differently. Here that was to film two changeovers before the event, not one, since the first day's video ran longer than usual.

A kaizen event board: what goes on the wall

Kaizen event examples outside the factory

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.

Measuring before and after is part of what researchers call structured management. A Census Bureau survey of about 35,000 US manufacturing plants, analyzed by Nicholas Bloom and colleagues in the American Economic Review in 2019, found that structured management practices, such as monitoring performance and setting targets, account for more than 20% of the variation in productivity between plants.

The 30-day follow-up list

What a kaizen event costs, and when it misses

A kaizen event is not free. With 7 people for 5 days at about 8 hours, the week alone costs about 280 team hours. Add around 20 hours of preparation for the leader and facilitator, and a few hours a week of follow-up for a month. In the line 3 example, saving 15 minutes on each of 3 changeovers a shift wins back 45 minutes of line time per shift, so the event pays back within weeks if the gain holds.

To put the team hours in money: US private employers paid an average of $46.89 per hour worked in June 2026, wages and benefits together, according to the Bureau of Labor Statistics. At that average, 280 hours comes to about $13,100 before preparation and follow-up.

Events do miss their targets. When that happens, report the real result honestly, along with what the team learned and what blocked it. A changeover cut from 40 to 31 minutes is still progress, and the remaining steps go on the action list with owners.

Then ask why the target was missed. Common reasons are a cause outside the scope, such as a tooling design problem, or a baseline that was wrong. Fix the scope or the baseline and decide with the sponsor whether to run a short follow-up event.

A supplies and logistics checklist helps the week run on time. Before the event, book a room close to the process, release every team member from their normal job for the full week, and arrange cover for their shifts. Gather a stopwatch or phone for video, flip charts, sticky notes and markers, tape for floor marking, and a small budget for quick trials. Agree with maintenance that they can help on day 3, and tell the area when trials will stop the line.

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