Purpose
For a process problem with fluctuating performance, the method brings analysis and improvement into a disciplined sequence. It creates a framework in which numbers, causes, and control come together.
Operations Process model
DMAIC
DMAIC directs improvement work from problem definition through measurement and analysis to controls and lasting transfer.
DMAIC narrows work from the problem space through measurement and analysis to improvement and control. The sequence keeps the measured effect and its stabilisation visible.
How will we improve an existing process through valid measurement, confirmed drivers, and sustainably controlled changes?
- Participants
- 3-10
- Time
- Four to twelve weeks for a typical improvement project; each phase ends with an evidence gate.
Evidence building, analysis, and effectiveness review form a multi-stage initiative.
Define
Project charter
Set problem, customer requirement, CTQ, goal, scope, business case, team, and sponsor in a charter.
Measure
Valid baseline
Map current process, operationalise measures, validate the measurement system, and collect a stratified baseline.
Analyze
Confirmed drivers
Derive potential X drivers from process and data; confirm causes through analysis, comparison, or experiment.
Improve
Verified improvement
Design solutions against confirmed Xs, assess risk, pilot, and verify against baseline.
Control
Control plan
Set process standard, monitoring, reaction plan, owner, and handover; verify stability after implementation.
Add new evidence at review and version decisions with the prior state.
A good fit when
Bei einem Prozessproblem mit schwankender Leistung bringt die Methode Analyse und Verbesserung in eine disziplinierte Folge. Sie schafft einen Rahmen, in dem Zahlen, Ursachen und Steuerung zusammenlaufen.
Ideal for
- Six Sigma projects
- Quality problems
- Process variation
Not good for
- Very small improvements
- Pure ideation
- Problems without data access
Outputs
Control plan
DMAIC project record with charter, validated baseline, confirmed causes, verified pilot, and handed-over control plan.
DMAIC · working structure
Fictional example
Fictional values show the actual method fields.
Project charter
Set problem, customer requirement, CTQ, goal, scope, business case, team, and sponsor in a charter.
Checkout p80 is 18 vs target 10 minutes; scope Saturday pickup Hamburg; sponsor Operations; goal ≤12 by 31 Mar.
Valid baseline
Map current process, operationalise measures, validate the measurement system, and collect a stratified baseline.
Arrival-to-handoff time; 240 cases over four Saturdays; timer agreement ±20 sec; p80 18 minutes.
Confirmed drivers
Derive potential X drivers from process and data; confirm causes through analysis, comparison, or experiment.
Slot clustering explains 46% of variation; inventory sync has no stable effect; regression and shift comparison recorded.
Verified improvement
Design solutions against confirmed Xs, assess risk, pilot, and verify against baseline.
Eight slots/hour on two Saturdays: p80 11.8; rejection 6%; no complaint increase.
Control plan
Set process standard, monitoring, reaction plan, owner, and handover; verify stability after implementation.
Weekly p80; warning >13, action >15; Ops owner; inspect slot profile after two warnings; 30/60-day review.
All values are fictional.
First step
Select an existing process with a measurable performance gap, customer requirement, sponsor, and clear boundary.
Deep dive
How it works
The work narrows step by step from the problem space to measurement, analysis, optimization, and control. This keeps visible which improvement actually carries the measured effect. Completion is only reached once the new performance is also stably secured.
In detail
DMAIC structures problem solving along a reliable data flow. Define clarifies problem, scope, and target; Measure creates a trustworthy measurement base. Analyze identifies causes, Improve develops and tests solutions, and Control anchors the new performance in the process. That connects analysis, implementation, and stabilization in one closed improvement frame.
Facilitation
Clarify sponsor, process boundaries, measurement definitions, and data access in advance. Do not jump straight into Improve before Measure and Analyze are solid. Plan reviews per phase and document decisions on scope, cause, and control plan.
The method guide walks execution through 5 phases, timing, 5 pitfalls, and clear stop criteria.
Open method guideYour perspective
Does this method help with your work?
Your feedback helps shape the next improvements to methodatlas.
Sources and topics
Artifact templates
DMAIC: WorksheetSet subject, evidence, roles, flow, and review.markdown
DMAIC: WorksheetSet subject, evidence, roles, flow, and review.
markdowndmaic-working-template.md
Set subject, evidence, roles, flow, and review.
DMAIC: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Whole initiative Time: Four to twelve weeks for a typical improvement project; each phase ends with an evidence gate.
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: Project charter, voice of customer, process map, measurement system and baseline, cause evidence, pilot, and control plan
- Roles: Process owner/sponsor · DMAIC lead · process participants · data/measurement-system expert · control owner
- Advance information: Select an existing process with a measurable performance gap, customer requirement, sponsor, and clear boundary.
- Overall time needed: Four to twelve weeks for a typical improvement project; each phase ends with an evidence gate.
- Setup: Prepare a workspace with Define · Measure · Analyze · Improve · Control; separate example from live data.
Prepare for the work steps
Define: Project charter
- Select an existing process with a measurable performance gap, customer requirement, sponsor, and clear boundary.
- Project charter, voice of customer, process map, measurement system and baseline, cause evidence, pilot, and control plan
Measure: Valid baseline
- Project charter
Analyze: Confirmed drivers
- Valid baseline
Improve: Verified improvement
- Confirmed drivers
Control: Control plan
- Verified improvement
DMAIC · working structure
Project charter
Set problem, customer requirement, CTQ, goal, scope, business case, team, and sponsor in a charter.
...
Valid baseline
Map current process, operationalise measures, validate the measurement system, and collect a stratified baseline.
...
Confirmed drivers
Derive potential X drivers from process and data; confirm causes through analysis, comparison, or experiment.
...
Verified improvement
Design solutions against confirmed Xs, assess risk, pilot, and verify against baseline.
...
Control plan
Set process standard, monitoring, reaction plan, owner, and handover; verify stability after implementation.
...
The blank worksheet contains prompts only.
Reference · original teaching example
Define: Project charter
Expected artifact: Project charter
Set problem, customer requirement, CTQ, goal, scope, business case, team, and sponsor in a charter.
Entry:
...
- Is the gap measurable, with process, customer, goal, and out-of-scope explicit?
Measure: Valid baseline
Expected artifact: Valid baseline
Map current process, operationalise measures, validate the measurement system, and collect a stratified baseline.
Entry:
...
- Are definition, measurement system, sample, and baseline trustworthy?
Analyze: Confirmed drivers
Expected artifact: Confirmed drivers
Derive potential X drivers from process and data; confirm causes through analysis, comparison, or experiment.
Entry:
...
- Is every priority driver evidenced and distinguished from the symptom?
Improve: Verified improvement
Expected artifact: Verified improvement
Design solutions against confirmed Xs, assess risk, pilot, and verify against baseline.
Entry:
...
- Does the pilot target confirmed drivers and improve outcomes within guardrails?
Control: Control plan
Expected artifact: Control plan
Set process standard, monitoring, reaction plan, owner, and handover; verify stability after implementation.
Entry:
...
- Does the plan specify measure, limit, frequency, owner, and reaction?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/dmaic/run-sheet
Alternatives and neighbors
Fitting alternatives with decision guidance, followed by other related methods.
Operations
8D Problem Solving
Instead of DMAIC, choose 8D Problem Solving when you want to work through a problem in a disciplined way with clear roles, actions, and verification.
Operations
A3 Problem Solving
Instead of DMAIC, choose A3 Problem Solving when a lighter problem-solving format is enough and the improvement cycle should not run as a large-scale process.
Operations
Scatter Diagram
Paired data points reveal whether two variables move together and where a suspected relationship needs deeper proof.
Operations
Causal Factor Analysis
Reconstructs a chain of events, marks factors, and derives verifiable causes and corrective actions.
Operations
Fault Tree Analysis
Models a top event with AND and OR branches to make critical paths and causes visible.
Operations
ABC Analysis
Splits items into A, B, and C by value or effect and directs focus to the most impactful ones.
Constraints and origin
HighWorkshop + async2-12 Wochen
Profile
- Method form
- Process model
- Participants
- 3-10
- Time
- 2-12 Wochen
- Maturity
- Canonical
- Origin
- Motorola Six Sigma
Next up: Standard Work Analysis