DMAIC explained: a step-by-step way to fix recurring problems
Written by LitCareer · 13 Oct 2026 · 2 min read
Define, Measure, Analyse, Improve, Control, with the key question and tools for each phase.
Why DMAIC works
Many teams jump straight to solutions and the problem comes back. DMAIC forces you to understand the problem with data before fixing it, and to lock in the gains afterwards.
Define: what exactly is the problem?
- Write a clear problem statement with numbers: "Customer complaints about late deliveries rose from 4% to 11% of orders in Q2."
- Set the goal, scope, team and timeline in a project charter.
- Identify the customer and what they consider a defect.
Measure: how bad is it now?
- Map the process step by step.
- Decide what to measure and how, and check that the measurement is reliable.
- Collect baseline data so you can prove improvement later.
Analyse: what is causing it?
- Brainstorm possible causes with a fishbone diagram.
- Use 5 Whys, Pareto charts and data analysis to find the few causes that matter most.
- Verify root causes with data, not opinions.
Improve: what will fix it?
- Generate solutions that target the verified root causes.
- Test them on a small scale first.
- Compare results with the baseline.
Control: how do we keep it fixed?
- Update standard work instructions and training.
- Use control charts or dashboards to monitor the process.
- Hand over ownership to the process owner with a response plan if results slip.
A small project to practise
Pick a process you can observe, such as the time to process leave requests or defects in a lab experiment, and walk it through all five phases.
Your next steps
- Write problem statements with numbers and dates
- Collect baseline data before changing anything
- Verify root causes with data
- Hand over with standard work and monitoring
General guidance for learning, not professional, legal or financial advice. Want help for your own situation? Book 1:1 career help.


