How to Run a Kaizen Event: Agenda, Roles and Results

Disclosure: M365.FM host Mirko Peters works at iFAKT GmbH. This page describes the company factually; paid partnerships and links are labelled as advertising.

By Mirko Peters · 2026-11-11

How to run a kaizen event in five days: when to use one, who does what, a day-by-day agenda, how to prove results and which mistakes make the gains fade.

A kaizen event is a short, focused improvement workshop, commonly lasting about five days, in which a cross-functional team analyzes one specific process, tests changes and sets a new standard. This guide is for continuous improvement managers who have to plan and lead one. You get a practical agenda, the roles you need, the preparation that matters most and the way to show results afterwards. The same format is also called a kaizen blitz, a rapid improvement event or a kaizen workshop.

Key points

• A kaizen event is a short, focused workshop, commonly about five days, in which a cross-functional team improves one specific process.
• Kaizen blitz, rapid improvement event and kaizen workshop are different names for the same format.
• Preparation decides the result: a clear problem, a scope, baseline data, the right team and a charter must exist before day one.
• Use events for problems that need several functions and fast change, and keep daily kaizen running, because leaders should not rely on events alone.
• Follow-up makes gains last: an action plan with owners, checks at the gemba and a result that finance has validated.

What is a kaizen event?

Kaizen is the Japanese word for continuous improvement: small, step-by-step changes that add up. A kaizen event is the intensive form of it. The Lean Enterprise Institute (LEI) describes a kaizen workshop as a group activity in which a team identifies and implements a significant improvement in a process. LEI says it commonly lasts about five days, with a team of staff experts and consultants as well as operators and line managers.

The Kaizen Institute describes the same format as a rapid improvement event, a short-term structured initiative to solve specific problems, and notes that kaizen event and kaizen blitz refer to the same thing. It typically runs three to five intensive days, at the gemba. Gemba is the Japanese word for "the real place", meaning the shop floor where the work happens. Read more in its article on the rapid improvement event.

The word kaizen matters here. An event is not a one-off project. It is one tool inside a continuous improvement process.

When should you use an event instead of daily kaizen?

LEI makes a clear point on its kaizen page: events can produce rapid, significant changes and build capability, but leaders should not rely on them solely. Steady daily kaizen forces management to develop frontline problem-solving skill.

Use this short check before you plan an event. An event fits when:

• The problem is specific and bounded, such as one cell, one line or one flow.
• The cause can be studied with available data before the event begins.
• The fix needs people from more than one function, for example production, maintenance and quality.
• The change can be tested within days.
• A sponsor can free the team for the full period.

If a problem is small and one team can fix it, use daily kaizen. If it is huge, such as the whole plant flow, start with value stream mapping, then cut it into event-sized pieces.

Where does a kaizen event fit among the types of kaizen?

There are three common types of kaizen in a plant. Daily kaizen is the steady stream of small fixes. A kaizen event is the focused week. A longer improvement project, for example a Six Sigma or Lean Six Sigma project, runs over months and relies on statistics. In lean manufacturing, the event sits in the middle: it handles process improvement problems that are too large for one team on a normal shift, and too urgent for a long project. Successful kaizen programs use all three, and they connect them through one board of problems and actions. A kaizen event can help most when a workflow crosses several teams and nobody owns the whole flow.

How do you prepare?

Preparation decides the result. The Kaizen Institute lists the preparation steps: define the problem and objectives, collect data, select a multidisciplinary team, handle logistics and scheduling, and complete a project charter. In practice:

1. Write a charter. One page with the problem, the scope, the target and the measure. Example target: "reduce changeover time on line 3 by 25%".
2. Collect baseline data. Current state numbers for the target process: times, defects, inventory. Do this before the event, not during it.
3. Pick the team. Include operators who do the work. Add a facilitator, a process owner and subject matter experts.
4. Block the time. Free the team for the whole event, and keep the room, tools and data ready.
5. Brief the surrounding teams. Tell neighbors what will change on their shift.

Who does what?

• Sponsor: removes obstacles, approves changes beyond the team's authority, attends the opening and closing.
• Facilitator: guides the method, keeps time, protects the team from interruptions. Usually a continuous improvement specialist.
• Team leader or process owner: owns the process and the follow-up after the event.
• Team members: operators, technicians and engineers who know the process. They do the analysis and the trials.
• Support functions: maintenance, quality, finance and IT, available for questions and for validation.

What does a five-day agenda look like?

This is a typical agenda. Adjust it to the process.

1. Day 1: Understand. Train the team on the method, review the charter and walk the process at the gemba. Draw a current state map, with value stream mapping or process mapping, and confirm the baseline.
2. Day 2: Analyze. Find the root cause of the main losses with the 5 whys or a fishbone diagram. List potential solutions and rank them by impact and effort.
3. Day 3: Test. Try the chosen changes right away in the real process. Use the PDCA cycle: plan, do, check, act. Measure each trial.
4. Day 4: Refine and standardize. Adjust what did not work. Write the new standard, update work instructions, and apply 5S where the layout changed.
5. Day 5: Present and plan. The team presents results to the sponsor and neighbors. Everyone agrees on an action plan with owners and dates.

The PDCA cycle gives a repeatable shape to the tests. Some organizations also use an A3 report to keep the event on one page.

How do you secure the results?

An event without follow-up produces a good week and a poor year. The Kaizen Institute describes follow-up as a PDCA-based action plan with owners, deadlines and indicators, evaluation against goals, standardization, training, and checks of adherence during gemba walks. It also states that gains should be quantified, with validation by the finance department.

Practical rules:

• Review at 30, 60 and 90 days. Compare the metric to the baseline.
• Walk the process. Check on the floor that the new standard is in use.
• Validate the number. Let finance confirm any savings you report.
• Share the learning. Show other teams what worked, so the next event starts further ahead.
• Sustain it. Move open actions into the normal daily routine, so the improvement continues after the event.

Example: planning and payback of one event

This example uses assumed numbers.

A cell has about 120 units of work in process (WIP) and ships 40 units per day. By the simple queue rule (WIP ÷ output per day), the average time in the cell is 120 ÷ 40 = 3 days. The team aims for 80 units of WIP.

• New time in the cell: 80 ÷ 40 = 2 days, one day shorter.
• Event effort: 8 team members × 5 days × 8 hours = 320 hours.
• At €45 per hour: 320 × 45 = €14,400 of working time, before any facilitator or material costs.

Whether that is a good trade depends on the value of a day of lead time and of the inventory you free. The point is to write the cost and the target down before the event, so the result can be judged after it.

Common mistakes

• Choosing a scope that is too big. A team cannot fix a whole plant in five days.
• Starting without baseline data. You cannot prove improvement without a before figure.
• Leaving out the operators. Staff experts alone produce solutions that the floor rejects.
• Treating the event as the goal. The goal is the new standard in daily use.
• No follow-up owner. Gains fade within weeks when nobody checks.
• Relying on events only. Run daily kaizen alongside, so improvement does not depend on a calendar.

How software can help

Before the trials on day 3, you can test options on paper. iFAKT's Polaris Simulator is a module of iFAKT Polaris that tests the production system virtually, for example capacity, staffing and buffer scenarios, and reveals bottlenecks before changes are made. In an event, that lets the team compare ideas on a model first and spend the real trial time on the best ones. A model supports the team's judgment, and it does not replace the trial at the gemba.

Next step

Choose one specific problem this month and write the one-page charter for your next kaizen event: the problem, the scope, the baseline and the target. Then book the team for five days and name the follow-up owner.