9.1 Process 1: Identify the Programme

9.1 Process 1: Identify the Programme

[!NOTE] Core MSP Lifecycle Definition: In Managing Successful Programmes (MSP) 5th edition, Identify the Programme is the initial process within the programme lifecycle. Its core purpose is to establish whether a proposed transformational initiative is strategically desirable, viable, and feasible before significant time, capital, and operational resources are committed to detailed design and delivery.

Every organizational transformation begins with strategic ambition: responding to market disruption, modernizing obsolete digital infrastructure, complying with sweeping statutory regulations, or executing a corporate merger. However, committing millions of dollars and hundreds of personnel to a multi-year transformation without validating its core premise is a primary cause of organizational failure.

Process 1 acts as an essential strategic filter. Rather than rushing into detailed solution design or launching constituent projects, MSP mandates a fast, cost-effective initial investigation to answer a foundational question: Does this potential investment represent a sound strategic intervention that warrants detailed design?

---

The Trigger: The Programme Mandate

Process 1 is never initiated spontaneously by project teams or operational units. It requires a formal trigger from executive leadership known as the Programme Mandate.

┌─────────────────────────────────────────────────────────────────────────────┐
│                     THE PROGRAMME MANDATE (THE TRIGGER)                     │
├─────────────────────────────────────────────────────────────────────────────┤
│  Originates from: Corporate Board, Executive Leadership, or Sponsoring Group │
│  Contains:                                                                  │
│    - High-level strategic rationale and corporate policy drivers            │
│    - Broad transformational objectives and strategic ambitions              │
│    - Indicative resource and capital boundaries                             │
│    - Appointment or nomination of the Senior Responsible Owner (SRO)        │
└─────────────────────────────────────────────────────────────────────────────┘

Characteristics of the Programme Mandate

• Strategic Origin: The mandate represents an executive decision that a strategic challenge or opportunity cannot be addressed through routine business-as-usual (BAU) or a single isolated project.
• Variable Granularity: Depending on organizational maturity, a mandate may range from a high-level strategic directive (e.g., "Transition our retail banking footprint to a cloud-native digital delivery model by 2030") to a detailed corporate policy paper commissioned by enterprise planning.
• Mandate Governance: The mandate provides the formal authority to mobilize key governance roles and incur early exploratory expenditures required to conduct initial feasibility assessments.

---

Key Objectives: Strategic Desirability, Viability, and Feasibility

During Process 1, the newly formed startup leadership team evaluates the proposed initiative against three rigorous governance criteria:

1. Strategic Desirability: Does this initiative align directly with corporate strategy, policy objectives, and enterprise priorities? Will it produce transformative outcomes that advance the organization's mission, or is it an unnecessary distraction from core operations?
2. Commercial & Financial Viability: Does a preliminary cost-benefit analysis demonstrate that the expected strategic benefits significantly outweigh the estimated capital expenditure, operational disruption, and ongoing run costs?
3. Delivery Feasibility: Does the organization possess—or can it realistically acquire—the technical capabilities, human talent, organizational bandwidth, and supplier partnerships needed to deliver the transformation without destabilizing ongoing business operations?

By testing these three criteria early, the organization avoids the common pitfall of "escalation of commitment," where poorly conceived initiatives gain political momentum and become impossible to cancel once heavy delivery expenditures begin.

---

Key Roles Involved in Process 1

Process 1 establishes the initial leadership cadre responsible for steering the programme from concept through detailed design.

                     ┌──────────────────────────────────────────────┐
                     │               SPONSORING GROUP               │
                     │  - Issues Programme Mandate                  │
                     │  - Appoints Senior Responsible Owner (SRO)   │
                     │  - Owns ultimate investment gate decision    │
                     └──────────────────────┬───────────────────────┘
                                            │ Appoints & Empowers
                                            ▼
                     ┌──────────────────────────────────────────────┐
                     │       SENIOR RESPONSIBLE OWNER (SRO)         │
                     │  - Single point of executive accountability  │
                     │  - Leads Process 1 investigation             │
                     │  - Appoints Programme Manager                │
                     │  - Owns the Outline Business Case            │
                     └──────────────────────┬───────────────────────┘
                                            │ Appoints & Directs
                                            ▼
                     ┌──────────────────────────────────────────────┐
                     │              PROGRAMME MANAGER               │
                     │  - Coordinates startup investigations        │
                     │  - Authors the draft Programme Brief         │
                     │  - Conducts initial stakeholder consultations│
                     │  - Supports Outline Business Case modeling   │
                     └──────────────────────────────────────────────┘

