DMAIC Template for Six Sigma Process Improvement

What the DMAIC methodology is

DMAIC is a structured problem-solving method used by Six Sigma practitioners to improve processes. The five phases — Define, Measure, Analyze, Improve, and Control — take you from a stated problem to a change that is monitored and held in place. It works as a root-cause analysis: rather than jumping to a fix, you define what you are trying to achieve, quantify the current state, find the cause, design and validate the improvement, and then hand over a system that keeps it stable. The approach is deliberately sequential. Each phase produces the evidence the next one depends on, so weak definition or measurement becomes visible before it turns into an unreliable improvement.

Why running DMAIC properly matters

Improvement work fails most often because the problem was never quantified or the cause was assumed rather than found. DMAIC forces both issues into the open. Measuring current process performance and benchmarking it gives you a baseline, so any improvement can be judged against something real. Analyzing value-adding and non-value-adding steps, sources of variation, and the critical inputs in relation to the output separates what genuinely drives the problem from what merely looks relevant. Control matters just as much. An improvement that is not monitored tends to erode, which is why the method ends by establishing a control system and handing responsibility to the process owner rather than leaving it with the project team.

What a good DMAIC record covers

A complete record follows the five phases and captures the reasoning in each one. - **Define.** The project goals, the deliverables to be produced for internal and external customers, the problem statement, and the performance targets. - **Measure.** A data collection plan to quantify the problem and benchmarking of the current process performance. - **Analyze.** Identification of value-adding and non-value-adding process steps, the sources of variation, a description of the few critical inputs relative to the output, and the resulting cause of the problem. - **Improve.** The possible solutions, whether the operating tolerances of the potential system are well defined, whether design of experiments were carried out, whether improvements were validated through pilot studies, and confirmation that solutions were reviewed and re-evaluated. - **Control.** The monitoring and control system, the introduction of statistical process control, the handover plan to the process owner, and a review of benefits, cost savings or avoidance, and profit growth. Alongside the technical content, the record captures who prepared it, where it applies, the date conducted, the signature, and the finished time.

Carrying out the work

1. Define the project goals and list the deliverables owed to the customer, both internal and external. 2. Write the problem statement and the performance targets so there is a clear standard to measure against. 3. Set out the data collection plan and benchmark the current performance of the process to quantify the problem. 4. Identify the value-adding and non-value-adding process steps, determine the sources of variation, and describe the critical inputs in relation to the output. 5. State the cause of the problem and set down the possible solutions. 6. Check whether the operating tolerances of the potential system are well defined. 7. Confirm whether design of experiments were carried out and whether improvements were validated through pilot studies. 8. Review and re-evaluate the possible solutions before committing to them. 9. Define the monitoring and control system, introduce statistical process control, and agree the handover plan to the process owner. 10. Review the benefits, cost savings or avoidance, and profit growth, then close the record with your signature and the finished time.

Frequently Asked Questions

DMAIC stands for Define, Measure, Analyze, Improve, and Control. It is the five-phase problem-solving methodology that Six Sigma practitioners use to drive process improvement, moving from a defined problem through measurement, root-cause analysis, solution design, and finally a monitoring and control system.

You should start by writing down the project goals, then list the deliverables that have to be produced for the customer, both internal and external. Benchmarking the current process performance helps you quantify the problem, and a data collection plan sets out how that measurement will actually be done.

These phases rely on data. You measure current process performance and benchmark it, analyze value-adding and non-value-adding process steps, determine sources of variation, and describe the few critical inputs in relation to the output. The outcome of the analysis is the cause of the problem, which you then act on.

You take the possible solutions and check them against the operating tolerances of the potential system, confirm whether design of experiments has been carried out, and validate improvements through pilot studies. Solutions that do not hold up are reviewed and re-evaluated rather than forced through.

Control is where you fix the monitoring and control system in place. That includes introducing statistical process control, agreeing a handover plan to the process owner, and reviewing the benefits, cost savings or avoidance, and profit growth that the improvement is expected to deliver.

You record the date the inspection was conducted, who prepared it, and the location. You close the record out with a signature and the time finished, alongside the real start and end dates of the inspection.

Written by

Arne Reis

Founder

Process optimizer with 25 years of expertise, focused on operational excellence in quality, maintenance, EHS, and commissioning. Emphasizes innovative solutions and top-quality standards.

View LinkedIn profile