11.1 Process 6: Evaluate New Information

11.1 Process 6: Evaluate New Information

[!NOTE] Core MSP Lifecycle Definition: In Managing Successful Programmes (MSP) 5th edition, Evaluate New Information is Process 6. Unlike sequential lifecycle processes that occur at specific chronological milestones, Process 6 is an active, continuous process that operates across the entire life of the programme. Its fundamental purpose is to establish an ongoing sensing and evaluation mechanism that monitors the internal delivery environment and external landscape, assesses the implications of emerging information, and triggers appropriate governance interventions to sustain strategic alignment and business justification.

Transformational programmes take years to execute, cost millions of dollars, and navigate complex organizational ecosystems. Over such extended delivery horizons, the initial assumptions established during programme startup inevitably decay. Competitors release disruptive technologies, regulatory mandates evolve, macroeconomic conditions fluctuate, corporate leadership changes, and constituent project delivery teams encounter unforeseen technical roadblocks.

Traditional project thinking often treats change as a defect or a failure of initial planning. In contrast, MSP 5th edition embraces change as an inescapable reality of large-scale transformation. Process 6 operationalizes two foundational MSP principles: Deal with ambiguity (recognizing that programmes operate in fluid, uncertain environments) and Align with priorities (ensuring the programme pivots whenever organizational strategy or external drivers shift).

---

The Philosophy of Continuous Sensing vs. Periodic Inspection

A common failure mode in legacy programme management is "gate-only governance"—the dangerous practice of evaluating progress and environmental shifts only when a delivery tranche concludes. If an enterprise waits twelve to eighteen months between formal tranche reviews to examine whether its strategic direction remains sound, it risks spending millions delivering capabilities that have become obsolete before deployment.

┌─────────────────────────────────────────────────────────────────────────────┐
│                     TRADITIONAL VS. MSP 5TH EDITION GOVERNANCE              │
├─────────────────────────────────────────────────────────────────────────────┤
│  Traditional Waterfall Mindset:                                             │
│    Assume Baseline is Static ──► Deliver Blindly ──► Audit at Tranche Gate  │
│    [Result: High vulnerability to market shifts, sunk-cost entrapment]     │
│                                                                             │
│  MSP 5th Edition Continuous Feedback Loop (Process 6):                      │
│    Continuous Scanning ──► Impact Analysis ──► Dynamic Baseline Adjustment  │
│    [Result: Agile alignment, early threat mitigation, preserved investment] │
└─────────────────────────────────────────────────────────────────────────────┘

Process 6 establishes a perpetual, closed-loop feedback mechanism. It ensures that whenever significant new data arises—whether an external statutory ruling or an internal engineering breakthrough—the programme leadership promptly evaluates its systemic consequences across all governance themes rather than deferring the assessment to a distant milestone.

---

Sources and Triggers: Internal vs. External Information

New information originates from two primary spheres: the external macro-environment and the internal organizational and delivery environment.

                             THE SPECTRUM OF NEW INFORMATION
          ┌───────────────────────────────────┼───────────────────────────────────┐
          ▼                                                                       ▼
┌───────────────────────────────────┐                   ┌───────────────────────────────────┐
│   EXTERNAL SOURCES & TRIGGERS     │                   │   INTERNAL SOURCES & TRIGGERS     │
├───────────────────────────────────┤                   ├───────────────────────────────────┤
│ • PESTLE Environmental Forces     │                   │ • Shifting Corporate Strategy     │
│ • Statutory & Regulatory Changes  │                   │ • Executive Sponsor Changes       │
│ • Competitor Disruptions          │                   │ • Project Variances (Cost/Time)   │
│ • Macroeconomic & Market Shifts   │                   │ • Operational Change Fatigue      │
│ • Emerging Technologies           │                   │ • Benefits Realization Velocity   │
│ • Third-Party Supplier Volatility │                   │ • Risk Crystallization (Issues)   │
└───────────────────────────────────┘                   └───────────────────────────────────┘

1. External Sources of New Information

External triggers originate outside the boundaries of the host organization. Programme leadership must utilize structured horizon-scanning tools (such as PESTLE analysis) to capture these shifts:

• Political & Regulatory Drivers: Sweeping legal updates (such as national data protection statutes, cross-border carbon tariffs, or sector-specific licensing criteria) that render existing operational designs non-compliant.
• Economic Fluctuations: Major shifts in interest rates, foreign exchange volatility, or inflation that distort capital procurement costs and supplier contracts.
• Societal & Demographic Shifts: Changing customer behavior, public expectations, or workforce demographics that alter the target operational user experience.
• Technological Breakthroughs: The emergence of generative AI, cloud-native architectures, or automated platforms that offer faster, cheaper alternatives to the solutions currently being engineered by constituent projects.
• Market & Competitor Actions: Aggressive pricing, mergers, or novel service offerings by rival organizations that demand a pivot in the programme's value proposition.

