A team on an assembly cell spends a morning watching one operator build a sub-assembly. Every few minutes she walks to a rack at the end of the line for fasteners, then waits for the torque tool another operator is using. Nobody had noticed, because it had always been done that way. The team has done 5S training. They can name the five Ss. What they have not practised is seeing this walking and waiting as waste, and designing a change they could test.
This is an illustrative scenario, not a documented customer case. It shows the gap that kaizen training exercises should close: moving teams from knowing the vocabulary to identifying waste in their own process and proposing an improvement that can be checked against a baseline. This guide is for plant training managers and the maintenance or quality leads who run improvement work.
What are kaizen training exercises?
Kaizen training exercises are practice tasks in which learners observe a real or realistic process, identify waste, and design a small improvement they can test. The Lean Enterprise Institute describes kaizen as a Japanese word meaning "continuous improvement" and says the kaizen process is based on Plan-Do-Check-Act cycles. A good exercise asks learners to work through that cycle, not to recite it.
Quick facts
| Question | Short answer |
|---|---|
| What is the task? | Identify waste in a process and design a testable improvement. |
| What is 5S? | Sort, Set in order (or Straighten), Shine, Standardise and Sustain: workplace practices that support visual control. |
| What do you score? | Quality of the diagnosis and feasibility of the proposed experiment. |
| Is knowing the 5S terms enough? | No. It shows the vocabulary was taught, not that a team can spot waste in a new process. |
| Who validates the case? | A maintenance or quality lead who knows the process. |
| What can training not fix? | Layout constraints, staffing, supply problems and a culture where suggestions go nowhere. |
| How do you know it worked? | A new, unseen process scored against agreed criteria, then a supervised improvement on the line. |
1. Describe the performance problem
Start with the job. A shop-floor team should be able to watch its own work, name what does not add value, and propose a change small enough to try and measure. That calls for observation, analysis and design, not recall.
The Lean Enterprise Institute defines muda as "any activity that consumes resources without creating value for the customer". It separates waste that cannot be removed at once, such as rework a process still needs, from waste that can be removed quickly through kaizen, such as repeated movement of products between steps. Teams need to tell the two apart. Otherwise they either propose changes that cannot work yet or ignore quick wins in front of them.
The same source describes the purpose of 5S as more than "a one-time housecleaning", and quotes Michael Ballé's warning about 5S programmes that turn into "a bureaucratic program to make the workplace look neat". If your 5S training ends with a tidier workstation and a filled-in audit sheet, it may be teaching the look of improvement rather than the habit.
2. Diagnose the learning and context gaps
Compare what the job needs with what your current training practises and assesses.
- Does current practice use a real process? If learners sort a box of mixed items in a classroom, they have practised the first S. They have not practised finding waste in a process they did not design.
- What is the cognitive demand? In Bloom's revised taxonomy, breaking a process into value-adding and non-value-adding steps is analysis, judging which change is worth testing is evaluation, and designing the new workflow is creation. Naming the five Ss sits at the remember level. Our guide to matching learning activities to Bloom's taxonomy shows how to read these demands.
- Is something other than skill in the way? If a team has no time away from the line, no authority to move a rack, or no one to approve a trial, more training will not produce improvements. Check staffing, tools and procedures first, and report blockers to whoever owns them.
3. Design purposeful preparation and practice
Give each stage a distinct job.
Preparation: confirm the basics. A short self-paced check on the terms the exercises rely on: the five Ss, the types of waste your site uses, and how your plant runs a Plan-Do-Check-Act cycle. A recall check like this confirms prerequisites only. Do not report it as capability.
Practice: exercises that make teams decide. Three kaizen training exercises, in rising order of demand:
- Spot the waste. Show a short video or written walk-through of a process. Each learner lists every step that does not add value and labels it, for example walking, waiting or searching. Compare lists, then discuss the steps people missed.
- Map the movement. Learners draw the path a part takes through the cell. The Lean Enterprise Institute calls this a spaghetti chart, because the route often looks like a plate of spaghetti. Many teams draw the operator's walking path the same way. The map makes walking and backtracking visible.
- Design the experiment. For one waste, the team proposes a change, states what they expect it to improve, says how they will measure it against today's baseline, and names what could go wrong.
Feedback linked to decisions. "You spotted the walking but not the waiting for the shared tool" is more useful than a total score. Feedback on the experiment should ask whether the measure would show the change, not whether the idea sounds good.
Live input or asynchronous review? Live input adds most value when teams compare their waste lists and argue about which change to test, because the disagreement is the lesson. Asynchronous review is enough for the vocabulary and for checking a waste list against an annotated expert list. A common mix is self-paced preparation, then a facilitated session on the line or on the case.
4. Work through a realistic example
Illustrative. A maintenance or quality lead should validate the case and the answer criteria before use.
The case. An operator builds a sub-assembly at a workstation. Fasteners are stored at the end of the line. A torque tool is shared with the next station. The team has a short video of three build cycles and the station's current cycle time.
The task. The team lists the waste they see, picks one to address, and writes a one-page improvement proposal: the change, the expected effect, the baseline measure, how long the trial runs and who must approve it.
A first attempt. The team spots the walk to the fastener rack and proposes moving all fasteners to the workstation. They do not mention the wait for the shared tool. Their proposal says the change "will save time" but gives no baseline and no way to check.
Feedback and retry. The facilitator asks the team to watch the video again and time each walk and each wait. They now see that waiting for the tool takes longer than walking for fasteners. The facilitator asks: what would you measure before and after, and what might the change disrupt?
A stronger attempt. "Waste observed: walking to the rack, about four trips per cycle, and waiting for the shared torque tool. We propose a trial of a second tool at this station for one week. Baseline: cycle time and waiting time from three timed cycles today. Check: the same measures at the end of the trial. Risk: the second tool needs calibration, so we need sign-off from maintenance. If waiting does not fall, we return the tool and try the fastener change next."
Why each response is defensible or incomplete. Judge each against approved criteria, not the facilitator's preference. The first attempt finds real waste but misses the larger one and proposes a change that cannot be tested. The stronger attempt prioritises using evidence, defines a baseline and a check, and names who must approve. It also avoids claiming success before the trial, which is the point of the "Check" step.
5. Assess capability and plan transfer
Evidence of capability is a team's response to a new process it has not seen. Score a short rubric from 0 to 2 for each criterion, defined with your maintenance or quality lead.
| Criterion | Observable evidence |
|---|---|
| Diagnosis | Identifies the waste in the process, prioritises it, and records the evidence for it. |
| Experiment design | Proposes a change with an expected effect, a baseline, a check and a time limit. |
| Boundaries | Uses approved procedures, names who must approve the change, and seeks help when information or authority is missing. |
Anchors: 0 means absent or unsupported, 1 means partial with relevant omissions, and 2 means complete and justified against agreed criteria. Define critical errors separately, for example a proposal that bypasses a safety guard or a calibration requirement, so a good overall score cannot hide one. This rubric is a proposed starting point, not a validated readiness standard. Our guide to assessing judgement and problem solving in training covers calibrating assessors and writing anchors.
Workplace follow-up. After suitable time on the line, ask each team to run one supervised improvement on its own process. The Lean Enterprise Institute describes a kaizen workshop as a group activity, commonly lasting five days, in which a team identifies and implements a significant improvement in a process. Your follow-up can be much smaller. What matters is that the team defines a baseline, runs the trial and reports what happened, including when the change did not help.
Measure what changed
Score the same two measures, quality of diagnosis and feasibility of the experiment, on a baseline task and on an unseen follow-up task. Define the population, the denominator and the timing. If you also track line results, such as cycle time or the number of improvement trials completed, check what else changed in the same period, such as new equipment, a different product mix or staffing, before crediting the training. A suggested change is not a verified improvement until its check is complete.
Where interactive delivery helps
Interactive formats help with the parts of this design that depend on everyone committing before they see the group. In a live session, a facilitator can play the process video, ask every participant to submit the wastes they spotted, and then show the spread before the discussion starts. The same case can run self-paced as preparation. AhaSlides supports interactive learning and moving between live and self-paced delivery. Check any authoring, feedback or reporting function you plan to rely on against your own workflow, and treat simulators, AI and system integrations as external or unconfirmed until you have seen them work. For a related manufacturing design, see our guide to operator troubleshooting training.
What training will not fix
- Layout and space. A team can propose moving a rack. Someone still has to approve and fund it.
- Staffing and time. Improvement work needs time off the line, which is a rostering decision.
- Supply and equipment. A shortage of tools or parts is a purchasing problem, not a skills gap.
- What happens to suggestions. If proposals are never tried, teams stop making them.
- Evidence limits. One case shows one set of choices. A score does not describe how a team improves its work in general.
Name these to sponsors early and agree who fixes each one.
Frequently asked questions
What are kaizen training exercises?
Practice tasks in which learners find waste in a process and design a small improvement they can test, using the Plan-Do-Check-Act cycle.
What are some examples of kaizen exercises?
Spotting waste in a process video, mapping an operator's movement with a spaghetti chart, and writing a one-page improvement proposal with a baseline and a check.
Is 5S the same as kaizen?
No. 5S is a set of workplace practices that support visual control and stability. Kaizen is continuous improvement, and 5S is often one of the first methods a team uses within it.
How do you know kaizen training worked?
Score a new, unseen process for quality of diagnosis and feasibility of the proposed experiment, compare it with a baseline, then check that teams run and report a real trial on the line.
Where to start
Pick one process your teams run every day. Film three cycles, have a maintenance or quality lead agree the main wastes in it, and draft the three-criterion rubric. Run the "spot the waste" exercise with one team, then score a new process before you roll it out.
To see how a case like this could run live and be reused self-paced afterwards, explore AhaSlides.
