methodatlas
Method guideOperations

DMAIC

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityHigh
Time2-12 Wochen
Participants3-10
FormatWorkshop + async
MaturityCanonical
Plan DMAIC
01

Prerequisite

What needs to be finished first

Complete firstClear boundary

Select an existing process with a measurable performance gap, customer requirement, sponsor, and clear boundary.

Without a boundary, cases, periods, or variables become mixed.
Complete firstEvidence access

Project charter, voice of customer, process map, measurement system and baseline, cause evidence, pilot, and control plan

Missing sources remain visible as uncertainty.
02

Preparation

What needs to be ready before start

Materials

Project charter, voice of customer, process map, measurement system and baseline, cause evidence, pilot, and control plan

People / roles

Process owner/sponsor · DMAIC lead · process participants · data/measurement-system expert · control owner

Pre-read

Select an existing process with a measurable performance gap, customer requirement, sponsor, and clear boundary.

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.

03

Core question

The one question this method answers

How will we improve an existing process through valid measurement, confirmed drivers, and sustainably controlled changes?

04

Flow

Phases with goal, actions, output and pitfall

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.

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.

Reference · original teaching example

  1. 1

    Define

    Project charter

    Goal

    Project charter: Set problem, customer requirement, CTQ, goal, scope, business case, team, and sponsor in a charter.

    Inputs for this step

    • 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

    Actions

    • Set problem, customer requirement, CTQ, goal, scope, business case, team, and sponsor in a charter.

    Output

    Project charter

    Set problem, customer requirement, CTQ, goal, scope, business case, team, and sponsor in a charter.

    Quality check

    Is the gap measurable, with process, customer, goal, and out-of-scope explicit?

    Pitfall

    The charter already mandates a favourite solution. State problem and goal in CTQ measures; remove solutions from Define.

    Timing: One to two weeks

  2. 2

    Measure

    Valid baseline

    Goal

    Valid baseline: Map current process, operationalise measures, validate the measurement system, and collect a stratified baseline.

    Inputs for this step

    • Project charter

    Actions

    • Map current process, operationalise measures, validate the measurement system, and collect a stratified baseline.

    Output

    Valid baseline

    Map current process, operationalise measures, validate the measurement system, and collect a stratified baseline.

    Quality check

    Are definition, measurement system, sample, and baseline trustworthy?

    Pitfall

    Analysis starts from unvalidated dashboard values. Validate operational definition and measurement system, then recollect baseline.

    Timing: One to three weeks

  3. 3

    Analyze

    Confirmed drivers

    Goal

    Confirmed drivers: Derive potential X drivers from process and data; confirm causes through analysis, comparison, or experiment.

    Inputs for this step

    • Valid baseline

    Actions

    • Derive potential X drivers from process and data; confirm causes through analysis, comparison, or experiment.

    Output

    Confirmed drivers

    Derive potential X drivers from process and data; confirm causes through analysis, comparison, or experiment.

    Quality check

    Is every priority driver evidenced and distinguished from the symptom?

    Pitfall

    Fishbone ideas become root causes without testing. Set an evidence test and counter-hypothesis for each candidate.

    Timing: One to three weeks

  4. 4

    Improve

    Verified improvement

    Goal

    Verified improvement: Design solutions against confirmed Xs, assess risk, pilot, and verify against baseline.

    Inputs for this step

    • Confirmed drivers

    Actions

    • Design solutions against confirmed Xs, assess risk, pilot, and verify against baseline.

    Output

    Verified improvement

    Design solutions against confirmed Xs, assess risk, pilot, and verify against baseline.

    Quality check

    Does the pilot target confirmed drivers and improve outcomes within guardrails?

    Pitfall

    The solution rolls out fully before effect and risk are measured. Run a small pilot with prediction, guardrails, and baseline comparison.

    Timing: One to three weeks

  5. 5

    Control

    Control plan

    Goal

    Control plan: Set process standard, monitoring, reaction plan, owner, and handover; verify stability after implementation.

    Inputs for this step

    • Verified improvement

    Actions

    • Set process standard, monitoring, reaction plan, owner, and handover; verify stability after implementation.

    Output

    Control plan

    Set process standard, monitoring, reaction plan, owner, and handover; verify stability after implementation.

    Quality check

    Does the plan specify measure, limit, frequency, owner, and reaction?

    Pitfall

    A dashboard without a reaction plan is treated as control. Add a concrete reaction, owner, and review for every limit.

    Timing: Two to four weeks plus ongoing monitoring