2. Internal Sources of New Information

Internal triggers emerge from within the enterprise or from the constituent projects executing work packages:

• Corporate Strategy Realignments: Revisions to enterprise strategy, capital rationing by the corporate board, or the acquisition of a new business unit that alters the programme's mandate.
• Delivery Variances & Slippages: Substantial deviations in project milestones, software defect backlogs, contractor disputes, or technical integration failures detected by second-line assurance.
• Operational Change Capacity & Absorption: Feedback from Business Change Managers (BCMs) indicating that frontline operational staff are experiencing severe change fatigue, threatening operational stability during planned cutovers.
• Benefits Realization Metrics: Early empirical measurements showing that realized intermediate benefits are tracking significantly above or below the trajectory baselined in the Benefits Realization Plan.
• Risk Crystallization: Emerging threats materializing into actual issues that exceed the risk management contingency reserves or risk appetite established in the Programme Strategy.

---

The 4-Stage Sensing and Evaluation Framework

To prevent Process 6 from becoming an ad hoc or chaotic exercise, MSP structures the evaluation of new information through a four-stage sensing loop:

  STAGE 1                 STAGE 2                 STAGE 3                 STAGE 4
┌──────────────┐        ┌──────────────┐        ┌──────────────┐        ┌──────────────┐
│  IDENTIFY &  │ ─────► │   FILTER &   │ ─────► │   ANALYZE    │ ─────► │  RECOMMEND & │
│   CAPTURE    │        │ PRIORITIZE   │        │   BASELINE   │        │  GOVERNANCE  │
│  (Continuous │        │ (Relevance   │        │    IMPACT    │        │  DECISION    │
│   Scanning)  │        │  Thresholds) │        │ (Cross-Theme)│        │ (Escalation) │
└──────────────┘        └──────────────┘        └──────────────┘        └──────────────┘

Stage 1: Identify & Capture (Continuous Horizon Scanning)

The Programme Office (PMO), enterprise architects, risk managers, and Business Change Managers maintain active intelligence-gathering networks. They review industry publications, regulatory filings, internal project highlight reports, and corporate executive briefings to capture emerging signals early.

Stage 2: Filter & Prioritize (Relevance Thresholds)

Not every piece of news warrants executive attention. The Programme Manager applies relevance filters to separate operational background "noise" from strategically significant information. Items are screened against predefined governance criteria: Does this information affect our strategic objectives, Target Operating Model, timeline, cost envelope, or risk profile?

Stage 3: Analyze Baseline Impact (Cross-Theme Evaluation)

Once prioritized, the programme team assesses the ripple effect of the new information across all interconnected governance baselines. A single regulatory change, for example, may simultaneously force an architectural modification to the Target Operating Model, delay the delivery schedule in the Delivery Plan, increase the cost baseline in the Business Case, and defer benefit realization.

Stage 4: Formulate Recommendations & Governance Decision

The Programme Manager, in collaboration with the BCM and Design Authority, formulates objective, evidence-based options for the Senior Responsible Owner (SRO). Depending on delegated authority limits, the SRO either enacts necessary adjustments or escalates strategic choices to the Sponsoring Group.

---

Impact on Core Programme Governance Baselines

When new information is evaluated and validated, it frequently requires synchronized updates across the four primary governance baselines of the programme:

---

The Governance Decision Spectrum: Tolerances vs. Escalations

A critical exam concept in MSP 5th edition is the relationship between delegated tolerances and governance escalation during Process 6.

                     ┌──────────────────────────────────────────────┐
                     │       NEW INFORMATION IMPACT EVALUATED       │
                     └──────────────────────┬───────────────────────┘
                                            │
                     Does the impact breach programme tolerances?
                                            │
                      ┌─────────────────────┴─────────────────────┐
                      ▼ NO                                        ▼ YES
       ┌─────────────────────────────┐             ┌─────────────────────────────┐
       │   WITHIN DELEGATED LIMITS   │             │   TOLERANCE BREACH DETECTED │
       ├─────────────────────────────┤             ├─────────────────────────────┤
       │ • SRO / Programme Manager   │             │ • SRO escalates to          │
       │   approves internal shifts  │             │   Sponsoring Group          │
       │ • Reallocate contingency    │             │ • Formal options appraisal  │
       │ • Adjust project priorities │             │   presented for decision    │
       └─────────────────────────────┘             └──────────────┬──────────────┘
                                                                  │
                                        ┌─────────────────────────┼─────────────────────────┐
                                        ▼                         ▼                         ▼
                                 [ 1. RESCOPE ]            [ 2. RE-BASELINE ]        [ 3. TERMINATE ]
                                 Add/cancel projects       Formally adjust cost,     Controlled early
                                 or alter capabilities     time, and benefit baselines  closure to cut losses

