Run a Lean Six Sigma DMAIC project on schedule with a Gantt chart — from Define through Control with kaizen events, SMED, SPC charts, and a 90-day post-implementation audit.
Lean Six Sigma DMAIC projects fail at two points more than any others: Define (the team doesn't frame the problem tightly enough and the project scope grows indefinitely) and Control (improvements are implemented and then quietly abandoned when attention moves elsewhere). Both failures are fundamentally project management failures — not methodology failures.
A Gantt chart for manufacturing process improvement keeps DMAIC on track. It makes the five-phase structure visible, assigns ownership at each phase, and ensures the Control phase actually controls — not just documents. This is the 3–6 month DMAIC project timeline that produces durable results.
DMAIC (Define → Measure → Analyze → Improve → Control) is the structured problem-solving methodology of Six Sigma. Each phase has a specific purpose and defined outputs (deliverables) that gate entry into the next phase.
The phases are not academic exercises — they're a discipline against the most common failure mode in manufacturing improvement: jumping to a solution before understanding the problem. The Gantt chart enforces the sequence and ensures each phase gets enough time to produce real output.
Typical DMAIC project duration:
Most DMAIC projects that run longer than 6 months are either out of scope or stalled in the Analyze or Improve phases. If your project is approaching week 24 without an implemented improvement, reassess scope.
Define is the phase where the team establishes what problem it's solving, who's involved, and what success looks like. Rushing it produces scope creep and unfocused analysis.
Problem statement:
A good problem statement describes the gap between current performance and desired performance in specific, measurable terms. It does not include causes or solutions — those are for Analyze and Improve.
Format: "[Process or product] is producing [specific defect or inefficiency] at [current rate], compared to a target of [desired rate], resulting in [business impact: cost, customer impact, throughput loss]."
Example: "The assembly line for Product X has an average cycle time of 4.2 minutes per unit, against a target of 3.0 minutes, resulting in a daily throughput shortfall of 85 units and $12,400 in daily opportunity cost."
Project charter:
The project charter is the formal contract between the project team and leadership. It includes:
The project sponsor (a plant manager or VP of operations) reviews and signs off on the charter before Measure begins. This is the gate into Phase 2.
Team formation:
DMAIC teams are cross-functional by design. A process improvement on an assembly line typically includes:
Operators must be included. The team without operators produces solutions that operators reject or work around.
Deliverable by Week 3: Signed project charter, team roster, phase timeline approved by sponsor.
Measure establishes the baseline — the current state of the process, quantified. You cannot improve what you cannot measure, and you cannot measure what you haven't defined.
Baseline data collection:
Determine what data to collect and how long to collect it. For a cycle time problem, you need actual cycle time data — not target cycle time, not engineering standard, but observed measurements from the real process.
Data collection considerations:
Key manufacturing metrics to baseline:
OEE (Overall Equipment Effectiveness):
OEE = Availability × Performance × Quality
Cycle time:
Defect rate:
Process capability:
Deliverable by Week 8: Baseline data set, process capability analysis, MSA results, current state value stream map.
Analyze is where the team identifies root causes of the performance gap. The temptation is to jump to solutions — particularly if operators and engineers already have strong intuitions about causes. Resist it. Intuitions are hypotheses; Analyze proves or disproves them with data.
Root cause analysis tools:
Fishbone diagram (Ishikawa diagram):
5-Why analysis:
Correlation and regression analysis:
Hypothesis testing:
Deliverable by Week 13: Root cause analysis complete, verified root causes identified and ranked by impact, process variable matrix (input variables and their relationship to output measures).
Improve is where solutions are developed, piloted, and implemented. The Define-phase project charter scope governs what improvements are in scope.
Solution development:
Generate multiple solution options before selecting. Common manufacturing improvement approaches:
Waste elimination (Lean):
Changeover reduction (SMED — Single-Minute Exchange of Die):
SMED is one of the most powerful tools in the Lean toolkit. The goal is to reduce the time required to switch a machine or production line from one product to another.
SMED implementation steps:
Example result: changeover that takes 3.5 hours reduced to 42 minutes by converting 80% of internal steps to external and standardizing remaining internal steps.
Kaizen event:
A kaizen event is an intensive 3–5 day improvement workshop that brings the full team together to implement changes immediately — not to plan changes for later implementation, but to make them right now.
Kaizen event structure:
A well-run kaizen event produces a measurable improvement by the end of the week. Plan the kaizen event as a milestone on your Gantt chart, with pre-work (materials preparation, management briefing) and post-work (standard work documentation, control chart setup) as flanking tasks.
Pilot line trial:
For significant equipment or process changes, run a pilot on one line or one shift before full deployment. Collect data during the pilot period (typically 2–4 weeks) to validate improvement performance before scaling.
Deliverable by Week 20: Pilot data confirming improvement vs. baseline, signed-off implementation plan for full deployment, control plan draft.
Control is the phase that most improvement projects shortchange — and the phase where improvement gains are most often lost. Implementation is not control. Control means the improved performance is sustained after the project team moves on.
Standard work documentation:
Every improved process must have updated standard work documentation:
If the process isn't documented, the next operator who trains will relearn the old way.
SPC chart setup (Statistical Process Control):
Control charts monitor the process in real time and signal when variation indicates the process may be drifting out of control — before defects are produced.
For each key output measure:
Operator training:
Train all operators on the improved process before full deployment. Training on standard work — not just "here's what's different" but hands-on practice of the new sequence — is required for adoption.
90-day post-implementation audit:
Schedule the audit at go-live. At 90 days after implementation:
The 90-day audit is the project's final deliverable — the proof that the improvement is real and lasting. If performance has regressed, the audit triggers corrective action.
Deliverable by Week 24: Standard work documented and posted, SPC charts operational, operator training complete, 90-day audit scheduled.
| Phase | Weeks | Key Deliverable |
|---|---|---|
| Define: charter, team, scope | 1–3 | Signed project charter |
| Measure: baseline data, MSA, OEE | 3–8 | Baseline performance data confirmed |
| Analyze: RCA, fishbone, 5-Why, hypothesis tests | 7–13 | Root causes verified with data |
| Improve: solution development, kaizen event, pilot | 12–20 | Pilot data confirming improvement |
| Control: standard work, SPC, operator training | 18–24 | Full deployment, charts live |
| 90-day post-implementation audit | Week 24 + 13 weeks | Sustained performance confirmed |
Indefinite Measure phase. Teams collect data indefinitely because they haven't set a collection window. The Gantt chart sets the window.
Analyze phase stalls in debate. Root cause analysis becomes opinion sharing without data analysis. The Gantt chart sets the analysis deadline and the deliverable (verified root causes, not candidate root causes).
Improve implementation never happens. The pilot validates the improvement, and then the plant goes back to normal operations before full deployment is complete. The Gantt chart schedules the full deployment immediately after the pilot.
Control isn't enforced. SPC charts are set up and then not monitored. The 90-day audit on the Gantt chart is the mechanism that checks.
The Gantt chart is not a substitute for DMAIC discipline — it's the structure that keeps the discipline intact through six months of competing operational priorities.
Build your manufacturing process improvement Gantt chart free at gantt-chart.io