1. The Sponsoring Group

The Sponsoring Group represents executive leadership and the primary corporate investors who hold ultimate financial sponsorship. In Process 1, the Sponsoring Group:

• Formally issues the Programme Mandate.
• Identifies, appoints, and empowers the Senior Responsible Owner (SRO).
• Commits initial seed funding to finance Process 1 activities.
• Serves as the executive decision-maker at the formal gate ending Process 1.

2. The Senior Responsible Owner (SRO)

The SRO is the single individual held personally accountable for the success of the programme and the realization of its business case. In Process 1, the SRO:

• Takes ownership of the Programme Mandate.
• Formally appoints the Programme Manager to manage startup operations.
• Directs the initial assessment of strategic desirability, viability, and feasibility.
• Engages executive peers across business units to build consensus and address emerging political friction.
• Submits the completed Programme Brief and Outline Business Case to the Sponsoring Group for approval.

3. The Programme Manager

The Programme Manager is appointed early by the SRO to provide day-to-day coordination and analytical rigor. In Process 1, the Programme Manager:

• Gathers data, interviews key stakeholders, and coordinates technical feasibility studies.
• Drafts the Programme Brief under the strategic guidance of the SRO.
• Collaborates with financial analysts and business architects to construct the Outline Business Case.
• Identifies initial candidate risks, assumptions, and critical dependencies.

[!NOTE] Role of Business Change Managers (BCMs) in Process 1: While full-time Business Change Managers are formally mobilized during Process 2 (Design the outcomes), the SRO and Programme Manager actively consult operational business leaders during Process 1 to gauge operational change appetite, validate candidate benefits, and identify potential constraints.

---

Core Management Products Created in Process 1

Process 1 produces two foundational management artifacts that form the baseline for executive review: the Programme Brief and the Outline Business Case.

Detailed Structure of the Programme Brief

The Programme Brief serves as the definitive expression of the programme's initial concept. Key sections include:

• Executive Rationale: Detailed narrative outlining the corporate drivers, competitive pressures, or statutory mandates necessitating transformation.
• Programme Objectives: Measurable, high-level transformational targets aligned with corporate strategy.
• Scope Boundaries: Explicit definition of what business units, technological platforms, and geographical regions are included in scope—and crucially, what is explicitly excluded to prevent scope creep.
• Candidate Benefits & Target Capabilities: High-level identification of the performance improvements, cost reductions, or revenue enhancements the organization expects to capture.
• Initial Risk Assessment: Preliminary inventory of macro threats (e.g., regulatory changes, technology immaturity, cultural resistance, supplier volatility) that could derail delivery.
• Initial Assumptions and Constraints: Fixed parameters such as statutory completion deadlines, capital expenditure ceilings, or core legacy system dependencies.
• Key Stakeholder Landscape: Initial mapping of influential internal and external stakeholder groups whose support is vital.

Detailed Structure of the Outline Business Case

The Outline Business Case provides preliminary economic justification. Rather than presenting a single rigid solution, it documents a structured options appraisal:

1. Option 1: Do Nothing / Business as Usual (BAU): Serves as the comparative financial baseline. It models the operational costs and competitive risks of taking no action.
2. Option 2: Minimal Intervention / Tactical Compliance: Evaluates low-cost, tactical fixes that address immediate compliance or operational pain points without achieving full transformation.
3. Option 3: Strategic Transformation: Evaluates the preferred, comprehensive transformational pathway that delivers the complete target operating model and maximizes benefits.

The Outline Business Case models broad capital expenditure (Capex) and operational expenditure (Opex) envelopes, provides rough order-of-magnitude (ROM) cost estimates (typically with a wide variance range, such as -20% to +50%), and establishes preliminary payback periods.

---

The Formal Decision Gate: Approval to Proceed to Detailed Design

Process 1 concludes at a mandatory executive decision gate. The Sponsoring Group convenes to formally review the Programme Brief and Outline Business Case presented by the SRO.

                    ┌────────────────────────────────────────┐
                    │        PROCESS 1 DECISION GATE         │
                    │       (Sponsoring Group Review)        │
                    └───────────────────┬────────────────────┘
                                        │
         ┌──────────────────────────────┼──────────────────────────────┐
         ▼                              ▼                              ▼