1. Action Within Delegated Tolerances

If the evaluated impact falls within the tolerances established by the Sponsoring Group (e.g., within +/- 5% budget variance or +/- 30 days schedule float), the SRO and Programme Manager take corrective operational action. This might include reallocating contingency funds between projects, adjusting work package sprint priorities, or reassigning specialist technical staff.

2. Formal Escalation to the Sponsoring Group

If the evaluated impact threatens to exceed programme-level tolerances—or invalidates a fundamental premise of the Business Case—the SRO must formally escalate the issue to the Sponsoring Group. The SRO presents a comprehensive Exception Report and options appraisal outlining five potential pathways:

1. Absorb and Adjust: Reallocate capital from low-priority work streams or accept minor compromises in non-critical operational capabilities.
2. Rescope the Programme: Commission new constituent projects to develop newly required capabilities, or formally de-scope and cancel projects whose deliverables have been superseded.
3. Re-baseline Governance Baselines: Formally reset the approved baselines for cost, time, and benefits realization through formal change control, securing additional investment funding from executive sponsors.
4. Pause / Hold Delivery: Temporarily suspend specific high-cost delivery projects while external regulatory or commercial uncertainties are resolved, avoiding further uncommitted capital burn.
5. Recommend Early Termination: Conclude that the programme is no longer strategically desirable, commercially viable, or achievable, and initiate controlled early closure to protect corporate capital.

[!IMPORTANT] Early Termination as Governance Success: In MSP governance, recommending early termination following the evaluation of new information is not an admission of failure. It is the ultimate demonstration of responsible, mature governance. Ending an unviable initiative before further millions are wasted protects shareholder value and reallocates scarce resources to higher-yielding enterprise opportunities.

---

Real-World Organizational Transformation Scenario

AeroShield Defence & Avionics Systems Transformation

Context: AeroShield Avionics initiated a $320M multi-year transformation programme to consolidate four disparate defense hardware manufacturing facilities into a single high-tech, automated manufacturing hub operating on a proprietary robotic assembly architecture.

The Emerging Information (Year 2 of Delivery):

1. External Regulatory Trigger: The Ministry of Defence introduced a new statutory cybersecurity and sovereignty framework prohibiting the use of third-party firmware in automated robotic cells.
2. External Market Trigger: A key robotic systems integrator entered bankruptcy administration, halting delivery of specialized robotic assembly arms.
3. Internal Performance Trigger: In-house software engineering teams developed a breakthrough micro-manufacturing workflow that reduced physical floor space requirements by 45%.

Applying Process 6 (Evaluate New Information):

• Stage 1 & 2 (Capture & Filter): The Programme Manager immediately recognized these events as high-severity strategic triggers rather than minor project issues.
• Stage 3 (Impact Assessment):
  • TOM Impact: The automated manufacturing facility design had to be completely reconfigured across the Technology, Information, and Processes facets to accommodate sovereign-firmware robotics and smaller cleanrooms.
  • Delivery Plan Impact: Halting the bankrupt supplier's project threatened the critical path by 14 months.
  • Business Case Impact: Software breakthroughs promised an additional $35M in recurring operational savings, but redesigning the facility would require an immediate $22M capital injection.
• Stage 4 (SRO Recommendation & Sponsoring Group Gate): The SRO presented three formal options to the Sponsoring Group: (a) Attempt to rescue the bankrupt supplier; (b) Revert to traditional manual assembly; or (c) Formally rescope the programme by terminating the robotic contract, adopting the internal micro-manufacturing breakthrough, and re-baselining the delivery schedule by 6 months.

The Outcome: The Sponsoring Group approved Option (c), formally authorizing a $22M re-baseline and commissioning a new domestic secure software work stream. Process 6 preserved the strategic integrity of the transformation and turned potential catastrophic failure into long-term technological leadership.

---

Exam Tips & Common Traps

• Exam Tip (Continual Nature of Process 6): If an exam question asks which MSP process operates iteratively and continuously throughout the entire lifecycle—rather than sequentially at specific boundaries—the answer is Process 6: Evaluate New Information.
• Exam Tip (Who Decides on Tolerance Breaches?): When evaluated information indicates that programme-level tolerances will be breached, the decision authority does not rest with the Programme Manager or Project Managers. The SRO must escalate the decision to the Sponsoring Group.
• Common Trap (Change as Failure): Watch out for exam distractors suggesting that updating the Business Case or Target Operating Model during delivery indicates poor initial planning. In MSP, progressive elaboration and dynamic baseline updating are the hallmarks of effective, adaptive governance.
• Common Trap (Process 6 vs. Project Change Control): Do not confuse Process 6 with lower-level project change control (e.g., evaluating a software change request in PRINCE2). Process 6 operates at the strategic programme level, evaluating how multi-faceted environmental shifts impact enterprise outcomes, intermediate states, and benefits.