Rapid improvement
One process. A focused event. Movement shaped by scope.
A focused, on-site event on one specific process. A cross-functional team measures the current state, redesigns the flow, and implements the change during the event — not a study that ends in a recommendation. Timing is determined by scope, not a prescribed day-by-day schedule.
What it is
- One process, one measure, one team — aligned before the event
- Current state baselined with real data, not opinion
- Change implemented and standard work written in the room
- A control plan and owner in place before the event closes
What it is
An implemented change, not a recommendation.
The team that runs the process is in the room for the whole event. They measure it, redesign it, and put the new method into service within the agreed scope.
- One process, one measure, one team — aligned before the event
- Current state baselined with real data, not opinion
- Change implemented and standard work written in the room
- A control plan and owner in place before the event closes
Inside the event
Scope and evidence determine where the team moves next. Phases overlap, repeat, and receive different emphasis as the process demands.
See the real work
The team walks the process, collects the real cycle times and defect points, and agrees on one measure the event will move.
Quantify the current state
Waste, queueing, rework loops, and constraint are measured against the baseline — not debated from memory.
Design and test the new flow
The team designs the future state, tries it on the floor in short cycles, and adjusts what does not survive contact with reality.
Implement, standardize, and hand over
Change implemented, standard work written, control plan and owner assigned, and the open items placed on a dated follow-up list.
This is not a sequence of daily assignments. The team moves forward, loops back, and adjusts emphasis based on what the process reveals.
Fit
When a Kaizen event works
- One contained process with a clear start and finish
- The people who run the work can be released for the event
- A sponsor who can approve changes as the event progresses
- A measure both operations and finance accept
When something else fits better
- Cross-functional problems spanning several systems and owners
- A problem with no agreed measure or baseline data
- Changes that require capital approval or a system release
- A stalled program — that starts with a recovery review instead
What you keep
A change that is already live
The event ends with the new method running, not with a slide deck of recommendations.
A measured before and after
The baseline is documented at the start and re-measured after the event so movement is verifiable.
Standard work and a control plan
The new method is written down with an owner, a measure, and a review cadence so it holds.
A team that can run the next one
Participants leave having done the analysis themselves — the method transfers with the result.
FAQ
Common questions about Kaizen events.
Request an event
Tell me the process and the measure.
Scope, team availability, process complexity, and site count determine the timing. I do not prescribe a rigid day-by-day schedule; we confirm the right event shape together before anything is scheduled.
Start the conversation
Start with one process.
Send the details of the process you want to fix and we will confirm whether an event is the right first step.