Home › The Garage › DMAIC
Lean

DMAIC

DMAIC is Six Sigma's backbone: a disciplined, data-driven march from a vague problem to a measured, controlled fix. It's deliberately heavier than everyday improvement — because it's built for the problems that are worth the rigour.

By LeanBean · Updated November 2026 · 6 min read
What's in this guide
  1. What DMAIC is
  2. The five phases
  3. Why Control is the phase that's skipped
  4. When to use DMAIC vs PDCA
  5. Common questions
Definethe problem Measurethe baseline Analysethe root cause Improvethe process Controlhold the gain Each phase has a gate: you don't move on until its question is answered with data.
Five phases, each gated by evidence. Control is what stops the problem creeping back.

What DMAIC is

DMAIC — Define, Measure, Analyse, Improve, Control — is the core problem-solving method of Six Sigma. It's a structured, data-driven sequence for taking a complex problem whose cause isn't yet known and driving it to a measured, sustained fix. Each phase is gated: you don't advance until its question is answered with evidence, which is what gives DMAIC its rigour — and what makes it heavier than a quick PDCA loop.

The five phases

Why Control is the phase that's skipped

An improvement without Control is a temporary result
Teams celebrate at Improve and move on — and six months later the metric has drifted back. Control is the unglamorous phase that makes the gain permanent: the new standard, the monitoring that catches drift, and the owner who acts on it. Skipping it is the single most common reason Six Sigma projects don't hold.

When to use DMAIC vs PDCA

Reach for DMAIC when the problem is complex, costly, and its cause is unknown — a defect rate you can't explain, a process that fails in ways no one can predict. Its measurement discipline earns its overhead there. For everyday, continuous, low-risk improvement where the fix is fairly obvious, a lighter PDCA loop is faster and perfectly sufficient. Most organisations need both: PDCA for the many small loops, DMAIC for the few problems worth a rigorous project.

Describe a process. Get the whole analysis.

LeanBean turns a plain-language description of any process into a professional map — with Lean waste, SIPOC, design-thinking, AI-readiness and capacity analysis built in, and a Transformation Coach that sequences the fixes. Free to start.

Build your first map free →

Keep learning in the Garage

Short, practical lessons on Lean, process mapping and AI-ready operations — the same thinking that powers LeanBean, in two minutes or less. Follow along and build the habit.

Common questions

What does DMAIC stand for?

Define, Measure, Analyse, Improve, Control — the five-phase, data-driven problem-solving method at the core of Six Sigma. It's built for complex problems whose cause isn't yet known, with each phase gated by evidence before you move on.

What happens in each DMAIC phase?

Define: state the problem, customer requirement and scope. Measure: baseline current performance. Analyse: find and validate the root cause with data. Improve: design, test and implement a fix that moves the baseline. Control: standardise and monitor so the gain holds.

Why is the Control phase important?

Because an improvement without Control drifts back within months. Control makes the gain permanent through standard work, monitoring that catches drift, and an owner who acts on it. Skipping it is the most common reason Six Sigma projects don't hold.

When should I use DMAIC instead of PDCA?

Use DMAIC when a problem is complex, costly and its cause is unknown — the measurement rigour earns its overhead there. For everyday, low-risk improvement where the fix is fairly obvious, a lighter PDCA loop is faster and sufficient.

Related guides: The PDCA cycle · Root cause analysis · SIPOC explained