Six Sigma DMAIC Template
The DMAIC template helps Six Sigma practitioners apply the DMAIC methodology (Define, Measure, Analyze, Improve, Control) as a root cause analysis for process improvement. Start by defining the project goals and listing the deliverables for the customer. Next, measure the current process performance to quantify the problem. Analyze until the root cause has been identified, and improve the design, system and/or procedure with evaluated and re-evaluated solutions. Finally, specify the monitoring and control system in place and complete the DMAIC with your digital signature.
Use this template with flowdit
- Customize this template or build your own
- Complete inspections using the mobile app
- Get reports and analyze your data
Start inspecting smarter — free for one user.
How to Use This Checklist
- **Define.** State the project objectives and the problem the DMAIC project will solve, and describe the intended improvement outcome. Define the scope, including the process's start and end points, and identify the customers affected. List the deliverables to be supplied to the customer with the expected acceptance criteria for each. Map the process and mark the steps contributing to the problem. Document the team members and their roles, confirm the project charter has been reviewed and approved by the project sponsor, and record the target completion date.
- **Measure.** Measure and quantify the current performance of the process. Define the metrics used to quantify the problem, with the unit of measure and the data source for each. Validate the measurement system before the data is collected, then record the current process capability or baseline defect rate. Set out the data collection plan: what data will be collected, by whom, how often and over what period.
- **Analyze.** Analyse the baseline data and examine the variation in the process. List the potential root causes of the problem and verify them against the data rather than accepting them on assumption. Identify and state the principal root cause. Record the analysis tools used to reach the conclusion and document the evidence linking the principal root cause to the measured problem.
- **Improve.** List the candidate solutions that address the principal root cause. Evaluate each against criteria such as cost, effort, risk and expected benefit, then state the solution selected for implementation and why it was chosen over the others. Confirm the selected solution covers the design, the system and/or the procedure as applicable, and identify the change requests needed to implement it. Measure the performance of the process after the improvement and compare it with the baseline. Re-evaluate the solution and confirm it has resolved the principal root cause without introducing a new problem.
- **Control.** Describe the monitoring and control system that will keep the improved process in place. Specify the control chart or control method to be used, and name the person or role responsible for monitoring after handover. Define the frequency of monitoring and the action to be taken when the process drifts out of control. Update the procedure or work instruction, standardise and communicate the improvements to the people who run the process, and record the lessons learned and any remaining opportunities for improvement.
Start inspecting smarter — free for one user.
Why DMAIC matters
DMAIC is a structured problem-solving method. It is what stops an improvement project from becoming a series of untested opinions: each phase produces evidence that the next phase relies on. Its value comes from the sequence and from the discipline of verification at each step.
What it involves
The project runs through five phases. - **Define** establishes the problem, the scope, the customer and the deliverables, and gets the charter approved. - **Measure** quantifies the current performance of the process so the problem has a size. - **Analyze** identifies the principal root cause and the evidence that links it to the measured problem. - **Improve** selects, implements and re-evaluates a solution that addresses that root cause. - **Control** puts the monitoring, ownership and standardised procedure in place so the improvement holds. Each phase has exit criteria: an approved charter before measuring, a validated measurement system before analysing, a stated root cause supported by data before improving, and a re-evaluated solution before controlling.
What a good DMAIC project covers
A well-run project keeps a clear thread from the problem statement to the control plan. That means the customer's acceptance criteria are named, the process is mapped with the problem steps marked, the data collection plan says who collects what and how often, the analysis tools are recorded, the evidence linking cause to effect is documented, the chosen solution is justified against alternatives, and the control method has an owner and a defined response to drift. Avoid shortcuts where a root cause is assumed rather than verified, or where the improvement is declared complete without re-measuring against the baseline.
Who it is for and how to run it
This template is for the practitioners running an improvement project in a manufacturing, service or transactional process, and can be worked through in phases by a team or used by an individual to structure and document the project. It is a practical record of the work, and it can also be used as a training scaffold. The project sponsor, the team members and the responsible roles in the control plan need to be named. Where the process is covered by a regulation or standard in your sector, the control phase is where you record that the improved procedure complies, and the signature, real start date and completion fields close out the project as a dated record.
Frequently Asked Questions
Ready to simplify inspections and get your team moving faster?
Start free today and turn inspections into a clear, consistent digital workflow. Prefer a guided walkthrough? Book a demo and see how flowdit can fit your team.