Project Charter Initialization IHI Framework Standard Operating Procedure

Standard Operating Procedure: Project Charter Initialization (IHI Framework)

Document ID: SOP-TR-PMO-004
Effective Date: 2023-10-27
Version: 1.0.2
Review Cadence: Annual

1. Executive Summary & Purpose

This SOP dictates the methodology for developing a Project Charter utilizing the Institute for Healthcare Improvement (IHI) framework. The objective is to standardize project alignment, define measurable aims, and ensure governance transparency for quality improvement (QI) initiatives. Failure to adhere to these specifications results in project scope creep and loss of institutional strategic alignment.

2. Scope & Prerequisites

• Scope: Applicable to all clinical and administrative performance improvement projects under the Template Registry governance umbrella.
• Software Requirements: Template Registry Charter Portal, MS Office 365, or validated PDF editor.
• Prerequisites:
  • Defined problem statement.
  • Executive sponsor endorsement.
  • Baseline performance data (3-month look-back minimum).

3. Roles & Responsibilities (RACI)

4. Step-by-Step Procedure

Phase I: Charter Drafting

• Define the Global Aim: State the desired outcome as a SMART goal (Specific, Measurable, Achievable, Relevant, Time-bound).
• Identify the Problem Statement: Detail the gap between current state and desired performance using empirical data.
• Establish Boundaries: Define what is "In-Scope" and "Out-of-Scope" to prevent drift.

Phase II: Stakeholder Alignment

• Assemble the Team: Select members based on required cross-functional skill sets.
• Draft the SIPOC Diagram: Define Suppliers, Inputs, Process, Outputs, and Customers.
• Secure Sign-off: Obtain wet or digital signature from the Executive Sponsor.

Phase III: Integration

• Upload to Registry: Log the finalized Charter into the Template Registry database.
• Set KPI Triggers: Configure automated alerts for milestone dates.

5. Quality Assurance & Pro-Tips

Best Practices

• The "So What?" Test: If the problem statement doesn't impact patient outcomes or operational efficiency, discard it.
• Avoid "Weasel Words": Use precise language (e.g., instead of "improve," use "reduce wait times by 15%").

Common Pitfalls

• Under-defining Scope: Leads to "Scope Creep." Always document what the project will not address.
• Ignoring Baseline Data: Proceeding without verified data is a failure of governance.

Metric Thresholds

• Charter Acceptance: Must be completed within 14 business days of initial project conception.
• Review Cycle: All Charters must undergo a peer review audit for compliance every 90 days.

6. Frequently Asked Questions (FAQ)

Q: Can the Project Charter be modified after signing?
A: Yes, but only via a formal "Change Request" form (CR-001) submitted to the Project Steering Committee if scope changes exceed 10%.

Q: What if we lack baseline data for the problem statement?
A: The Charter must then include a "Phase 0: Data Collection" sub-project. A charter cannot be finalized without a confirmed quantitative baseline.

Q: How granular should the "In-Scope" section be?
A: It must be granular enough that an auditor can determine if a task performed by a team member is within the authorized project boundaries.

Authorized by: Julian Vance Chief Architect, Template Registry