DMAIC
Phase-by-phase guides to the DMAIC method: charters, baselines, root cause verification, pilots, control plans, tollgate reviews, and the final report.
DMAIC is the five-phase method that Six Sigma uses to fix a process problem when the cause is not known. The letters stand for Define, Measure, Analyze, Improve, and Control. Each phase ends at a tollgate, where a sponsor decides whether the project moves forward, goes back for more work, or stops.
This hub collects the working guides for each phase and for the objects a DMAIC project produces: the charter, the primary metric and its baseline, the verified root causes, the piloted solution, the control plan, and the final report. Read the end-to-end walkthrough first if you are new to the method. Use the phase guides when you are inside a project and need the deliverable for the next gate.
What each phase must produce
Define. A charter with a quantified problem statement, a goal statement with a target and a date, a business case, and an explicit scope. The primary metric is named here, even if its baseline is not yet measured. The Define tollgate asks one question: is this a problem worth a project, and is this the right team to solve it?
Measure. A baseline for the primary metric that a skeptic would accept. That means a stated sample period, a named data source, and a check that the measurement system itself is stable. Most failed projects skipped this phase and went straight to a solution.
Analyze. A short list of verified causes, not a long list of suspected ones. The team proves each cause with data before it is allowed into the Improve phase.
Improve. A solution tested on a pilot before it is rolled out. The pilot shows movement in the primary metric and no damage to the secondary metrics.
Control. A control plan, a monitoring plan, a response plan, and a named process owner who takes the process back. The project is not closed until the gain has held for an agreed period.
Where projects go wrong
The same failures repeat across industries. The problem statement contains a cause or a solution. The baseline is an estimate, not a measurement. Scope grows at every meeting because the charter was never marked final. Savings are claimed without a classification that finance recognizes. The control plan is written but never handed to anyone. The guides in this hub address each of these at the point in the method where it happens.
How SixGrid runs DMAIC
SixGrid ships DMAIC as one of five standard methodology templates. Applying it to a project creates the phases in order, from Idea through Define, Measure, Analyze, Improve, and Control to Close, with tollgate milestones marked in each phase. The Charter tab holds the problem statement, goal statement, business case, and the primary metric with its baseline, current value, and target. The Financials tab classifies each benefit as hard or soft and by type, so the numbers survive a finance review. The Report tab produces the final report as a PDF from the charter, team, metrics, and financials already on the project. Owners and Admins can clone the standard DMAIC template and adjust it to their own tollgate standard.
Start with the end-to-end walkthrough below, then work through the phase guides in order.
Articles
2 articlesThe Six Sigma Project Charter, Field by Field
A blank template tells you the field names, not what a strong entry looks like. The charter field by field: quantified problem statement, SMART goal, baseline and target, explicit scope, and the draft-to-final lifecycle that makes it a contract.
How to Run a DMAIC Project End to End
A complete walkthrough of the DMAIC method: qualifying the project, chartering the problem, earning a defensible baseline, verifying causes, piloting improvements, and locking in the gain with controls and tollgate reviews at every phase.