Chris-Maskey/kaizen

Kaizen - Continuous Improvement

Kaizen (改善) means "change for better" in Japanese. It is a philosophy and practice of continuous, incremental improvement involving everyone in an organization—from executives to frontline workers.

When to Use This Skill

• Process inefficiencies or bottlenecks
• Quality issues or recurring defects
• Customer complaints
• Before investing in new technology or equipment
• Engaging teams in improvement culture
• Conducting focused improvement workshops (Kaizen events)
• Eliminating waste in workflows

Core Concepts

The 5 Kaizen Principles

| Principle | Description | | -------------------- | ---------------------------------------------------- | | Know Your Customer | Understand who benefits from your work and what they value | | Let It Flow | Create seamless processes; eliminate waste and bottlenecks | | Go to Gemba | Go to the actual place where work happens to see reality | | Empower People | Involve everyone at all levels in suggesting improvements | | Be Transparent | Make problems visible; don't hide issues—expose them |

The PDCA Cycle

    +-----------+
    |   PLAN    | Identify problem, analyze data, plan change
    +-----+-----+
          |
          v
    +-----+-----+
    |    DO     | Implement small-scale test
    +-----+-----+
          |
          v
    +-----+-----+
    |   CHECK   | Evaluate results against expectations
    +-----+-----+
          |
          v
    +-----+-----+
    |    ACT    | Standardize if successful, or iterate with new plan
    +-----------+

Kaizen vs. Traditional Improvement

| Aspect | Kaizen | Traditional | | -------------- | ----------------------------- | ---------------------------- | | Changes | Small, incremental | Large, radical | | Authority | Everyone participates | Top-down directives | | Timing | Continuous, ongoing | Project-based, episodic | | Risk | Low cost, low risk | High cost, high risk | | Focus | Process improvement | Result outcomes |

The 7 Types of Waste (Muda)

Kaizen seeks to eliminate these wastes:

| Waste | Description | | ---------------- | ---------------------------------------- | | Transport | Unnecessary movement of materials | | Inventory | Excess stock tying up resources | | Motion | Unnecessary movement of people | | Waiting | Idle time between process steps | | Overproduction | Making more than needed | | Overprocessing | More work than required | | Defects | Errors requiring rework |

Memory Aid

Use the acronym TIMWOOD to remember 7 wastes:

T - Transport
I - Inventory
M - Motion
W - Waiting
O - Overproduction
O - Overprocessing
D - Defects

Analysis Framework

Step 1: Define the Problem

Be specific and measurable:

❌ Bad:  "The process is slow"
✅ Good: "Customer onboarding takes 14 days, industry benchmark is 3 days"

❌ Bad:  "We have quality issues"
✅ Good: "Defect rate is 12%, target is below 2%"

Step 2: Go to Gemba

Visit the actual workplace to observe:

• Watch the process as it actually happens
• Talk to people doing the work
• Look for hidden wastes (excess motion, waiting, inventory)
• Collect real data, not reports

Step 3: Map the Current State

Create a value stream map showing:

[Supplier] --> [Input] --> [Process Steps] --> [Output] --> [Customer]

Identify:
- Value-adding steps (green)
- Non-value-adding steps (red)
- Bottlenecks
- Wait times

Step 4: Identify Waste

For each process step, ask:

| Question | If Yes (Waste) | | -------- | -------------- | | Does this transform the material/information? | If no → Non-value-adding | | Would the customer pay for this step? | If no → Non-value-adding | | Can we eliminate this step without breaking the process? | If yes → Eliminate | | Is there unnecessary movement? | If yes → Motion | | Are items waiting between steps? | If yes → Waiting | | Is there excess inventory? | If yes → Inventory |

Step 5: Implement and Iterate

Apply PDCA:

Plan:   Design improvement for highest-impact waste
Do:     Implement on small scale
Check:  Measure before vs. after
Act:    Standardize if successful, or try different approach

Kaizen Events (Kaizen Blitz)

Focused, short-duration improvement workshops.

Event Characteristics

| Attribute | Value | | ----------- | ------------------------- | | Duration | 2-5 days | | Team Size | 5-10 people | | Scope | Specific process or area | | Outcome | Immediate implementation |

Event Structure

1. Define scope and goals — What problem are we solving?
2. Map current state — Value stream mapping
3. Identify waste — Apply TIMWOOD
4. Implement changes — Quick wins first
5. Standardize and document — New process baseline

Before the Event

• Define clear problem statement with metrics
• Assemble cross-functional team
• Gather baseline data
• Prepare materials (sticky notes, markers, current maps)

During the Event

Day 1: Current State
- Present problem statement and data
- Map AS-IS process
- Identify wastes

Day 2-3: Analysis & Design
- Root cause analysis
- Design TO-BE process
- Prioritize improvements

Day 4-5: Implementation
- Implement quick wins
- Train team on new process
- Document new standard work

Output Templates

Kaizen Analysis Template

## Kaizen Analysis

**Process:** [Name] **Date:** [Date] **Team:** [Names]

### Problem Statement

[Clear, measurable description of the problem]

**Current State:** [Metrics]
**Target State:** [Metrics]
**Gap:** [Difference]

### Gemba Findings

