What is DMAIC methodology? It is a five-phase, data-driven method for fixing a process that already exists but misses its targets. The letters stand for Define, Measure, Analyze, Improve, and Control. In simple terms, DMAIC makes you describe the problem, measure it, find the proven cause, fix that cause, and then lock the gain in so the problem does not return.
This guide goes beyond the acronym. You will see why teams rely on DMAIC, how to run each phase and which tools belong where, a worked example with numbers, how DMAIC relates to Six Sigma, DMADV, and PDSA, and the mistakes that sink most projects.
We write from practice. Lean Six Sigma Experts has delivered consulting, training, and recruiting for Lean Six Sigma since 2011, and DMAIC is the roadmap behind the Green Belt and Black Belt training we deliver.
Why DMAIC matters for process improvement
DMAIC matters because it makes you prove the cause of a problem before you spend money fixing it. Most failed improvement efforts skip that proof.
It replaces guesswork with evidence
Teams under pressure jump to a solution: new software, more staff, another approval step. DMAIC delays that jump. The method proposes no change until step four of five, after you have a measured baseline and a verified root cause. Compare that with PDSA, where a change is planned at step two.
The last phase matters just as much. Control is built into the method, so the gain is documented and owned by someone. Without it, results fade once the project team disbands.
A DMAIC project earns the right to change a process by measuring it first and controlling it last.
Where DMAIC is used
DMAIC grew out of Six Sigma, which engineer Bill Smith developed at Motorola in the 1980s to reduce process variation. Lean Six Sigma later combined it with Lean’s focus on removing waste. Today you find it in manufacturing, healthcare, government, and corporate services. A 2020 systematic review counted 196 manuscripts on Six Sigma in healthcare alone, covering problems such as slow radiology results and medication errors.
Is it still relevant? Yes. Variation and waste have not gone away, and the method does not depend on any single tool. It works the same whether your data comes from a spreadsheet or a production database.
How to apply the five DMAIC phases
Apply DMAIC by working through the five phases in order and finishing each phase’s deliverable before you start the next.
The phases at a glance
Each phase answers one question and ends with one concrete output. The table also shows the tools most teams reach for in each phase.
| Phase | Question it answers | Common tools | Output |
|---|---|---|---|
| Define | What problem are we solving, and for whom? | Voice of the customer, SIPOC, project charter | Charter with problem and goal statements |
| Measure | How bad is it today? | Process map, data collection plan, measurement system analysis, capability analysis | Trusted baseline |
| Analyze | Why does it happen? | Pareto chart, fishbone diagram, 5 whys, hypothesis tests, FMEA | Verified root causes |
| Improve | Which fix works? | Brainstorming, pilots, design of experiments, kaizen event | Tested solution |
| Control | How do we keep it fixed? | Control plan, control charts, standard work, mistake-proofing | Control plan with a named owner |
What to do in each phase
Use this checklist as a working guide. The advice in each step is where projects usually succeed or fail.

- Define: Write a charter with one problem statement, one measurable goal, a scope, a team, and a timeline. "Reduce quote turnaround from 9 days to 5 days" is a goal. "Improve sales" is not.
- Measure: Check that people record data the same way before you collect any. Then gather enough data to cover normal demand swings, not just one quiet week.
- Analyze: Separate the vital few causes from the trivial many, then test your suspected cause with data. A cause you cannot confirm is still a guess.
- Improve: Pilot the fix on a small scale before rollout. Prefer fixes built into the process flow, such as required fields or hard stops, over reminders that rely on people’s memory.
- Control: Name a process owner, the metric, its limits, and what to do when it drifts. Then track it on a control chart.
Finish each phase’s deliverable before starting the next, because every later phase builds on it.
A worked DMAIC example with numbers
The example below is hypothetical, but the steps and arithmetic are typical of a real project. It shows how the phases hand results to each other.
A quote turnaround project
A distributor takes an average of 9 days to send customers a quote. Customers complain, and sales leaders want 5 days. The table shows what the team does in each phase.

