You do not need to spend $5,000 on a Lean consultant to run an effective Kaizen event. You need a specific problem, the right four to eight people, three hours of preparation, and a clear process to follow on the day. That is it.
A Lean workshop — also called a Kaizen event or Kaizen blitz — is a focused, time-boxed improvement session where a small team works on one specific process problem. They map the current state, identify the waste, design a solution, and where possible implement it — all within a single day or short series of sessions. The output is not a report or a set of recommendations. It is a real change to a real process, implemented by the people who run it.
This article walks you through the entire workshop process in five phases — from preparation through to close out. Read it on a Monday. Run your first workshop on a Friday. Your first one will not be perfect. Run it anyway.
Phase 1 — Choose the right problem and prepare properly
Before the day — 2 to 3 hours of preparation
Choosing the right problem is the most consequential decision in the whole exercise. Your first workshop should have a narrow, specific, painful, and measurable scope. Narrow: one process step, one flow, one product family. Painful: the team feels it every week. Measurable: you can time it, count it, or cost it. If you cannot put a number on the current state, you cannot demonstrate improvement.
Three criteria for your first workshop target: it can be addressed in a single day of focused work; the people who do the work have strong opinions about it; and at least one person in the room has the authority to approve a change without a sign-off chain.
Who to invite: four to eight people maximum. At least two or three of the people who actually perform the process steps, plus the person responsible for the process. No passengers. No observers. If someone is in the room, they are working.
Data to gather before the day: you don't need a full VSM before your first workshop — but you do need something. Current average cycle time, queue time at the primary bottleneck, defect or rework rate. Even rough data from a 30-minute floor walk beats opinions. Write the numbers on the whiteboard at the start and let them set the tone.
Room and materials: a whiteboard or large paper on the wall, sticky notes in two colours (problems and ideas), markers, a printed or drawn current state process map, and a timer. Nothing else required.
Three hours of preparation transforms a vague discussion into a focused session with a shared starting point, clear success criteria, and data the team cannot argue with.
Phase 2 — Open the workshop and frame the problem before you try to solve it
60–90 minutes
The opening 60 to 90 minutes set the tone for everything that follows. Get this phase right and the rest of the session flows. Rush it and you will spend the afternoon relitigating the problem rather than solving it.
Start with the data. Put the numbers on the whiteboard before anyone sits down. Do not frame it as a problem management has already diagnosed. Let the data speak: "This process currently takes 18 days from order to dispatch. The actual work takes 2.5 days. Today we are going to understand where the other 15.5 days go."
Walk the process together. If the physical layout allows it, walk the process as a group — stand at each step, observe it, time it, note what the data cannot show. If the process is not walkable, walk through it on the map instead. Observation beats assumption every time.
Agree on success criteria. Before the analysis begins, the group agrees on what today's session is trying to achieve — specific and measurable. Abstract goals produce abstract outputs.
Facilitator role in Phase 2: Ask questions. Do not offer answers. "Why does that step take that long?" "What happens when the drawing is not ready in time?" Your job is to create a shared, data-grounded understanding of the current state — not to diagnose the problem yourself before the team has had the chance to.
The goal of the opening phase is not to agree on solutions — it is to agree on reality. A team that has seen the same data and walked the same process will produce better solutions than one still arguing about what the problem actually is.
Phase 3 — Identify waste and root causes
90–120 minutes
With the current state understood, Phase 3 turns to analysis. Use the 8 wastes of Lean as the analytical lens — work through the relevant categories systematically and ask the team to identify where each waste appears in the process you're reviewing today. Each waste category is a prompt, not an obligation — focus on the two or three that are most clearly present.
Once the wastes are identified, apply 5 Whys to dig below the surface of the most significant ones. Ask "why" until the answer is no longer another symptom. "Why does the job queue at inspection for three days? Because inspection only runs twice a week. Why does it only run twice a week? Because the inspector also manages the QA register and both cannot be done in the same day." The root cause is now specific and addressable.
Facilitator guidance: Capture everything on the whiteboard without filtering in this phase. When the board is full, prioritise: which two or three root causes, if addressed, would have the biggest impact on the target metric? Use dot voting if the group cannot agree.
The most common mistake in Phase 3: the room jumps to solutions before confirming the root cause. The facilitator's job is to keep the team in diagnosis mode: "Let's hold that idea — can we first understand why this waste is happening?"
Solutions designed before the root cause is understood are expensive guesses. Spend more time in Phase 3 than feels necessary — the analysis here determines the quality of everything that comes after it.
Phase 4 — Design and trial solutions
90–120 minutes
For each of the two or three root causes identified in Phase 3, the team generates potential solutions. At this stage, quantity matters more than quality — generate as many ideas as possible before evaluating any of them.
Select the most promising solution using two criteria: impact (will this actually address the root cause?) and effort (can it be implemented today, or at least trialled?). High-impact, low-effort improvements are your first priority. High-impact, high-effort improvements go on the action list with an owner and a deadline.
Where possible, trial the improvement on the floor during the workshop. This is the most powerful thing a Lean workshop can do — the team does not leave with a plan, they leave with a result they implemented themselves. The energy in the room changes when something real changes on the floor.
Document the improved method before moving to Phase 5. It does not need to be a formal SOP immediately — a hand-written description on a single sheet is sufficient for the day, with the formal SOP update as an action item. Without documentation, improvements revert within weeks.
A workshop that produces a trial improvement on the day is worth ten workshops that produce a list of recommendations. The moment the team implements something themselves, CI stops being a management program and becomes their own.
Phase 5 — Close out: actions, owners, measures, and recognition
45–60 minutes
The final 45 to 60 minutes determine whether the workshop produces lasting change or evaporates. More workshops fail in this phase than in any other — not because the analysis was poor, but because the close was rushed and the actions were left without owners.
Every action needs three things: a specific owner (not "the team" — one person), a deadline (not "soon" — a date), and a measurement method. If nobody volunteers to own an action, that action is not a priority — either drop it or assign it explicitly.
Establish the baseline and target. Return to the metric from the start of the day and record today's baseline and the target the team has committed to. This is the number the 30-day review will check against.
Schedule the 30-day review before anyone leaves. A specific date and time, with the same team, in the same format — not "we'll find a time." It checks whether actions were completed, whether the metric has moved, and whether new problems have surfaced.
Recognise specifically what the team achieved. A genuine, specific acknowledgement of what was accomplished is the fuel that makes people willing to come back for the next workshop.
The 30-day review is not administrative overhead — it is what separates a Lean workshop from a Lean conversation. Book it in the room. Make it non-negotiable.
Workshop agenda — one-page reference
| Phase | Timing | What Happens | Key Facilitator Questions |
|---|---|---|---|
| 1 — Prepare | Before the day | Select scope, gather data, book the team, prepare room and materials | What metric are we trying to move? Who can approve a change? |
| 2 — Open | 60–90 min | Present the data, walk the process, agree on success criteria | Why does that step take that long? What would "good" look like? |
| 3 — Analyse | 90–120 min | Identify wastes using the 8 wastes framework, apply 5 Whys, prioritise root causes | What is actually causing this? What are we not seeing? |
| 4 — Improve | 90–120 min | Generate solutions, select highest impact, trial on floor if possible, draft updated SOP | Could we trial this now? Who needs to know about this change? |
| 5 — Close out | 45–60 min | Assign actions with owners and deadlines, set baseline and target, schedule 30-day review, recognise team | Who owns this? By when? What did we achieve today? |
One-Page Lean Workshop Agenda — Print and Use Today
A printable one-page agenda card with all 5 phases, timing guides, facilitator questions, and an action-capture template. Take it into the workshop and keep the session on track.
Download Free →The five most common first-workshop mistakes — and how to avoid them
Running your first Lean workshop will feel uncertain in moments. These are the five failure modes that catch most first-time facilitators — and the specific countermeasures that prevent them.
The team is asked to improve "the whole production scheduling process" rather than the specific queue time between planning and fabrication release.
The facilitator wants to be helpful and chooses a big problem. Big problems require more time, data, and authority than a single workshop can accommodate.
Define the scope before you invite the team. If the problem cannot be fully addressed in a single day, break it down. Start with the one step causing the most pain.
The workshop includes three managers who observe but do not perform the process, and the operators who do the work are not present.
Managers schedule workshops around their own availability. Operators are seen as participants in the solution, not the source of it.
Make operator attendance mandatory, not optional. Without them, the workshop produces management theories, not operational improvements.
The workshop opens with "I think the bottleneck is the inspection step" — and 45 minutes are spent debating whether that impression is accurate.
Data collection feels like extra work before an already full calendar. It gets skipped.
Spend 30 minutes on the floor before the workshop with a clipboard and a stopwatch. Even rough numbers change the quality of every conversation that follows.
The whiteboard is covered in ideas at the end of the day. Nobody is assigned to own any of them. Two weeks later, nothing has changed.
The group is tired at the end of the day and the facilitator does not want to create conflict by pushing for ownership.
Do not close the session until every idea moving forward has a named owner, a date, and a measure. Unowned actions are not actions — they are aspirations.
Actions are assigned and some are completed. But nobody checks whether the metric moved, and the improvement is never confirmed or celebrated.
The workshop was the event. The review feels like admin. It gets pushed to accommodate other priorities.
Book the 30-day review in the calendar before anyone leaves the room. Treat it as mandatory — it's where the workshop's value is confirmed, or where the next problem is found.
When to bring in a consultant — and when you don't need one
Most first Lean workshops do not need external facilitation. A well-prepared internal facilitator with a focused scope, the right team, and basic data will produce a useful result. The discomfort of running it yourself is part of the learning that makes the second workshop better.
Where an external facilitator adds genuine value: when the problem spans multiple departments with competing interests and a neutral facilitator reduces the politics of who is right; when the team has significant scepticism that an external credibility signal can overcome; or when the internal person who would logically facilitate the session is also a key decision-maker in the process.
What a good Lean consultant should do: facilitate, not consult. They ask the questions the internal facilitator might be too close to ask, keep the session on track, and bring experience of what good looks like elsewhere. What they should not do: solve the problem for the team. If the consultant is doing most of the talking, the workshop will not produce a team that can run the next one without them.
The goal of your first few workshops — internally run or externally facilitated — is to build the capability to run every subsequent one yourself. That capability is more valuable than any single improvement the consultant might help you find.
Your first workshop does not need to be perfect.
The facilitation will feel awkward in moments, the scope will be slightly off, and one action item will slip through without a clear owner. Run it anyway — the team will produce something real, and the second workshop will be better. If you want structured support for your first event, Innovengg's Lean team is here to help.
Book Your Free Lean Consultation →