- DMAIC is a five-step method for fixing a process that already exists: Define, Measure, Analyze, Improve and Control. It is the problem-solving core of Lean Six Sigma.
- Each step asks something different of the team. Define asks for agreement, Measure for patience, Analyze for honesty, Improve for restraint and Control for ownership.
- The method's real discipline is the order. No one changes the process until the data has shown what is causing the problem.
- East African teams already use the simple tools. A pilot study of practitioners in Kenya, Uganda, Tanzania and Rwanda found process maps, cause-and-effect diagrams and Pareto charts did most of the work.
- Most projects fail at the ends, not the middle: a vague problem statement at the start or no one owning the result at the finish.
Most process problems are no secret to the people who live with them. The loan that takes three weeks to approve, the order that ships with the wrong item, the patient file that cannot be found: every team can name its version, and most can name a fix. What they rarely have is proof that the fix addresses the cause. DMAIC (Define, Measure, Analyze, Improve, Control) is the method Lean Six Sigma uses to get that proof before anything changes.
Since 2019, the requests for process improvement that reach us have tended to arrive with the solution already chosen: a new system, an extra approval step, more staff. Sometimes the chosen solution is right. DMAIC is how a team finds out which time it is, and the five steps ask more of the people involved than of the statistics.
This article explains what DMAIC is, how Lean Six Sigma is used in East Africa, what each step asks of your team, a worked example from a published case and how to run a first project.
What DMAIC Is
DMAIC is a structured way to improve a process that exists but does not meet the standard customers or managers expect. The American Society for Quality describes it as five phases, each building on the one before, with the goal of a long-term fix rather than a quick patch. It is not for designing a new process from scratch; it is for the one you already run.
DMAIC sits inside Lean Six Sigma, which joins two traditions:
- Lean comes from the Toyota Production System, which aims to eliminate waste and shorten lead times. Its question is: which steps add nothing the customer would pay for?
- Six Sigma is about variation. Its question is: why does the same process give a good result on Monday and a bad one on Thursday?
Most real problems involve both, which is why the two are now usually taught together, and why DMAIC uses tools from each.
The American Society for Quality sets the numerical goal of a process at the six sigma level as 3.4 defects per million opportunities. Few service processes in any country come close, and they do not need to. The figure matters less as a target than as a reminder that quality is counted, not felt.
How Lean Six Sigma Is Used in East Africa
Lean Six Sigma is not new in East Africa. A pilot study published in The TQM Journal surveyed people from Kenya, Uganda, Tanzania and Rwanda who had attended Yellow, Green or Black Belt courses at the Kenya Institute of Management in Nairobi. They came from textiles, banking and finance, agriculture, health, utilities and manufacturing. Most had completed between one and five projects, and most of those who could estimate the savings put them between KSh 1 million and KSh 50 million a year.
The tools they found most useful were not the advanced statistics. Process mapping, brainstorming, cause-and-effect analysis, Pareto analysis and control charts did most of the work. Design of experiments and regression, the tools that make Six Sigma sound intimidating, were used by fewer than half.
That finding matters for Kenyan managers deciding whether DMAIC is for them. The method's value lies less in its statistics than in its order: define before measuring, measure before blaming, prove the cause before changing anything. In many Kenyan organizations, where seniority often settles what the problem is, a method that makes the data speak first is a real change in how decisions are made.
In the East African pilot, only 11 of the 23 respondents said their organization had a Lean Six Sigma Champion, the senior sponsor who clears obstacles for a project. They named competing projects, a lack of tangible results and changes in management as the main barriers. Each of those is a leadership problem, not a statistical one.
Source: Douglas, Douglas and Ochieng, Lean Six Sigma Implementation in East Africa, The TQM Journal (2015)
The Japan International Cooperation Agency describes the Africa Kaizen Initiative as a 10-year program it launched in 2017 with the African Union Development Agency, and Kenya hosted its annual conference that year. Kaizen, the habit of small continuous improvement that Lean depends on, already has public backing across the continent; few firms need to start from zero.
The 5 DMAIC Steps and What Each Asks of Your Team
Every step has a technical output, and every step asks the team for a particular kind of discipline. The second is where projects usually succeed or fail.
1. Define
The question: what exactly is the problem, for whom, and what would fixed look like? The team writes a project charter: a one-page statement of the problem, the goal, the scope, the customer and the measure of success. ASQ's guidance adds a stakeholder analysis and the voice of the customer, meaning what customers say satisfies or frustrates them.
What it asks of the team: agreement. A problem statement such as "loan approvals are slow" is not a definition. "Business loan applications under KSh 5 million take a median of 19 working days from complete file to decision, against a promise of 7" is one. Getting a sales head, a credit head and an operations head to sign the same sentence is often the hardest work in the project.
2. Measure
The question: how does the process actually perform today? The team maps the real process, not the one in the procedures manual, checks that its measurements can be trusted and establishes a baseline.
What it asks of the team: patience. Measuring feels like delay when everyone already knows the answer. But a baseline is the only thing that will later prove the change worked, and the process map regularly surprises the people who run the process every day.
3. Analyze
The question: what is causing the gap? The team identifies the inputs that drive poor performance, using root cause analysis, cause-and-effect diagrams and Pareto charts, which rank causes by how often they occur.
What it asks of the team: honesty. The root cause is often a decision someone in the room made: an approval step added after one bad loan, a form designed by a department that never uses it. A team that cannot name its own contribution will find causes only in other departments.
4. Improve
The question: what change removes the cause, and does it work? The team generates and tests solutions, often through a short pilot or a kaizen event: a few intense days in which the people who do the work redesign a narrow part of it.
What it asks of the team: restraint. The solution has to address the cause found in Analyze, not the one people preferred before the project began. Pilot it on a small scale and measure it against the baseline before rolling it out.
5. Control
The question: how will the gain last after the project team disbands? The team writes a control plan, updates standard procedures, and sets up ongoing measurement with a named person who reacts when the numbers drift. Mistake-proofing, which makes errors impossible or immediately visible, belongs here.
What it asks of the team: ownership. A process improvement with no owner reverts as soon as the project team moves on.
| Step | Question it answers | Main output | Common tools |
|---|---|---|---|
| Define | What is the problem, and for whom? | Project charter with a measurable goal | Voice of the customer, stakeholder analysis |
| Measure | How does the process perform today? | Process map and trusted baseline | Process map, Pareto chart |
| Analyze | What causes the gap? | Verified root causes | Cause-and-effect diagram, root cause analysis |
| Improve | What change removes the cause? | Tested solution with results against baseline | Pilot, kaizen event |
| Control | How will the gain last? | Control plan with a named owner | Control chart, mistake-proofing |
Is there a process your team has tried to fix more than once?
Our Strategic Planning program includes operations excellence and Lean Six Sigma training built around the DMAIC framework, for the managers and process owners closest to daily execution. Participants who complete the Lean Six Sigma module receive a certificate. Request a proposal.
A Worked DMAIC Example
Published DMAIC cases from African service businesses are rare, which makes one from South Africa worth reading closely. Researchers from the University of South Africa and Tshwane University of Technology applied DMAIC at a bookkeeping and tax consulting firm in Gauteng with 27 staff, publishing the results in the South African Journal of Industrial Engineering in 2022. Here is how the five steps played out:
- Define. Clients were unhappy with delays. The team set the problem as reducing delays and client waiting time across the firm's work, from registering companies to monthly tax submissions, and mapped the activities involved.
- Measure. A time study measured each activity, separating time that added value for the client from time that did not, and time the systems were working from time they were down.
- Analyze. Consultants, managers and clients built a cause-and-effect diagram. It traced the delays to six causes, including unreliable internet, too few computers, a poor work layout and too few people to monitor the work.
- Improve. Over three months the firm hired three more staff, added three computers and extra internet capacity, and reorganized the work.
- Control. Control charts were set up to track value-added time and flag drift.
Time Per Process Cycle Before and After a DMAIC Project, Bookkeeping Firm in Gauteng, South Africa
Seconds, across the firm's mapped activities, before and three months after the changes. Source: Magodi, Daniyan and Mpofu, South African Journal of Industrial Engineering, 2022
Non-value-added time fell from 1,139 to 452 seconds, down 60%. Downtime fell from 900 to 470 seconds, down 48%.
Bars are totals in seconds across the activities the study timed, not the time for any single client request.
Non-value-added time, the waiting and rework clients do not benefit from, fell by 60%, from 1,139 to 452 seconds across the mapped activities. Downtime fell by 48%, from 900 to 470 seconds.
Two things in this case are worth noticing. First, the fix was unglamorous: three people, three computers and a better internet connection. DMAIC does not promise a clever solution. Sometimes the data says you are short of three people, and the value of the method is that you can now prove it to whoever signs the budget. Second, the authors note the case covers one firm, and its control charts tracked a projected period rather than years of results. The study shows what the first four steps can deliver in three months; whether the gains lasted depends on the step that is easiest to skip.
How to Run Your First DMAIC Project
A first project should be chosen to succeed, because its main job is to show the organization what the method can do.
1. Pick a process with a visible cost
Choose a process where customers or staff already complain, the cost of the problem can be counted, and the whole process sits within a few departments. Avoid anything that depends on a regulator or a system replacement already under way.
2. Name a sponsor with authority
The sponsor, often called the Champion, is the senior manager who approves the charter, clears obstacles between departments and signs off the solution. Without one, the project stalls the first time it needs a decision from someone outside the team.
3. Staff the team with the people who do the work
Include the people who handle the process daily, not only their managers. They know where the workarounds are, and they will be the ones keeping the improvement in place.
4. Agree the measure before the solution
Write down how success will be measured and take the baseline before anyone proposes a fix. Once a solution is on the table, every measurement starts to look like evidence for it.
5. Hand over to a named process owner
Plan the Control step from the start. Name the person who will own the process afterward, the measure they will watch and what they will do when it drifts.
Three Common DMAIC Mistakes
Starting at Improve
The most common failure is a project that begins with the solution and runs DMAIC backwards to justify it. The charter is written around the new system already bought. Measurement and analysis become paperwork. The cure is the sponsor's job: refuse to discuss solutions until the Analyze step has named a verified cause.
Measuring what is easy to count
Teams measure what their systems already record, which is rarely what the customer feels. A bank may track the time from file submission to credit committee because it is in the system, while the customer's wait begins with the first visit to the branch. Measure the process as the customer experiences it, even if that means collecting data by hand for a few weeks.
Skipping Control
When the results look good, the team disbands and the process drifts back. Changes in management, one of the barriers named in the East African pilot study, make it worse: the new manager inherits a process with no record of why it works the way it does. Write the control plan, name the owner and review the measure monthly for at least a year.
Frequently Asked Questions
What is the DMAIC process?
DMAIC is a five-step method for improving a process that already exists but does not meet the standard expected of it. The steps are Define, Measure, Analyze, Improve and Control. It is the core problem-solving approach of Six Sigma and Lean Six Sigma, and its main discipline is the order: prove the cause of a problem before changing the process.
What does each DMAIC step involve?
Define sets out the problem, the customer and a measurable goal in a project charter. Measure maps the real process and establishes a trusted baseline. Analyze identifies and verifies the root causes. Improve tests a change that removes those causes against the baseline. Control keeps the gain through a control plan, standard procedures and a named process owner.
What is the difference between Lean and Six Sigma?
Lean, which comes from the Toyota Production System, focuses on removing waste: steps that add nothing the customer would pay for. Six Sigma focuses on reducing variation, so a process gives the same result every time. Lean Six Sigma combines the two, and DMAIC uses tools from both.
Is Lean Six Sigma used in Kenya and East Africa?
Yes. A pilot study in The TQM Journal surveyed practitioners from Kenya, Uganda, Tanzania and Rwanda trained at the Kenya Institute of Management, working in banking, manufacturing, health, agriculture, utilities and textiles. They found the simpler tools, such as process mapping, cause-and-effect diagrams and Pareto charts, the most useful.
How do you choose a first DMAIC project?
Pick a process where customers or staff already complain, where the cost of the problem can be counted and where the whole process sits within a few departments. Name a senior sponsor, staff the team with people who do the work, agree the measure before discussing solutions and name the person who will own the process afterward.
Why do DMAIC projects fail?
Most fail at the ends rather than the middle. Some start with a solution already chosen and use the steps to justify it. Others measure what the system records rather than what the customer experiences. Many skip Control, so the process drifts back once the project team disbands or management changes.
Conclusion
DMAIC is less a statistical method than a rule about order: define, measure and prove the cause before changing anything. Teams that keep that order rarely need advanced statistics.
Think of the last process change your organization made to fix a recurring problem. Could anyone show you the baseline it was measured against, and is someone still watching the number today?
If the answer is no, our Strategic Planning program can train your managers and process owners in Lean Six Sigma and the DMAIC framework, working on a real process from your own organization. Request a proposal and we will start from the problem your team already knows best.
