How to Plan a Kaizen Event: A Step-by-Step Planning Guide and Checklist

A Kaizen event is a short, focused burst of improvement work. A small cross-functional team spends a few days studying one process, removing waste, testing changes, and leaving behind a new standard. Done well, it builds momentum and teaches people how to improve their own work. Done poorly, it becomes a week of meetings that produces a list of ideas nobody owns.

The difference is almost always planning. Most of what makes a Kaizen event succeed happens in the weeks before the team gathers and in the months after they leave the room. This guide walks through every phase: scoping and the charter, picking the team, collecting data before the event, running the event week day by day, the report-out, and the 30/60/90-day follow-up. You will also find a planning checklist, the most common mistakes, and answers to frequent questions.

If you are new to some of the terms used here, such as gemba, standard work, or the eight wastes, the Lean Six Sigma glossary has plain definitions.

Kaizen Event Planning at a Glance

Phase	When	What you finish with
1. Scope and charter	4 to 6 weeks before	A signed one-page charter
2. Select the team	3 to 4 weeks before	A team of 6 to 10, released from regular duties
3. Prepare	1 to 3 weeks before	Baseline data, logistics, and a team kickoff
4. Run the event	Days 1 to 5	Tested changes and new standard work
5. Report out	Day 5	Results and open actions shared with leaders
6. Follow up	30, 60 and 90 days after	Gains confirmed and the charter closed

What Is a Kaizen Event?

“Kaizen” roughly means “change for the better.” In practice, the word describes two things. Daily kaizen is the habit of small, continuous improvements made by everyone. A Kaizen event (also called a Kaizen blitz or rapid improvement event) is a structured, time-boxed workshop, usually three to five days, aimed at a specific problem in a specific process.

A Kaizen event is a good fit when:

• The problem is bounded and the process can be observed directly.
• The people who do the work can be freed up for several days.
• Changes can be tested quickly, without months of approvals or capital spending.
• A leader is willing to make decisions during the week and support the follow-up.

If the problem needs months of data analysis, or the root cause is unknown and complex, a longer DMAIC project may be a better tool. A Kaizen event can still be part of that project, often during the Improve phase.

Phase 1: Scoping and the Kaizen Charter (4 to 6 Weeks Before)

Start planning about four to six weeks before the event. The first and most important step is a scoping meeting with three people:

• The sponsor: a leader with the authority to approve changes and remove barriers.
• The process owner: the person responsible for the process day to day, who will own the new way of working after the event.
• The facilitator: the person who will guide the team through the method.

Pick the right process

Choose a process that matters to customers or the business and that has a visible pain point: long waits, rework, errors, excess inventory, or too many handoffs. Avoid problems that are really about policy, budget, or staffing levels the team cannot change.

Define the boundaries

The most common scoping error is going too wide. Write down exactly where the process starts and where it ends. “Order entry” is too vague. “From the time a customer order is received by email until it is released to the warehouse” is a usable scope. Also note what is out of scope, so the team does not drift.

Check that the data exists

Ask now whether you can measure the problem. If the numbers you need are not already tracked, start simple manual tracking right away, using check sheets, so you have at least two to three weeks of baseline data by the time the event starts.

Write the charter

The Kaizen charter is a one-page agreement that everyone signs off on. It should include:

• Problem statement: what is wrong, where, and how you know, in factual terms.
• Scope: start and end points, plus what is excluded.
• Goals and measures: two or three measurable targets, such as lead time, first-pass yield (the share of work done right the first time), number of steps, or distance traveled.

• Sponsor and process owner.

• Team roles and facilitator. Names can be confirmed during team selection in Phase 2.

• Constraints: budget limits, systems that cannot change, safety or regulatory rules.
• Dates and logistics: event dates, report-out time, and room.

Phase 2: Selecting the Kaizen Team (3 to 4 Weeks Before)

A typical Kaizen team has six to ten people. Smaller teams can lack perspective; larger teams struggle to make decisions. Aim for a mix:

• People who do the work every day. They know where the real problems are, and they will live with the new process. They should be the majority.
• Upstream and downstream partners. The people who hand work to the process and receive work from it.
• Support functions such as IT, maintenance, quality, or finance, if their help will be needed to make changes.
• One or two “fresh eyes.” Someone from outside the area who will ask the obvious questions insiders stop asking.
• A team leader, often the process owner or a supervisor, who will carry the work forward.
• A trained facilitator, who guides the method and keeps the team on schedule but does not own the solution.

The sponsor usually does not sit on the team full time, but should open the event, check in daily, and attend the report-out.

Confirm availability early. Team members need to be fully released from their regular duties for the event. Arrange backfill (someone to cover their normal work) with their managers so they are not pulled out mid-week.

Phase 3: Pre-Event Data and Preparation (1 to 3 Weeks Before)

Good pre-work saves the team a full day during the event.

Gather baseline data

Collect the data you need to measure the charter goals: current lead times, volumes, error or defect rates, cycle times by step, and customer demand. If you started manual tracking in Phase 1, pull it together now. Baseline numbers are what make the before-and-after comparison credible.

Collect process information

Pull existing procedures, forms, system screens, layouts, and any previous improvement work on the same process. A rough walk of the process by the facilitator helps spot surprises early.

Communicate

Tell the people affected by the process that the event is happening, why, and how they can share input. People who are not on the team should not be surprised by changes during the event week.

Handle logistics

Book a room close to the work, with wall space. Gather supplies: sticky notes, butcher paper, markers, tape, stopwatches, and printed data. Confirm the report-out audience and time. Plan meals and breaks. Check that IT, maintenance, or facilities staff are on call if changes will need them.

Hold a pre-event kickoff

A short meeting a week before lets the team review the charter, ask questions, and understand the schedule. It also gives you a last chance to fix a scope that is still too broad.

Phase 4: The Kaizen Event Week, Day by Day

The agenda below assumes a five-day event. Two habits run through every day: a short team huddle each morning to review the plan, and a brief check-in between the facilitator and sponsor at the end of each day to review progress and clear barriers.

Day 1: Training, charter review, and current state

• Sponsor opens the event and explains why it matters.
• The facilitator gives short, just-in-time training on the tools the team will use, such as the eight wastes, process mapping, and standard work (the agreed, written best way to do each step).
• The team reviews the charter and baseline data.
• The team goes to the gemba (where the work happens) to observe, time steps, follow the work, and talk with the people doing it.
• Build a current-state map on the wall: steps, handoffs, waits, and data.

Day 2: Analyze waste and root causes

• Finish the current-state map and identify waste at each step.
• Use simple root cause tools such as the 5 Whys or a fishbone diagram for the largest problems.
• Draft a future-state vision: what the process should look like if the waste were removed.
• Brainstorm countermeasures (possible fixes) and sort them by impact and effort.

Day 3: Design and test improvements

• Select the changes to try first.
• Run quick trials on the real process: move equipment, change a form, combine steps, add visual controls (signs, labels, or boards that show at a glance whether work is on track).
• Measure what happens and adjust. Expect several rounds of trial and adjustment.

Day 4: Refine, standardize, and measure

• Lock in the changes that worked.
• Write standard work for the new process and update visual controls.
• Train other staff who were not on the team.
• Measure results against the baseline. Be honest about what did and did not improve.
• Build the action list (often called a Kaizen newspaper) for items that could not be finished during the week, with an owner and due date for each.

Day 5: Report-out and celebration

• Prepare and deliver the report-out (see below).
• Recognize the team’s work.
• Confirm who owns follow-up and when the first check-in will be.

Running a shorter event

Shorter events compress the same flow. In a three-day event, a common split is: Day 1 for training, the gemba walk, current state, and root causes; Day 2 for testing changes; Day 3 for standard work, results, and the report-out.

Phase 5: The Report-Out (Day 5)

The report-out is a short presentation, usually 30 to 45 minutes, to the sponsor, leaders, and the people affected by the process. Team members, not the facilitator, should present. A simple structure:

