Project Charter

Project mandate: problem statement and measurable goals

Overview

The project charter is the founding document of a Six Sigma project. It describes briefly and traceably why the project is needed, what it should achieve, who is involved, and within which boundaries the work happens. It is the first tool of the Define phase and is used as a reference in tollgate reviews.

Problem statement: Briefly describes the current problem with facts: what is happening, where, when, how often, and with what impact? Deliberately without causes and without solutions — those come later in Analyze and Improve.

Project goals: What should be achieved at the end? Each goal gets a row with description, target date, metric, and target value. "Reduce scrap from 4.2 % to 1.5 % by Dec 31" is a good goal; "improve quality" is not.

GAL (goal achievement level): How far has the goal been reached? 0 = not started, 100 = fully achieved. Keep the value up to date during the project — that way the charter always shows the current state.

Scope: What is part of the project and what is not? Record this in the problem statement. A clear boundary prevents scope creep — e.g. "Only production line 3, not final assembly".

Org chart (team and roles): Sponsor, project leader (Black/Green Belt), core team. Clearly documented roles avoid responsibility gaps later. The RACI matrix covers responsibilities in detail, the stakeholder analysis covers interests and influence.

Approach

  • Write the problem statement in 2–4 sentences — with facts, no speculation.
  • In the problem statement, also record what is NOT part of the project.
  • Create goals, each with metric, target value, and target date.
  • Add team and roles in the org chart, at minimum sponsor and project leader.
  • Keep the GAL of each goal up to date as the project progresses.
  • Align the charter with the sponsor and get sign-off — it is the basis for everything that follows.

Pitfalls

Solution in the problem statement: Sentences like "We need a new machine" are not problem statements — they jump to a solution. While writing, ask: does the sentence describe the symptom or the answer?

Immeasurable goals: "Increase efficiency", "motivate employees" are not goals. Every goal needs a number, a unit, and a date — otherwise it cannot be verified at the end of the project.

Scope too large: Six Sigma projects should typically finish in 3–6 months. Wanting to "optimize the entire plant process" leads to failure. Cut the project small and refine later.

No sponsor commitment: Without an active sponsor (resources, escalation path, political backing), projects stall at the latest in Improve. The sponsor in the org chart is not symbolic — the sponsor must be informed and engaged.

Charter is never updated: During the project, goals, scope, and participants change. The charter should be a living document — record changes with a date instead of preserving an outdated state.

Examples

This module ships with the following example datasets — load any of them in the app with a single click.

Available in the following cycles

  • DMAIC: Define
  • DMADV: Define
  • 8D: D2 — Describe the Problem