05

Artifact

What comes out at the end

Sketch: what the artifact looks like

DMAIC · Six SigmaStabilize process problems sustainably through scope, measurement baseline, cause analysis, improvement, and control plan
DMAICThe visual shows DMAIC as a data-driven improvement flow with Define, Measure, Analyze, Improve, Control, and a traceable data and control path.Improve process performance measurably and keep it stableDMAIC guides a problem from clear definition through reliable measurement and root cause analysis into improvement and control.CharterBaselineRoot CausePilotControl Planphase gates instead of gut feeldata flow stays traceableDefineclarify problem, scope,and goalMeasuresecure baseline andmeasurement systemAnalyzetest causes with dataImprovetest and introducesolutionControlanchor control plan andmonitoring
Form

DMAIC project record with charter, validated baseline, confirmed causes, verified pilot, and handed-over control plan.

Versioning / ownership

Record date, owner, source state, and review date; preserve prior versions.

Tool alternatives
  • DMAIC charter and phase gates
  • Measurement and cause analysis
  • Pilot and control plan

dmaic-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

06

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

dmaic-beispiel.md

Concrete filled scenario, fictional example

Fictional teaching example: DMAIC · working structure

Project charter

Checkout p80 is 18 vs target 10 minutes; scope Saturday pickup Hamburg; sponsor Operations; goal ≤12 by 31 Mar.

Valid baseline

Arrival-to-handoff time; 240 cases over four Saturdays; timer agreement ±20 sec; p80 18 minutes.

Confirmed drivers

Slot clustering explains 46% of variation; inventory sync has no stable effect; regression and shift comparison recorded.

Verified improvement

Eight slots/hour on two Saturdays: p80 11.8; rejection 6%; no complaint increase.

Control plan

Weekly p80; warning >13, action >15; Ops owner; inspect slot profile after two warnings; 30/60-day review.

07

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

  1. Project charterThe charter already mandates a favourite solution.View in phase
  2. Valid baselineAnalysis starts from unvalidated dashboard values.View in phase
  3. Confirmed driversFishbone ideas become root causes without testing.View in phase
  4. Verified improvementThe solution rolls out fully before effect and risk are measured.View in phase
  5. Control planA dashboard without a reaction plan is treated as control.View in phase
08

Stop criteria

When to pause, resolve prerequisites, or choose another approach

Stop Define: Is the gap measurable, with process, customer, goal, and out-of-scope explicit?
Stop Measure: Are definition, measurement system, sample, and baseline trustworthy?
Stop Analyze: Is every priority driver evidenced and distinguished from the symptom?
Stop Improve: Does the pilot target confirmed drivers and improve outcomes within guardrails?
Stop Control: Does the plan specify measure, limit, frequency, owner, and reaction?

Method after Motorola Six Sigma. Curated with 1 sources.

Sources: DMAIC

Flow, timeboxes, and pitfalls are editorially curated practice recommendations based on the listed sources.

Where to go next?

Paper illustration for Standard Work Analysis.
Operations
Standard Work Analysis

Anchors the control plan as a documented, repeatable work standard.

Visual Management workspace showing the question, observations, and next decision.
Operations
Visual Management

Makes the agreed control plan visible in the work area.

View in playbookSystematically Solve a Recurring Operations ProblemMove from direct on-site observation through a structured DMAIC treatment to a new, anchored standard.

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

Go to profileMore methods