DMAIC Project Charter

Launch a Six Sigma process-improvement project with a complete DMAIC charter. Capture the problem and goal statements, business case, scope, team, baseline-to-target metrics, milestones and risks that authorize the work.

Create DMAIC Charter →

What is a DMAIC Project Charter?

A DMAIC project charter is the founding document of a Six Sigma process-improvement project. It follows the Define-Measure-Analyze-Improve-Control framework and is completed in the Define phase to authorize the project and align the team before improvement work begins.

It is built for improving an existing process that underperforms in a measurable way. The charter pins down a specific problem statement, a quantified goal statement, and the business case that justifies the effort, then bounds the work with an explicit scope and identifies the team and sponsor.

Crucially, a DMAIC charter quantifies success. Its metrics section records baseline and target values, its milestones set the project timeline, and its risk section anticipates obstacles. Together these turn a good intention into an accountable, measurable project.

In plain terms: This is the classic Six Sigma charter for fixing a process that's broken in a measurable way. It nails down the problem, a numeric goal (from X to Y by when), what's in and out of scope, who's on the team, the metrics with baselines and targets, key milestones and the main risks.

Core Sections

Problem & Goal Statements

The problem states what underperforms, where and by how much. The goal states the measurable target, for example reduce lead time from 6.4 to 3.5 days by a date.

Business Case & Scope

The business case quantifies the value of solving it. Scope-in and scope-out lists bound the work and guard against creep.

Team, Metrics, Milestones, Risks

A named team and sponsor, metrics with baseline and target values, dated milestones, and ranked risks with mitigations.

Key Formulas

Problem → Goal: from <baseline> to <target> by <date>
Metrics: metric | baseline | target | unit
Scope: in-scope items and out-of-scope items
Milestones: charter approved → current-state map → pilot → close

What a Strong DMAIC Charter Looks Like

The goal statement carries the weight: it should read as a move from a baseline to a target by a date, with a secondary metric to guard against side effects (for example, cut lead time while sustaining order accuracy).

Milestones and risks make the charter operational. Dated milestones from charter approval through pilot to project close give the project a spine, and a ranked risk list with mitigations shows the obstacles have been thought through before they arrive.

Assumptions & Validation

Existing, Measurable Process

There is an existing process whose performance can be measured.

If violated: For designing a new process, use a DMADV charter instead.

Quantified Goal

The goal has a baseline, a target and a date.

If violated: Add the numbers; a goal without them cannot be verified.

Explicit Scope

In-scope and out-of-scope items are both listed.

If violated: Add the out-of-scope list to prevent creep.

Sponsor & Team

An accountable sponsor and defined roles exist.

If violated: Name the sponsor and assign roles.

⚠️ Check assumptions first

A DMAIC charter fails when the goal is not quantified or the scope is open-ended. Improve fulfillment is not a goal; reduce average lead time from 6.4 to 3.5 days by September 30 while sustaining 98% accuracy is. Always pair the primary target with a guardrail metric so improvement in one area does not quietly degrade another, and always include an out-of-scope list.

When NOT to Use DMAIC Project Charter

Designing Something New

To create a new process or product rather than improve an existing one, use a DMADV charter.

Quick Root-Cause Work

For a fast one-page effort, a Lean A3 charter is lighter and more visual.

Hypothesis Testing

For a designed study with variables and success criteria, use a Research charter.

Industry Applications

Cycle-Time Reduction

Charter a project to cut lead time or cycle time while protecting quality.

Defect Reduction

Frame a project to reduce a defect or error rate with a measurable target.

Cost & Yield

Authorize work to improve first-pass yield or reduce cost of poor quality.

SLA Improvement

Charter a project to raise the share of orders or cases meeting SLA.

Frequently Asked Questions

When should I use a DMAIC charter?

Use a DMAIC charter when you are improving an existing process that underperforms in a way you can measure, and the aim is to reduce defects, variation, cost or cycle time. It follows the Define-Measure-Analyze-Improve-Control framework and is the standard charter for Six Sigma improvement projects. If instead you are designing a new process or product, a DMADV charter is the correct choice.

What sections does a DMAIC charter contain?

A DMAIC charter typically contains a problem statement, a goal statement, a business case, scope-in and scope-out lists, a team and sponsor, a metrics table with baseline and target values, dated milestones, and a risk list with mitigations. Together these authorize the project, bound it, staff it, quantify its success, schedule it and anticipate its obstacles.

What makes a good goal statement?

A good DMAIC goal statement expresses a measurable move from a baseline to a target by a specific date, such as reducing average lead time from 6.4 days to 3.5 days by a given deadline. It is best paired with a guardrail metric, for example sustaining a minimum accuracy level, so that improvement in the primary metric does not come at the expense of another important outcome.

Why include a business case in the charter?

The business case quantifies the value of solving the problem, such as the annual cost avoided or revenue protected, which justifies the resources the project will consume and helps the sponsor prioritize it against competing work. Without a business case, a charter states what will be done but not why it is worth doing, which weakens the mandate to allocate people and time.

How detailed should the scope be?

The scope should be explicit on both sides. The in-scope list names the parts of the process the project will address, while the out-of-scope list names related areas it deliberately will not, such as supplier lead times or pricing systems. The out-of-scope list is especially important because it is the primary defense against scope creep once the project is underway.

How does the charter relate to the rest of DMAIC?

The charter is the key output of the Define phase, setting the problem, goal, scope and metrics. The Measure phase then baselines those metrics with valid data, Analyze investigates causes, Improve implements and verifies solutions, and Control sustains the gains. The charter's targets and metrics thread through all five phases, which is why getting it specific and measurable at the start matters so much.

Launch Your Six Sigma Improvement Project

Build a complete DMAIC charter with quantified goals and scope. Free during Beta.

Create DMAIC Charter →