Kaizen events: the concentrated week and the preparation it depends on

Scope agreed before anything else is booked

Write down the physical boundary, the problem, the measure and the sponsor before inviting anyone. A boundary is a stated start and end operation, not a department. A problem is specific enough to be wrong, such as material waiting between two named machines, rather than improving productivity in assembly. Without this, the team spends the first day negotiating what they are there for and the second day discovering the real constraint lies outside the boundary. Where scope has to change, the sponsor should agree it explicitly rather than the team drifting, because a wandering event produces recommendations instead of changes.

Who is released, and what that release costs

The team needs operators who work the process daily, someone from maintenance who can build and fit things, and a person from planning or quality with authority to agree changes on the spot. One outsider with no stake is worth including because they ask the questions nobody local dares ask. All of these people have to be genuinely released: cover arranged, phones left, targets adjusted. The unbudgeted cost is supervisory attention, because the area still has to run while its best operator is away. Plants that pretend the event is free end up with participants pulled out on the second morning and a team that never gels.

Preparation that must be finished before the first session

Observation data collected in advance saves a day of the week: cycle observations, a record of stoppages, a layout drawing, samples of the defects being discussed. Physical readiness matters more. Order the fasteners, castors, brackets, bench material and any long-lead parts beforehand. Confirm that services can be moved and that the electrical and safety approvals exist for relocating equipment. Book the fitter and the forklift. A team that spends the week designing something it cannot install has produced a proposal, and proposals decay the moment everyone returns to their normal jobs.

The list that exists on the final afternoon

Every event leaves items that could not be finished, and this list is where most of the value is lost. Each entry needs a named individual, an agreed completion point, and a place where it will be reviewed alongside other plant work rather than in a folder belonging to the improvement team. Keep the list short by finishing things during the week wherever possible; a long list is a sign that the team designed rather than built. A standing follow-up review, with the sponsor present, is what separates a plant where events accumulate results from one where each event starts again from nothing.

When a concentrated week is the wrong instrument

Events suit problems that are physical, local and understood well enough to try something. They suit poorly a technical unknown requiring experiment over a longer period, a problem spread across several plants or a supplier, anything needing capital approval, and anything whose real cause is a decision management has been avoiding. Running an event on the last of these is common and corrosive, because the team correctly identifies a decision they cannot make and learns that the format is decorative. Some problems also need continuous everyday attention instead, which no concentrated week can substitute for.

Frequently asked questions

How long should a focused improvement workshop run?

Long enough to observe, decide, build and test, and short enough that people can be released without disrupting delivery. Most plants settle on a working week for a substantial physical change and a couple of days for something narrow. What matters more than duration is that the block is continuous. Splitting the same hours across several weeks removes the main advantage of the format, because the team loses momentum and participants get pulled back into their normal work between sessions.

Should the same people attend every event?

A core of experienced facilitators helps, but a fixed team turns improvement into a specialism and the rest of the plant into spectators. Rotate operators through so that each area builds its own experience, and always include people from the process being changed, since a team of visitors will design something that ignores a constraint everyone local knows about. Over time the aim is that area teams run their own smaller events with light support.

How do we stop the area reverting once the team goes back to normal work?

Two things do most of the work: the change must be physically difficult to undo, and the standard must be rewritten and taught before the team disbands. If the new arrangement depends on people remembering an agreement, it will decay at the next shift change or holiday period. Build in fixtures, positions and containers that make the old method awkward, then have the area supervisor confirm the new routine daily for the first weeks and report what is drifting.