**Location:** [Where observation occurred]
**Observations:**
- [Finding 1]
- [Finding 2]
- [Finding 3]

### Waste Identified

| Waste Type | Location | Impact | Priority |
| ---------- | -------- | ------ | -------- |
| [Waste 1]  | [Where]  | [Cost] | High     |
| [Waste 2]  | [Where]  | [Cost] | Medium   |

### Root Causes

1. [Root cause 1]
2. [Root cause 2]
3. [Root cause 3]

### Improvement Plan

| Improvement | PDCA Phase | Owner | Due Date |
| ---------- | ---------- | ----- | -------- |
| [Change 1] | Plan/Do    | [Name]| [Date]   |
| [Change 2] | Plan/Do    | [Name]| [Date]   |

### Expected Results

- **Lead Time:** [X] → [Y] days
- **Cost Savings:** $[X]/month
- **Quality:** [X]% → [Y]% improvement

Kaizen Event Charter Template

## Kaizen Event Charter

**Event Name:** [Name]
**Dates:** [Start] - [End]
**Location:** [Gemba location]

### Problem Statement

[What problem are we solving?]

### Scope

**In Scope:**
- [Item 1]
- [Item 2]

**Out of Scope:**
- [Item 1]
- [Item 2]

### Goals (SMART)

| Metric          | Baseline  | Target   | Owner |
| -------------- | --------- | -------- | ----- |
| [Metric 1]     | [X]       | [Y]      | [Name]|
| [Metric 2]     | [X]       | [Y]      | [Name]|

### Team

| Role      | Name     | Responsibility |
| --------- | -------- | --------------- |
| Leader    | [Name]   | [Role]          |
| Member    | [Name]   | [Role]          |

### Milestones

| Day | Deliverable |
| --- | ----------- |
| 1   | Current state map |
| 2   | Root causes identified |
| 3   | Solutions designed |
| 4-5 | Implementation complete |

Real-World Examples

Manufacturing Example (Toyota Original)

Problem: Assembly line stoppages due to equipment failures

Gemba Finding: Operator waiting 45 minutes for maintenance

Waste Identified: Waiting, Motion (going to get tools)

Kaizen Solution:

• Installed tool crib next to line
• Created preventive maintenance checklist
• Trained operators on basic maintenance

Result: 85% reduction in equipment downtime

Software Development Example

Problem: Feature delivery takes 6 weeks

Gemba Finding:

• Handoff between teams takes 3 weeks
• Testing starts only after development complete
• Many rework cycles

Waste Identified:

• Waiting (dev waits for design)
• Overprocessing (multiple review cycles)
• Motion (context switching)

Kaizen Solution:

• Design-develop-test parallel workflow
• Incremental deliveries every 2 weeks
• Definition of Done for each story

Result: 60% reduction in delivery time

Office Process Example

Problem: Invoice processing takes 30 days

Gemba Finding:

• Invoice sits in inbox for 2 weeks
• Manual data entry with errors
• Approval requires physical signature

Waste Identified:

• Waiting (inbox queue)
• Defects (data entry errors)
• Motion (physical routing)

Kaizen Solution:

• Digital invoice submission
• Automated data extraction
• Email-based approval workflow

Result: 23-day reduction in processing time, 95% accuracy

Key Questions for Kaizen

Use these questions to guide improvement:

| Question | Purpose | | -------- | ------- | | What is the problem we're solving? | Focus | | What does the customer value? | Alignment | | Where is the waste? | Target | | What small change can we test today? | Action | | How will we know it improved? | Measurement | | Who does the work daily? | Involve | | Have we gone to Gemba? | Reality check | | What is hiding in the process? | Visibility |

Best Practices

Do

• Start small — One improvement at a time
• Go to Gemba — See reality, not reports
• Involve everyone — Frontline workers know the waste best
• Measure before and after — Quantify improvements
• Standardize wins — Document new process baseline
• Celebrate improvements — Reinforce continuous improvement culture

Avoid

• Big bang changes — Small increments reduce risk
• Skipping PDCA — Test before full implementation
• Focusing on tools — Kaizen is mindset, not just tools
• Blame individuals — Focus on process, not people
• Improvements that create new waste — Consider downstream effects
• Forgetting to standardize — Without standard, improvement decays

Common Mistakes

| Mistake | Why It's Wrong | Correct Approach | | ------- | -------------- | ---------------- | | Skip Gemba | Reports don't show reality | Go observe firsthand | | Large changes | High risk, hard to isolate cause | Small, testable changes | | No measurement | Can't prove improvement | Baseline and track metrics | | One-time event | Waste returns | Continuous improvement | | Top-down only | Miss frontline insights | Involve everyone | | Copy others | Different context | Adapt to your situation |

Integration with Other Methods

| Method | Combined Use | | ------------------ | ------------------------------------------- | | Five Whys | Find root cause of problems | | Kanban | Visualize and manage improved workflow | | PDCA | Structure continuous improvement cycles | | Value Stream Map | Identify waste in processes | | Six Sigma | Data-driven problem solving for variation | | DMAIC | Structured problem-solving methodology |

Resources

• Lean Production: Kaizen
• Toyota Production System
• Masaaki Imai — Gemba Kaizen (book)
• Kaizen Institute