1. The problem and charter goals.
2. Current state: what the team saw and measured.
3. Root causes found.
4. Changes made and how they were tested.
5. Results versus baseline, stated plainly.
6. The open action list with owners and dates.
7. What the team needs from leadership.

Leaders should ask questions, thank the team, and publicly commit to supporting the follow-up.

Phase 6: 30/60/90-Day Follow-Up (After the Event)

Many Kaizen events lose their gains in the following months because nobody checks. Build sustainment into the plan before the event starts.

• Weekly for the first month: the team leader reviews the open action list and checks that standard work is being followed. Short huddles at the work area work well.
• 30 days: formal review with the sponsor. Are the measures holding? Are open actions on track? Fix any slips now while they are small.
• 60 days: confirm that most action items are closed and that the new standard work is part of training for new staff. Audit the process against the standard.
• 90 days: final review. Compare results to the baseline and the charter goals. Document lessons learned, close the charter, and decide whether the process needs another event or should move to daily improvement.

Kaizen Event Planning Checklist

Common Kaizen Event Mistakes

• Scope too big. Trying to fix an entire department in a week leads to shallow analysis and an unfinished list. Narrow the scope.
• No real sponsor. Without a leader who can approve changes during the week, the team stalls waiting for decisions.
• Skipping baseline data. Without a before measure, you cannot show improvement, and the team loses credibility.
• Solution already decided. If leadership has already chosen the answer, it is not a Kaizen event. Teams notice, and engagement drops.
• Too few frontline workers. A team of managers designing someone else’s job rarely creates a process that sticks.
• Staying in the conference room. Improvements come from watching the work, not discussing it from memory.
• Treating the report-out as the finish line. Most of the value is protected or lost in the follow-up.
• Facilitator as problem-solver. The facilitator guides the method. The team owns the answers.

Learn to Plan and Lead Kaizen Events With Work Stream

Work Stream Consulting’s instructors have led over 1,000 Kaizen events across many kinds of organizations. That experience shapes our Kaizen Facilitator training program, a 40-hour course that teaches people to scope, plan, facilitate, and sustain Kaizen events like the one described in this guide.

The training is delivered through live instruction, either online or on-site anywhere in the world, or as a hybrid of the two. For teams, our group and on-site training can be built around your own processes, so participants practice on real work. Leaders who sponsor Kaizen events may also benefit from our Lean Leader training program. If you would rather have experienced facilitators run your first events alongside your people, see our process optimization consulting.

Ready to plan your next Kaizen event or train your facilitators? Contact Work Stream Consulting to talk through your goals.

Frequently Asked Questions

How long does it take to plan a Kaizen event?

Most organizations start planning four to six weeks before the event. That allows time to scope the problem, write the charter, pick and release the team, and collect baseline data. Simple, well-understood processes can sometimes be prepared faster.

How long is a Kaizen event?

A typical Kaizen event runs three to five days. Shorter events can work for small, tightly scoped problems, while the follow-up period after the event usually runs about 90 days.

Who should be on a Kaizen event team?

Six to ten people is common. Include people who do the work daily, upstream and downstream partners, any support functions needed to make changes, one or two people from outside the area, a team leader, and a trained facilitator.

What should be in a Kaizen event charter?

A problem statement, a clearly bounded scope, two or three measurable goals, the sponsor and process owner, team roles and facilitator, constraints, and the event and report-out dates.

What happens after a Kaizen event?

The team leader tracks open actions weekly, and the sponsor holds reviews at 30, 60, and 90 days to confirm results are holding, standard work is followed, and remaining actions are closed.

What is the difference between a Kaizen event and daily kaizen?

A Kaizen event is a focused, multi-day workshop on one process. Daily kaizen is the ongoing habit of small improvements made by everyone as part of normal work. Strong organizations use both.

Do I need Kaizen training to facilitate an event?

It helps a great deal. Facilitators need to know the tools, keep the team on schedule, manage group dynamics, and set up sustainment. Kaizen facilitator training gives people a structured method and practice before they lead a real event.