Skip to content
Let ideas be heard and improvements last.
Gemy

How to plan a kaizen event: a one-week workshop plan

In brief

A kaizen event is a workshop in which a team leaves its daily work to solve one problem within a few days. The preparation, a five-day plan and how to protect the gain after the workshop.

4 November 2026 · 5 min read

Sample company · demo dataKobetsu project: loss, team, steps and target
Kobetsu project

The Lean Enterprise Institute lexicon defines a kaizen workshop as a team effort, usually lasting five days, in which people from different units come together to study a process on the spot and change it. The kaizen page of the US Environmental Protection Agency relays that events last between one and seven days, that teams generally prefer low-cost solutions and aim to implement changes quickly. The two sources meet at the same point: the event is short, focused and done on site. This article gives the one-week plan of such an event.

Before the event: two weeks of preparation

  • Choosing the topic: pick a measurable loss. A bottleneck, high work-in-progress, a recurring quality problem or a long changeover are typical topics. “Improving productivity” is not a topic; “changeover time on line A” is.
  • Target: write the current state as a number and the target as a number. Without numbers the success of the event stays open to argument.
  • Team: the people who do the work should be the majority; one person each from maintenance, quality and planning; one outsider to the process. Team members largely withdraw from their daily work for the week; agree this with their managers in advance.
  • Data: collect existing data before the event, such as downtime records, scrap rate and cycle times. The first day of the week should not be spent collecting data.
  • Logistics: a meeting room, closeness to the floor, a stopwatch, a camera, materials and spending authority for small changes. Waiting for authorisation during the week kills the event.

The five-day plan

  • Day one, understand: a short training in the morning (types of waste, observation method), documenting the current state on the floor in the afternoon. The process is written step by step, times are measured, walking distances are drawn.
  • Day two, find the causes: the biggest losses are ranked with the collected data; 5 Whys is asked for each loss. By the end of the day the team decides which causes it will act on.
  • Day three, try: solution ideas are generated, the simplest and cheapest are chosen and tried on the floor immediately. A layout change, a fixture, a visual marker. If a trial fails it is corrected and tried again.
  • Day four, standardise: the change that works becomes the new standard; the work instruction is updated, a one point lesson is prepared, the people who do the work try the new way.
  • Day five, measure and present: the new state is measured and compared with day one's number; remaining tasks are listed with owners and dates; the team presents the result to management.

What should be in the presentation?

It should be short: before and after numbers, photos of the changes made, the list of remaining tasks and what the team learned. Management's job is not to applaud but to remove the obstacles in front of the remaining tasks and to ask for the result again a month later.

After the event: protecting the gain

The EPA page relays that teams track key measures to confirm the gain lasts and that some companies schedule follow-up meetings after 30 and 90 days. Sustaining is the most neglected phase: the change is made, not measured, and three months later the old habit returns. That is why the last task of day five is to write the date and owner of the measurement a month later.

Common mistakes

  • Choosing too broad a topic: in one week a line gets fixed, not a factory.
  • No one on the team who does the work: a solution designed at the table does not hold on the floor.
  • Putting the event in place of daily kaizen: the Lean Enterprise Institute stresses that workshops should not be relied on alone, and that small daily improvements build the floor's capability. The workshop is an accelerator, not the system itself.
  • Closing the gain with an estimate: if the number written on day five is an estimate, the event is not finished; a measured number is needed.
Sample company · demo dataKobetsu meeting minutes: decisions and tasks
Kobetsu meeting minutes

How it is done in Gemy

  • Work run by a team, with steps and meetings, is opened as a Kobetsu Kaizen project: topic, measurable target, unit, team leader and members, start and target end dates, meeting frequency. The project does not enter an approval flow; the leader and team run it.
  • The project page holds the steps, the action list and meeting minutes; when a meeting day arrives the leader gets a reminder, and an overdue action shows in red.
  • If the time study feature is on, steps are timed with a stopwatch and before / after times sit side by side. An improvement made by one person in a short time is opened as a Kaizen record instead: problem, change, result measurement and sustainment follow-up.
  • Gain is kept as estimate, measurement and finance validation separately and is never summed; persistence is re-measured at set intervals.
  • Gemy has no separate workshop calendar or training content; the week's plan and training belong to the company. Kobetsu, time study and verified value are switched on by the company.

In short

A kaizen event starts with two weeks of preparation: a measurable topic, a numeric target, a team in which the people who do the work are the majority, data collected in advance and spending authority. The five days pass in order through understanding, finding causes, trying, standardising and measuring. A gain is not considered protected until it is re-measured one and three months later. The workshop does not replace daily kaizen; it accelerates it.

Sources

You may copy and share this article with attribution (Gemy, https://www.gemydigital.com/en/blog/kaizen-etkinligi-nasil-planlanir-bir-haftalik-plan).

Related posts

Cookies

Essential cookies are needed for the site to work. Analytics cookies load only if you allow them; declining is as easy as accepting. You can change your choice at any time via the footer link.

Cookie policyPrivacy notice