[ 1. AUTHORIZE DESIGN ]       [ 2. MANDATE REWORK ]          [ 3. DISCONTINUE ]
- Approves Programme Brief    - Requests deeper analysis     - Terminated early
- Approves Outline Case       - Adjusts scope boundaries     - Capital preserved
- Releases Design Budget      - Re-evaluates options         - Prevents wasteful
- Authorizes Process 2        - Re-submits to gate             escalation

The Three Formal Gate Decisions

1. Authorize Detailed Design (Proceed to Process 2): The Sponsoring Group confirms that the programme is strategically aligned, commercially viable, and feasible. They formally approve the Programme Brief, endorse the Outline Business Case, and authorize the release of the necessary budget and resources to execute Process 2: Design the Outcomes.
2. Mandate Rework / Refinement: If the Sponsoring Group determines that strategic scope boundaries are ambiguous, options appraisals are insufficient, or financial models are poorly substantiated, they mandate specific revisions before re-evaluating the gate.
3. Reject / Discontinue: If the initial investigation reveals that the proposed transformation is technically unachievable, excessively risky, or misaligned with shifting corporate strategy, the proposal is rejected immediately. In MSP governance, stopping an unviable initiative during Process 1 is considered an exemplary governance success, as it preserves millions in capital before significant expenditures occur.

[!IMPORTANT] Scope of the Gate Decision: Approval at the conclusion of Process 1 is not an authorization to begin executing projects or purchasing production hardware. It is strictly an authorization to invest the resources required to undertake detailed outcome and operating model design in Process 2.

---

Real-World Organizational Transformation Scenario

TransGlobal Logistics Decarbonization & Smart Network Transformation

Context: TransGlobal Logistics, an international freight operator with 8,000 delivery vehicles and 120 distribution hubs, faced stringent European carbon emission penalties and rapid market share erosion from automated tech-enabled courier startups.

The Trigger: The Corporate Board issued a Programme Mandate directing the formation of an exploratory team to evaluate transitioning the fleet to 100% zero-emission electric vehicles (EVs) and deploying automated robotic parcel-sorting hubs by 2032.

Executing Process 1:

• Role Appointments: The Sponsoring Group appointed the Chief Operating Officer (COO) as the Senior Responsible Owner (SRO). The SRO immediately recruited a seasoned enterprise delivery leader as the Programme Manager.
• Drafting the Programme Brief: The Programme Manager led a six-week cross-functional study involving fleet managers, facilities engineers, software architects, and regional directors. The resulting Programme Brief established strict scope boundaries: regional line-haul distribution and urban last-mile delivery were in scope, while long-haul air freight operations were explicitly excluded.
• Constructing the Outline Business Case: The team evaluated three options:
  • Option 1 (BAU): Continued diesel operations, incurring an estimated $85M in statutory carbon penalties by 2030.
  • Option 2 (Hybrid Retrofit): Retrofitting existing diesel trucks with hybrid powertrains (low upfront cost, but failed to meet net-zero targets).
  • Option 3 (Full EV & Automated Sortation Transformation): Purpose-built EV fleet acquisition, automated smart sortation hubs, and AI-driven dynamic routing software (estimated capital envelope: $450M; projected operational savings: $72M annually; 100% regulatory compliance).

The Decision Gate: The SRO presented the Programme Brief and Outline Business Case to the Sponsoring Group. The Sponsoring Group confirmed strategic desirability and commercial viability, formally authorizing $6.5M in design funding and directing the SRO to initiate Process 2: Design the Outcomes.

---

Exam Tips & Common Traps

• Exam Tip (The Mandatory Trigger): If an exam question asks what event formally initiates Process 1 (Identify the Programme), the correct answer is always the Programme Mandate.
• Exam Tip (Role Hierarchy in Startup): Remember the appointment sequence: The Sponsoring Group appoints the SRO, and the SRO appoints the Programme Manager.
• Common Trap (Business Case Granularity): Do not confuse the Outline Business Case (produced in Process 1 as an initial options appraisal and high-level viability check) with the Programme Business Case (drafted in Process 2 and baselined in Process 3). A fully detailed business case does not exist during Process 1.
• Common Trap (Authorizing Delivery vs. Authorizing Design): A classic exam distractor suggests that the Sponsoring Group's approval at the end of Process 1 authorizes the initiation of constituent projects. This is false. Approval at this gate only authorizes proceeding to Process 2 (Design the Outcomes) and committing design-phase expenditure.