5.1 The Project Charter & Problem Statements

The Project Charter & Problem Statements

Quick Answer: The project charter is a formal document and living contract that establishes executive sponsorship, authorizes resource allocation, and aligns project goals with organizational strategy. A comprehensive charter contains six core elements: Business Case, Problem Statement, Goal Statement, Project Scope, Milestones, and Team Roles. A critical formulation rule is that problem statements must describe the observable defect, baseline performance, and quantified gap without assuming root causes or prescribing solutions. Independent CSSYB study guide by OpenExamPrep.

Purpose and Strategic Role of the Project Charter

A Six Sigma initiative cannot succeed without formal executive backing, access to process data, and dedicated team time. The project charter fulfills this need by serving as the foundational governance agreement of the Define phase, establishing a binding contract between the project team, the Project Champion, and the Process Owner.

The charter accomplishes three vital objectives:

1. Resource Authorization: Grants the project leader (Black or Green Belt) and team members (including Yellow Belts) explicit authority to expend organizational resources—such as work hours, capital, equipment time, and statistical software.
2. Strategic Alignment: Links localized process defects directly to high-level organizational goals, such as operating cost reduction, regulatory compliance, customer retention, or margin growth.
3. Operational Consensus: Establishes shared boundaries, preventing misunderstandings regarding what the project will and will not deliver.

Although formally signed at the conclusion of the Define phase, the charter functions as a living document. As the team collects empirical data during Measure and Analyze, newly uncovered facts may warrant refining parameters—such as tightening scope or adjusting milestone targets—subject to formal review and re-approval by the Project Champion.

The Six Core Elements of a Robust Charter

A comprehensive Six Sigma charter integrates six interconnected components:

1. Business Case: Answers the executive question, "Why does this project matter now?" It details the strategic and financial justification for the initiative, highlighting the Cost of Poor Quality (COPQ), regulatory mandates, or customer satisfaction trends. It establishes operational urgency by framing the business risks of inaction.
2. Problem Statement: Provides an objective, data-driven description of the operational pain point. It articulates four specific dimensions:
   • What: The specific defect, error, or metric variance observed.
   • Where: The physical facility, production line, customer segment, or software application.
   • When: The timeframe, shift pattern, or duration of observation.
   • Magnitude / Baseline Gap: Baseline performance compared against the expected standard, including financial consequences.

   The Cardinal Rule: A problem statement must never state suspected root causes, assign personal blame, or prescribe solutions. Prematurely speculating on causes biases data collection and circumvents DMAIC rigor.

3. Goal Statement: Adheres to the SMART framework (Specific, Measurable, Achievable, Relevant, Time-bound). It specifies the baseline metric ($Y_0$), the quantified target metric ($Y_{\text{target}}$), and the target completion deadline (e.g., "Reduce invoice processing errors from 8.4% to under 2.0% by December 15, 2026, generating $65,000 in annual COPQ savings").
4. Project Scope: Demarcates project boundaries by explicitly documenting both in-scope and out-of-scope activities, processes, and geographic sites. Defining clear limits prevents scope creep—the uncontrolled expansion of project boundaries without corresponding increases in time or budget.
5. Milestones / Project Plan: Outlines target completion deadlines for the five DMAIC phase tollgates (Define, Measure, Analyze, Improve, and Control), establishing clear accountability.
6. Team Roles & Resources: Identifies key participants and responsibilities, including the Champion, Process Owner, Black/Green Belt project leader, Yellow Belt frontline contributors, and financial analysts who audit cost savings.

BoK checkpoint: The CSSYB Body of Knowledge names four charter components you must be able to describe: problem statement, project scope, baseline data, and project goal. Baseline data is the measured current performance (for example, an 8.4% invoice error rate over the last six months). It supplies the magnitude in the problem statement and the starting point ($Y_0$) of the goal statement, so a charter without baseline data cannot show how much improvement the goal requires.

Formulating Rigorous Problem Statements

Effective problem statements isolate observable symptoms from unverified assumptions. The table below illustrates common formulation errors and their data-driven corrections:

Scope Management & Charter Governance

Uncontrolled project expansion, or scope creep, represents a primary failure mode for continuous improvement projects. If stakeholders attempt to append additional processes or software systems to an active initiative, the project leader must prepare a formal charter amendment. This amendment evaluates the proposed addition against project timelines, budget, and Yellow Belt resource availability, requiring formal sign-off from the Project Champion before any operational boundaries are altered.