Kaizen event plan & facilitator checklist

Kaizen event plan & facilitator checklist

Purpose: Run short, focused improvement events that produce measurable outcomes at the plant or line level and convert those outcomes into lasting standard work.

How to use this playbook: Treat this as a facilitator toolkit. Use the prework checklist to scope and prepare. Follow the three-phase agenda as a flexible structure (scoping & baseline; root cause & rapid experiments; standardize & handover). Use the measurement templates to capture baseline and targets, and the sustainment checklist to lock improvements into daily work.

Core hunger this serves

Help teams rapidly solve a specific process problem, show measurable improvement, and keep the gain through clear ownership, standard work, and follow-up.

When to run a kaizen

• There is a clearly scoped performance gap tied to a measurable metric (e.g., cycle time, throughput, defect rate, changeover time, downtime).
• Data indicates the problem is local and fixable within a short, focused effort.
• Process owner and frontline staff can participate and commit to follow-through.

Prework checklist (facilitator & sponsor)

• Define the problem: Capture the current condition, the observed impact, and why it matters to the operation.
• Specify the metric: Identify the baseline metric, desired target, unit, and timeframe. Example: Reduce average changeover time from 32 min to 20 min within the event.
• Assemble the team: Process owner, facilitator, data owner, 3–6 frontline contributors, maintenance rep, QA if relevant. Confirm availability during the event window.
• Collect baseline data: Gather objective measurements (preferably 1–2 weeks of data or sample runs). Provide summary chart or table to the team before the event.
• Prepare materials: A3/problem statement template, value stream or process map, sticky notes/markers, camera for gemba photos, stopwatch, data capture sheets, standard work templates.
• Secure sponsor buy-in: Clear scope, decision authority, budget for small experiments, and expectation for sustainment actions.
• Logistics: Reserve workspace, whiteboard, flip charts, and schedule daily check-in and follow-up times.
• Safety check: Ensure any experiments are risk-assessed and safe to run on the shop floor.

Suggested 3‑phase agenda (use as a guide)

Phase: Scoping & Baseline (typical half‑day to one full day)

• Introduce the team, review the sponsor's business context and the proposed problem statement.
• Walk the process (gemba) and collect direct observations with the group.
• Display baseline data and process map; agree a clear, measurable target (SMART-style).
• Identify constraints, non-value steps, and obvious quick fixes for immediate action.

Phase: Root Cause, Solutions & Rapid Experiments (typical one full day)

• Use root cause tools (5 Whys, fishbone) focused on the agreed problem statement.
• Brainstorm countermeasures, prioritize using impact/effort or PICK rules.
• Plan and run safe, rapid experiments (PDCA cycles) on the shop floor to validate ideas.
• Collect data from each experiment and compare to baseline; iterate quickly.

Phase: Standardize, Handover & Sustainment (typical half‑day)

• Document the winning countermeasures as standard work, checklists, or visual cues.
• Assign owners for daily checks, audits, and data collection that will monitor the metric.
• Create a simple control plan with audit frequency and what to do if the metric regresses.
• Plan 30/60/90‑day follow-ups and communicate the change to impacted shifts or teams.

Roles & responsibilities

• Facilitator: Manage agenda, keep the team focused on the problem and the metric, coach problem‑solving methods, and ensure decisions are recorded. The facilitator is neutral and keeps time and scope.
• Process owner: Owns the process and accountability for outcomes and sustainment commitments. Has authority to approve changes in the process and resources for implemention.
• Data owner: Prepares baseline data, supports experiment measurement, and hands over data collection protocols for sustainment reporting.
• Team members: Frontline operators, maintenance, quality—provide practical know‑how, test ideas, and adopt standard work.
• Sponsor: Removes barriers, provides decisions beyond team authority, and ensures the event receives follow-up attention.

Measurement plan (baseline → target → verification)

Capture a minimum viable measurement plan before running experiments.

• Metric name: Clear name and unit (e.g., Cycle Time, seconds per unit).
• Baseline: Document how baseline was measured (dates, sample size, method).
• Target: Specific numeric goal and timeframe.
• Data collection method: Who collects, how often, tool or sheet used, and where data is stored.
• Verification: How improvements will be verified (run charts, before/after samples, defect counts, time studies).

Example SMART metric: "Reduce average downtime per shift on Press #2 from 45 minutes to 20 minutes within 30 days of standard work implementation; maintenance logs will record downtime events daily."

Facilitator checklist (day‑by‑day and event checklist)

• Confirm scope, sponsor, and process owner have signed the event charter.
• Ensure baseline data and visual aids are printed or projected for the team.
• Bring A3/problem statement template and explain how the team will use it.
• Run a safety briefing before any on-floor experiments.
• Keep experiments small, measurable, and reversible when possible.
• Record decisions, owners, and deadlines in a visible place (action board or digital tracker).
• Before close, verify standard work documents are updated, owners are assigned, and follow-up dates are scheduled.

Sustainment & handover checklist

• Update formal standard work and post copies at the workstation.
• Create a control plan: metric, owner, frequency, acceptable bounds, and response steps.
• Schedule short verification audits: daily checks for 2 weeks, weekly for the next month, then monthly.
• Plan a 30/60/90 day review meeting with sponsor and process owner to review data and adjust if needed.
• Capture lessons learned in a short event summary and add to site knowledge base.
• Identify training needs and incorporate changes into onboarding and shift handovers.

Common pitfalls (and how to avoid them)

• Poor scope: Avoid overly broad problems; focus on a measurable slice of the process.
• Missing data: Always collect a defensible baseline. Don’t rely on anecdotes for measurement decisions.
• No owner for sustainment: Assign explicit owners and calendarized follow-ups before closing the event.
• Temporary fixes: Translate quick wins into standard work and visual controls rather than leaving them as ad hoc changes.

Templates & deliverables to produce during the event

• A3 or problem statement (current condition, target condition, root cause, countermeasures, plan)
• Baseline data summary and simple run chart
• Process map or value stream snapshot
• Experiment log (what was tried, when, results, next steps)
• Standard work / control plan and handover checklist
• Event summary with owners and 30/60/90 day follow-up dates

Adaptation notes (tailoring for your site)

Use this playbook as a starting point. For complex processes or cross-functional problems, extend the team and lengthen the experimentation phase. For high-risk environments, involve safety and engineering earlier and run more thorough risk assessments before experiments.

Suggested next steps after the event

1. Publish the event summary and share results with stakeholders.
2. Ensure assigned owners complete the first scheduled audits and report findings.
3. Convert successful practices into training materials and include them in operator onboarding.
4. Consider bundling similar kaizens into a theme-based improvement program (e.g., reduce changeover across all presses).

Resources & image

Image search phrase: kaizen event plan

Suggested templates to add to this playbook: A3 template, experiment log spreadsheet, standard work template, simple run chart generator.