| Phase | What the team did | Result |
|---|---|---|
| Define | Wrote a charter targeting 5-day average turnaround and confirmed with customer feedback that speed was the top complaint | Agreed scope and goal |
| Measure | Aligned how staff log start and end times, then timed 200 recent quotes | Baseline of 9.0 days |
| Analyze | Pareto chart of delay reasons: missing customer specs 55%, waiting for pricing approval 30%, other 15% | Two causes explain 85% of delays |
| Improve | Added a required-field intake form and pre-approved pricing bands, piloted for 4 weeks with one sales team | Average fell to 4.8 days |
| Control | Weekly control chart owned by the sales operations manager, with a reaction plan if the weekly average passes 5.5 days | Gain tracked |
What the example shows
The average dropped from 9.0 to 4.8 days, a reduction of 4.2 days or about 47%. The team beat its 5-day goal because the Pareto chart pointed it at the two causes behind 85% of the delay. Without that analysis, it might have hired more quote writers and fixed nothing.
Notice also what the team did not do. It never changed the process during Define, Measure, or Analyze. Every change waited for evidence, and the pilot confirmed it before the full rollout.
The Pareto chart told the team where to act, so it did not spread effort across fifteen small causes.
DMAIC compared with Six Sigma, DMADV, and PDSA
DMAIC is the improvement roadmap inside Six Sigma, not a rival to it. DMADV and PDSA solve different problems.
DMAIC versus Six Sigma
Six Sigma is the broader quality discipline. It covers statistical methods, project selection, and the belt roles from Yellow to Master Black Belt. DMAIC is the project roadmap that Six Sigma teams follow to improve an existing process. Lean Six Sigma adds Lean’s tools for removing waste, so a DMAIC project often uses tools from both.
DMAIC versus DMADV and PDSA
Pick the method by what you are working on:

- DMAIC improves a process that already runs but underperforms.
- DMADV (Define, Measure, Analyze, Design, Verify) builds a new product or service, or completely redesigns a process that cannot be repaired.
- PDSA (Plan, Do, Study, Act) tests small changes quickly. It proposes a change earlier than DMAIC, so it suits low-risk fixes where the cause is already clear.
If the process exists and the cause is unknown, use DMAIC. If the process does not exist yet, use DMADV.
When to use DMAIC and what goes wrong
Use DMAIC when a process exists, you can collect data on it, and nobody can yet say why it fails. It fits complex or high-risk problems best.
When DMAIC is the right choice
If the fix is obvious and cheap, just make it. A missing label does not need a five-phase project. DMAIC pays off when the cause is unclear, the cost of a wrong fix is high, or earlier fixes have failed. You can run it two ways: a part-time team that works over several months, or a kaizen event that compresses the cycle into about a week with the team pulled off regular duties.
Common mistakes
These problems account for most stalled projects:
- Vague scope. A goal such as "improve quality" gives the team nothing to measure.
- Unchecked measurement. If people record data differently, your baseline means nothing.
- Jumping to Improve. Teams skip Analyze because they already "know" the cause.
- No owner in Control. A control plan that belongs to everyone belongs to no one.
Building the skills to lead a project
The belt level sets how deep you can go. Our Yellow Belt online course (about 12 hours, $650) introduces Six Sigma methods and suits people with a project and time already assigned. The Green Belt online course (about 28 hours, $1,195) expands on each DMAIC stage with an emphasis on measuring. The Black Belt online course (about 43 hours, $1,795) goes further into analysis, covering hypothesis tests, ANOVA, and multiple regression, and requires Green Belt first.
Putting DMAIC to work
DMAIC is a disciplined way to fix an existing process. You define the problem, measure the baseline, prove the cause, test a fix, and control the result. The order is the point. Each phase stops you from acting on a hunch, and the Control phase keeps the gain after the project team moves on.
Start small. Pick one process with a measurable problem and data you can collect, write a charter with a number in the goal, and resist changing anything until Analyze gives you a confirmed cause.
If you want a second opinion on your first project, Lean Six Sigma Experts offers a free 30-minute assessment with no obligation. Contact our Lean Six Sigma team to talk through your process and decide whether DMAIC fits.
