---
name: kaizen
description: Use when asked to apply Kaizen — continuous, incremental, all-employee process improvement built on the Plan-Do-Check-Act cycle (see plan-do-check-act) — as distinct from a project-scoped Six Sigma DMAIC effort (see dmaic), which is heavier-weight and typically team-led rather than everyone-participating.
---

# Kaizen

Kaizen (Japanese for "continuous improvement") is a philosophy and
methodology emphasizing systematic, incremental process and product
improvement involving *everyone* in an organization — from top management
to frontline workers — rather than a change imposed top-down or run by a
dedicated project team alone.

## Built on PDCA

Kaizen's improvement cycle is [[plan-do-check-act]] applied at a
continuous, everyday cadence:

- **Plan** — identify an opportunity for improvement and develop a plan
  for the change.
- **Do** — implement the plan and make the change.
- **Check** — measure the results to determine whether the change was
  actually effective.
- **Act** — if effective, standardize the change and keep using it; if
  not, identify why and iterate further.

The cycle then repeats, continuously, rather than concluding once one
improvement lands — this ongoing repetition is what distinguishes Kaizen
from a single, one-off process-improvement project.

## Why "everyone," not just management or a project team

Kaizen is explicitly not a top-down approach — it's a collaborative
process where every level of the organization identifies improvement
opportunities and helps implement changes. Teamwork, communication, and
collaboration are central to the philosophy: the frontline workers
closest to a process are often best positioned to notice a small,
concrete improvement opportunity that wouldn't be visible from a
management or project-team vantage point.

## Where it applies

Any process or product, across manufacturing and service industries alike
— used to improve efficiency, quality, safety, and customer satisfaction,
and reported to produce cost savings, increased employee engagement, and
a genuine culture of continuous improvement when it's actually practiced
broadly rather than treated as a slogan.

## Kaizen vs. DMAIC

Both are structured improvement methodologies, but at different scales
and cadences: Kaizen is continuous, incremental, and involves everyone,
suited to ongoing small improvements across the organization; DMAIC (see
[[dmaic]]) is project-scoped, data-intensive, and typically run by
a dedicated team for a defined, often larger problem. Neither replaces
the other — many organizations run Kaizen as the everyday improvement
culture and reach for DMAIC when a specific problem needs a heavier,
more rigorous, data-driven project.

## Common pitfalls

- **Treating Kaizen as a top-down management initiative** — defeats the
  core premise; if frontline workers aren't genuinely empowered to
  identify and drive improvements, it isn't really Kaizen, whatever it's
  called internally.
- **One-off "Kaizen events" with no ongoing cycle afterward** — Kaizen's
  value comes from *continuous* application; a single improvement
  workshop that's never repeated is closer to a one-time project than the
  philosophy it borrowed its name from.
- **Skipping the Check step** — implementing a change without measuring
  whether it actually worked means the organization can't tell whether to
  standardize it or try something else.
- **Using Kaizen's lightweight cycle for a problem that actually needs
  DMAIC's rigor** — a significant, poorly-understood problem often needs
  DMAIC's dedicated data-gathering and root-cause analysis; Kaizen's
  everyday cadence isn't calibrated for that scale.

## Learn more

- [[plan-do-check-act]] for the underlying PDCA cycle Kaizen applies continuously.
- [[dmaic]] for the contrasting project-scoped, data-driven methodology.
- [[always-improving]] for related individual/organizational continuous-improvement thinking from a different angle.