Project Charter Template Mckinsey

Standard Operating Procedure: McKinsey-Style Project Charter Formulation

Document ID: TR-SOP-PM-042
Effective Date: 2023-10-27
Version: 1.0.0
Review Cadence: Annual

1. Executive Summary & Purpose

This SOP defines the institutional framework for drafting a Project Charter using the McKinsey "Structured Problem Solving" methodology. The purpose is to move from ambiguity to high-leverage action by aligning stakeholders on scope, hypothesis, and resource allocation before project initiation.

2. Scope & Prerequisites

• Scope: Applicable to all enterprise-level initiatives requiring cross-functional resource commitment.
• Required Tools: Template Registry Project Charter (v4.2), LucidChart/Miro for MECE (Mutually Exclusive, Collectively Exhaustive) mapping, MS Excel for resource load forecasting.
• Prerequisites: Completed Stakeholder Interest Assessment; access to the Project Repository; documented Initial Hypothesis.

3. Roles & Responsibilities (RACI)

4. Step-by-Step Procedure

Phase I: The "So What?" Definition

• Define the core problem statement (must be a specific, measurable business pain).
• Draft the "North Star" goal: A single, quantifiable outcome.
• Validate alignment with corporate strategy using the McKinsey 7S Framework.

Phase II: Hypothesis Formulation

• List 3-5 working hypotheses to solve the core problem.
• Map dependencies for each hypothesis.
• Conduct a pre-mortem: Identify the "Why might this fail?" scenarios.

Phase III: Resource & Workstream Mapping

• Define the Work Breakdown Structure (WBS) in 3 tiers.
• Allocate headcount based on Capacity vs. Need (never exceed 80% utilization per SME).
• Set definitive milestones with binary (Success/Fail) exit criteria.

Phase IV: Governance & Review

• Establish communication cadence (e.g., weekly status, monthly steer-co).
• Define escalation path for budget or scope variance >10%.
• Obtain formal digital signature from the Executive Sponsor.

5. Quality Assurance & Pro-Tips

• The MECE Test: Every workstream must be Mutually Exclusive and Collectively Exhaustive. If you find overlap, your scope is ill-defined.
• The "Elevator Test": If you cannot articulate the project's purpose and expected ROI in under 60 seconds to a C-suite executive, your charter is too dense.
• Metric Thresholds:
  • Scope Creep: If >5% change, trigger an automatic re-baseline.
  • Stakeholder Sentiment: Minimum 4/5 satisfaction on charter clarity during the Kick-off review.
• Pitfall: Avoid "Solution Searching." Ensure the problem is fully diagnosed before assigning a specific technology or methodology.

6. Frequently Asked Questions (FAQ)

Q: What if the executive sponsor disagrees with the proposed timeline?
A: Do not compromise on the timeline if it sacrifices quality. Present a "Triple Constraint" analysis showing the direct correlation between accelerated timelines and increased risk/cost.

Q: How do we handle "Scope Creep" from high-ranking stakeholders?
A: Refer to the "Zero-Sum Resource Policy." If a new requirement is added, an existing requirement of equal scope must be removed or deferred to a subsequent phase.

Q: How granular should the workstreams be in the charter?
A: Keep to the Level 2 hierarchy. Level 3 and below belong in the Project Plan/Backlog, not the Charter.

Authorized by: Julian Vance, Chief Architect, Template Registry