Kaizen Event Plan & Agenda

Purpose & Scope

This Kaizen Event Plan is a facilitator-ready template to run focused, short-cycle improvement events that produce measurable, sustainable results. Use it to define the problem, align people and data, run rapid experiments, convert improvements into standard work, and verify sustainment at 30/60/90 days.

Before the Event — Prework & Diagnostics

Complete these items before inviting the broader team. The goal is to enter the week with a clear problem, baseline data, and basic materials.

• Problem Statement (A3-style): One sentence problem, impact, location/line, target metric, and target improvement.
• Scope & Boundaries: What is included / excluded (process start/end, equipment, shifts, SKUs)?
• Baseline Metrics: Collect and attach last 30 / 60 / 90 days of relevant data (OEE, cycle time, downtime minutes, defects, throughput).
• Customer/Stakeholder Input: Quick interviews or VOC summary from operations, maintenance, quality, and supervision.
• Initial Process Map / SIPOC: High-level map showing inputs, steps, outputs, and suppliers.
• Required Logistics: Room reservation, visual board, post-its, marker pens, printing of work instructions and data sheets, cameras for gemba photos.
• Team Roster (draft): Facilitator, process owner, subject-matter experts, operators, maintenance, quality, data owner.
• Pre-event Training: Short primer for participants on event purpose, rules, and metrics they will use.

Team Roles & RACI

Define clear responsibilities so decisions and follow-through are owned.

• Facilitator (Lead): Keeps agenda, coaches problem-solving, ensures timeboxes, records decisions.
• Process Owner (Owner): Responsible for implementing changes and converting to standard work.
• Data Owner / Analyst (Support): Provides baseline and event data, runs quick analysis.
• Subject-Matter Experts (SMEs): Provide technical input (maintenance, tooling, quality).
• Operators / Frontline (Doers): Participate in experiments, validate practicality, help draft standard work.
• Sponsor / Leader (Approve): Removes roadblocks and approves resource changes.
• Scribe / Recorder (Record): Captures actions, owners, and measurement plans.

Week-of Hour-by-Hour Agenda (Sample 3-day / compressed 2-day options)

Adjust hours to your plant schedule. Timeboxes keep the event productive.

Day 0 — Kickoff / Prep (2 hours)

1. Welcome, objectives, success criteria (15 min)
2. Problem statement and baseline data review (30 min)
3. Gemba plan and safety brief (15 min)
4. Confirm logistics, roles, and communication rules (30 min)

Day 1 — Observe, Diagnose, Generate Ideas

1. Gemba walk with data collection (60–90 min)
2. Quick process map & identify waste (45 min)
3. Root-cause tools (5-whys, fishbone) in small groups (60 min)
4. Converge on countermeasure ideas using prioritization matrix (45 min)
5. Draft experiments and quick tests (60 min)

Day 2 — Test, Implement, Standardize

1. Run pilot experiments (90–120 min)
2. Measure pilot results against acceptance criteria (30 min)
3. Refine and plan broader rollout (45 min)
4. Update standard work drafts and training notes (60 min)
5. Handover, action assignment, and follow-up schedule (45 min)

Data & Metrics to Collect

Decide a small set (2–5) of outcome and leading metrics. Examples:

• Primary outcome metric (example: throughput parts/hour or first-pass yield %).
• Supporting metrics: cycle time, downtime minutes, changeover time, defect counts, operator walking time.
• Leading indicators: number of experiments run, training completion, SOP updates completed.
• Baseline, target, acceptable range, and measurement frequency for each metric.

Experiment / Change Sign-off Criteria

Before any experiment proceeds, document these minimum items and get the agreed sign-offs.

• Objective: What the experiment intends to prove (linked to metric).
• Acceptance Criteria: Quantitative threshold that defines success (e.g., reduce downtime by 20% in test window).
• Test Plan: Who, when, where, materials/equipment, exact steps.
• Safety/Quality Check: Has maintenance/quality signed off for risk?
• Data Collection Method: How results will be measured and recorded.
• Rollback Plan: Steps to return to previous condition if experiment fails.
• Signatures/Names: Facilitator, process owner, safety/quality rep.

Standard Work Update Checklist

Converting an improvement to lasting practice requires disciplined documentation and training.

1. Draft updated standard work with step-by-step tasks, photos, and acceptance points.
2. Include reasons for change and expected metrics in the doc (context helps adoption).
3. Validate standard work with operators on the line (walk-through).
4. Produce a short visual quick-reference (1 page) for the workstation.
5. Train all affected operators and supervisors; record attendance.
6. Embed checks into the shift handover (who verifies, when).
7. Assign owner to maintain the document and process (owner responsible for reviews).

Handover & 30/60/90-Day Follow-up Schedule

Follow-up turns short-term wins into sustainable improvements. Use this schedule to verify adoption, measure outcomes, and iterate as needed.

• Immediate Handover (Day 0–2): Assign owners, list actions with owners, due dates, and acceptance criteria.
• 30-Day Review: Operator validation, data check vs baseline, update any open actions.
• 60-Day Review: Confirm measurement stability and that updated standard work is in regular use. Close or escalate remaining actions.
• 90-Day Review: Final verification of sustainment. If improvements hold, archive event with final report; if not, plan follow-on countermeasures.

Suggested 30/60/90 Review Template

• Metric snapshot (baseline, current, target)
• Operator feedback summary
• Open actions and their status
• Any quality or safety incidents related to the change
• Decision: Sustain / Adjust / Rollback

Common Pitfalls & How to Avoid Them

• Unclear problem — ensure the problem statement ties to a measurable metric.
• Too many objectives — focus on a single primary outcome to avoid diffusion of effort.
• No data owner — name someone accountable for collection and accuracy.
• Top-down fixes without operator validation — involve operators early and test changes on the floor.
• Failing to standardize — treat pilot success as a start, not the finish.

Templates & Tools (copyable)

Keep these short templates handy for event materials:

One-line Problem Statement

At [location/process], we are experiencing [problem] which causes [impact]. Current metric = [baseline]. Target = [target].

Action Log Row (for each action)

Action | Owner | Due Date | Acceptance Criteria | Status

Experiment Card (one page)

Objective / Steps / Measurement / Acceptance / Rollback / Sign-offs

How to Use This Template

1. Copy the template into your event workspace and fill the prework items at least 3 business days before the event.
2. Use the provided agendas as timeboxes — shorten or extend testing windows as needed but keep decision points strict.
3. Record every action with an owner and due date before closing the event.
4. Schedule 30/60/90 follow-ups immediately and protect the time on calendars.

Notes for Facilitators

Keep the event people-centered. Your job is to enable the team to discover root causes, run rapid experiments, and turn simple, tested countermeasures into reliable standard work. Celebrate measurable wins and make the learning visible.