10.3 Process 5: Embed the Outcomes

10.3 Process 5: Embed the Outcomes

[!NOTE] Core MSP Lifecycle Definition: In Managing Successful Programmes (MSP) 5th edition, Embed the Outcomes is the fifth lifecycle process. While Process 4 builds capabilities and transition management executes the initial go-live, Process 5 ensures that new ways of working become deeply institutionalized into everyday operational routines. Its purpose is to guide the business through stabilization so that capabilities produce sustained outcomes, early leading indicators of value are verified, and long-term strategic benefits emerge.

Executing a successful technical cutover and surviving the initial transition period is a major achievement, but it does not guarantee that the transformation will endure. Without disciplined reinforcement, human organizations exhibit an overwhelming natural tendency to revert to familiar legacy habits under operational stress.

Process 5 addresses this challenge directly. It is the phase where temporary change mechanisms are dismantled and new behaviors are hardwired into the cultural, structural, and operational DNA of the enterprise. By stabilizing new working practices, eliminating legacy workarounds, tracking leading indicators, and measuring user compliance, Process 5 transforms delivered capabilities into sustainable, measurable value.

---

Purpose and Scope of Embed the Outcomes

The primary purpose of Process 5 is to transition newly introduced capabilities into sustainable everyday operational routines (business-as-usual), achieving the desired change in operational performance (the outcome), and initiating the realization of strategic benefits.

┌─────────────────────────────────────────────────────────────────────────────┐
│                      THE VALUE REALIZATION PROGRESSION                      │
├─────────────────────────────────────────────────────────────────────────────┤
│  PROJECT OUTPUT     ──► An asset created by a project                       │
│                         (e.g., automated customer self-service portal)      │
│        │                                                                    │
│        ▼                                                                    │
│  CAPABILITY         ──► Operational ability to perform an activity          │
│                         (e.g., customer service reps & portal configured)   │
│        │                                                                    │
│        ▼                                                                    │
│  OUTCOME            ──► Sustained change in operational behavior & practice │
│                         (e.g., 85% of customer inquiries handled digitally) │
│        │                                                                    │
│        ▼                                                                    │
│  BENEFIT            ──► Quantifiable, measurable strategic improvement      │
│                         (e.g., $14M annual operating cost reduction)        │
└─────────────────────────────────────────────────────────────────────────────┘

The Core Scope of Process 5

Process 5 encompasses the operational activities required to anchor change across the enterprise:

• Reinforcing and institutionalizing target behaviors across frontline staff and operational supervisors.
• Decommissioning legacy applications, paper forms, and physical infrastructure to make regression impossible.
• Monitoring leading adoption indicators to detect early operational friction.
• Managing ongoing, subtle change resistance and eliminating informal "shadow systems."
• Measuring early benefits realization against the baselines baselined in the Benefit Profiles.
• Providing formal empirical feedback to the Programme Board and SRO to support tranche review gates.

---

Embedding New Working Practices into Everyday Operational Routines

Embedding is the process of turning "the new programme way" into "just the way we do things around here." For an outcome to be truly embedded, the new working practices must survive employee turnover, leadership changes, and daily operational crises.

Hardwiring Change into Enterprise Infrastructure

To prevent new behaviors from decaying over time, the Business Change Manager (BCM) hardwires the Target Operating Model into permanent business systems:

                             HARDWIRING EMBEDDED CHANGE
          ┌───────────────────────────────┼───────────────────────────────┐
          ▼                               ▼                               ▼
[ FORMAL JOB DESCRIPTIONS ]     [ PERFORMANCE APPRAISALS ]      [ ONBOARDING CURRICULA ]
- Updated role definitions      - KPIs tied to target behaviors - New employee training
- New competency frameworks     - Bonuses linked to adoption    - Standard training paths
- Clear task accountabilities   - Compliance in reviews         - Permanent skill building
          │                               │                               │
          ├───────────────────────────────┼───────────────────────────────┤
          ▼                               ▼                               ▼
[ COMPLIANCE AUDIT RUBRICS ]    [ GOVERNANCE & COMMITTEES ]     [ OPERATIONAL BUDGETS ]
- Routine quality floor audits  - Business unit agendas         - Reallocated Opex budgets
- Standard SOP compliance logs  - Operational review charters   - Permanent maintenance lines
- Error tracking dashboards     - Ongoing supervisory metrics   - Legacy budget stripped

1. Job Descriptions & Competency Frameworks: Formalizing new tasks and technical skills into standard human resources job descriptions and career progression ladders.
2. Performance Management & Incentives: Aligning employee scorecards, key performance indicators (KPIs), and annual bonus criteria with the new operational model. If sales representatives are rewarded based on volume rather than digital order accuracy, they will resist using the new system; aligning incentives ensures personal success mirrors programme success.
3. New Hire Onboarding Curricula: Integrating target operating procedures into the permanent training materials given to all new staff, ensuring institutional memory does not fade as employees leave.
4. Operational Governance & Review Charters: Incorporating new performance metrics into routine departmental weekly and monthly management meetings.

Decommissioning Legacy Infrastructure: "Burning the Boats"

One of the most powerful strategies for embedding outcomes is actively removing the legacy alternative. As long as old software platforms, paper order forms, or manual approval paths remain accessible, stressed employees will use them as crutches.

┌─────────────────────────────────────────────────────────────────────────────┐
│              DECOMMISSIONING CHECKLIST ("BURNING THE BOATS")                │
├─────────────────────────────────────────────────────────────────────────────┤
│  [x] Terminate legacy software maintenance contracts & vendor licenses      │
│  [x] Power down legacy servers and archive historical data stores           │
│  [x] Revoke user access permissions to old transactional databases          │
│  [x] Physically remove old paper forms, rubber stamps & legacy workstations │
│  [x] Redirect intranet URLs and software bookmarks to the new enterprise app│
│  [x] Audit departmental shared drives to eliminate unauthorized spreadsheets│
└─────────────────────────────────────────────────────────────────────────────┘

By systematically dismantling legacy infrastructure, the BCM eliminates the possibility of operational regression, compelling all personnel to master the new capability.

---

Tracking the Transition: From Capability to Stable Operational Outcome

Transition cutover creates an unstable operational environment characterized by the J-curve performance dip. Process 5 tracks the progression of the business unit as it climbs out of the dip and establishes a new, stable operational baseline.

Defining Operational Stability

How does the BCM know when a capability has successfully converted into a stable outcome? MSP defines operational stability through clear empirical criteria:

• Predictable Process Throughput: Transaction processing times and operational output achieve or exceed the Target Operating Model specifications.
• Normalized Error Rates: Transaction error rates, rework loops, and customer complaints drop back down to—or below—pre-change historical averages.
• Withdrawal of Super-Users: Frontline personnel process complex and atypical transactions independently without relying on transition floor-walkers or external project developers.
• Supervisory Autonomy: Routine operational managers and team leads manage performance and handle operational exceptions within standard operating procedures.

Once stability is confirmed, the temporary transition state is formally concluded, and the new operational state becomes the official business-as-usual.

---

Monitoring Early Leading Indicators of Benefits Realization

Transformational programmes exist to realize strategic benefits—such as increased profitability, reduced carbon footprint, improved customer retention, or enhanced regulatory compliance. However, these ultimate benefits are lagging indicators; they often take 6 to 24 months to fully materialize on corporate balance sheets.

If programme governance waits two years to see if profits rise, it is too late to fix an operational failure. Process 5 solves this by continuously monitoring leading indicators.

Leading vs. Lagging Indicators in Benefits Realization

LEADING INDICATORS (Process 5)                LAGGING BENEFITS (Long-Term Value)
┌────────────────────────────────────┐        ┌────────────────────────────────────┐
│ • 94% User Adoption of New CRM     │───────►│ • 22% Increase in Cross-Sell Margin│
│ • Quotation Lead Time Down to 2 Hrs│        │ • $18M Working Capital Optimization│
│ • Order Error Rate Drops to 0.4%   │        │ • #1 Regional Customer Satisfaction│
└────────────────────────────────────┘        └────────────────────────────────────┘

Validating the Benefits Map

During Process 5, the BCM compares actual leading metrics against the cause-and-effect pathways documented in the Benefits Map (formulated in Process 2). If a leading indicator is lagging—for example, if user adoption of a self-service customer portal is only 30% instead of the projected 70%—the BCM immediately investigates root causes (e.g., poor user experience, lack of customer awareness, or counter-incentives in sales commissions) and executes corrective actions.

---

The Role of the BCM in Measuring Adoption and User Compliance

The Business Change Manager (BCM) is the primary operational custodian of Process 5. While the Programme Manager tracks project schedules and budgets, the BCM focuses relentlessly on human adoption, operational compliance, and value realization.

The Spectrum of Employee Adoption

In live operations, the BCM encounters a spectrum of user behaviors:

┌─────────────────────────────────────────────────────────────────────────────┐
│                      THE ADOPTION BEHAVIOR SPECTRUM                         │
├─────────────────────────────────────────────────────────────────────────────┤
│  1. CHAMPIONS (15%)  : Enthusiastically adopt, discover new efficiencies,   │
│                        and actively mentor struggling colleagues.            │
│  2. COMPLIANT (65%)  : Adopt new methods routinely because mandated, but    │
│                        still experience occasional friction.                 │
│  3. PASSIVE (15%)    : Avoid new tools when unsupervised; maintain offline   │
│                        spreadsheets; slow down team throughput.              │
│  4. SUBVERSIVE (5%)  : Actively reject new workflows; create shadow work-    │
│                        arounds; voice cynical dissent across the unit.       │
└─────────────────────────────────────────────────────────────────────────────┘

BCM Interventions for Non-Compliance

• Targeted Refresher Coaching: Conducting small-group, hands-on clinics for users struggling with specific workflow steps.
• Root-Cause Analysis: Distinguishing between ability issues (the user does not understand the software or the interface is poorly designed) and motivation issues (the user understands the tool but refuses to use it due to loss of perceived status).
• Eliminating Ergonomic Friction: Partnering with the Programme Manager to deliver minor software enhancements that resolve annoying daily friction points (e.g., removing redundant data entry fields or adding keyboard shortcuts).
• Management Escalation: When deliberate non-compliance persists despite coaching, the BCM leverages operational line management authority to enforce compliance through formal supervisory reviews.

---

Managing Resistance and Preventing Reversion to Shadow Systems

One of the most insidious threats in Process 5 is the emergence of shadow systems—unauthorized, informal tools and workarounds created by operational staff to circumvent new standard procedures.

Anatomy of a Shadow System

• The Private Spreadsheet: An accounting team copies data out of the new enterprise ERP into private Excel spreadsheets to reconcile balances because they prefer familiar keyboard macros.
• The Paper Clipboard: Hospital nurses write patient vitals on paper sheets taped to clipboards, batch-typing the records into the electronic health system at the end of a 12-hour shift rather than documenting in real time at the bedside.
• The Offline Email Chain: Customer service teams route escalated support requests via informal peer emails rather than logging them in the central ticketing system.

Why Shadow Systems Destroy Value

Shadow systems fragment data integrity, introduce severe cybersecurity and compliance risks, degrade operational transparency, and directly prevent the realization of benefits. If data is entered hours late or stored on private desktops, automated real-time analytics and predictive capabilities cannot function.

Eradication Strategies

The BCM eliminates shadow systems through a balanced combination of empathy, engineering, and enforcement:

1. Listen to the Symptom: A shadow system is usually an unvarnished signal that a specific workflow in the Target Operating Model is clunky or poorly optimized. The BCM captures this operational reality and requests targeted adjustments from the delivery team.
2. Locking Down Shadow Workflows: Working with IT to block unauthorized macros, disable local data exports where inappropriate, and remove shared network folders used for illicit spreadsheets.
3. Visible Leadership Role-Modeling: Ensuring department heads, lead clinicians, and senior managers visibly and exclusively use the new system in all public meetings, dashboards, and operational reviews.

---

Formal Feedback into the Programme Board on Benefits Emergence

Process 5 is not an isolated operational silo; it provides vital empirical intelligence that fuels programme governance.

┌────────────────────────┐                          ┌────────────────────────┐
│       PROCESS 5        │                          │    PROGRAMME BOARD     │
│   Embed the Outcomes   │                          │      & SRO REVIEW      │
├────────────────────────┤                          ├────────────────────────┤
│ • Leading Indicators   │                          │ • Evaluates Tranche Gate│
│ • User Adoption Rates  │─────────────────────────►│ • Validates Business Case│
│ • Measured Early Value │  Formal Benefits Report  │ • Authorizes Next      │
│ • Operational Baselines│                          │   Tranche Investment   │
└────────────────────────┘                          └────────────────────────┘

Feeding the Tranche Review Gate

As each delivery tranche reaches completion, the Sponsoring Group and Programme Board convene for a formal Tranche Review Gate. They do not merely ask: Did the projects deliver their outputs on time? They demand empirical answers to vital value questions:

• Has the business unit successfully absorbed the new capability?
• Are error rates stable and operational throughput normalized?
• What percentage of operational personnel are fully compliant with target workflows?
• What early benefits have emerged, and do leading indicators substantiate the multi-year Business Case?

The BCM provides this evidence through the formal Benefits Realization Report. If the BCM demonstrates that outcomes are firmly embedded and leading indicators are positive, the Programme Board confidently authorizes capital release for subsequent tranches. If adoption is faltering, the Board directs resources to remediate embedding before launching new projects.

---

Real-World Organizational Transformation Scenario

AeroFleet Global Aviation: Aircraft Maintenance & Inventory Transformation

Context: AeroFleet Global, an international cargo airline operating 140 widebody freighters across 12 maintenance hangars, executed a multi-year programme to deploy an IoT predictive maintenance and automated parts replenishment platform.

Executing Process 5 (Embed the Outcomes):

• Dismantling Legacy Systems: Following cutover, the BCM for Fleet Maintenance formally decommissioned the 25-year-old green-screen parts requisition database and collected all physical paper maintenance clipboards from the hangar floors.
• Uncovering and Resolving Shadow Workarounds: Two months post-cutover, leading indicators revealed that parts requisition cycle times in two hangars were lagging by 50%. The BCM conducted a floor walk and discovered a shadow system: senior mechanics were handwriting part orders in personal paper pocket notebooks and having apprentice technicians key them into the digital system at shift end. Why? The mobile tablets issued to mechanics were difficult to navigate while wearing heavy, grease-covered work gloves.
• Collaborative Remediation: The BCM escalated the issue to the Programme Manager. Within three weeks, the project team deployed voice-activated headsets and ruggedized barcode scanners that mechanics could easily operate without removing protective gloves. The paper notebooks disappeared.
• Tracking Benefits Emergence: With the workflow friction removed, mechanics embraced real-time logging:
  • Leading Indicator: Mobile part-logging compliance soared from 61% to 99.2% across all 12 hangars.
  • Leading Indicator: Aircraft ground inspection turnaround times dropped by 38 minutes per turnaround.
  • Lagging Benefit: Aircraft-On-Ground (AOG) maintenance delays decreased by 44% over the subsequent six months, capturing $32M in verified fuel, logistics, and downtime savings.
• Tranche Review Gate: The BCM presented these verified metrics to the Programme Board, providing the empirical justification required for the Sponsoring Group to approve $45M in funding for Tranche 3.

---

Exam Tips & Common Traps

• Exam Tip (BCM Accountability for Embedding): In MSP 5th edition, the Business Change Manager (BCM) is explicitly accountable for embedding outcomes and realizing benefits within their operational business area.
• Exam Tip (The Value Progression Chain): Memorize the foundational sequence: Project Outputs lead to Organizational Capabilities, which enable Operational Outcomes, which realize Strategic Benefits.
• Common Trap (Outcome vs. Benefit): A classic exam distractor confuses outcomes with benefits. An outcome is a resulting operational state or change in behavior (e.g., call center staff resolving 80% of customer issues on the first call). A benefit is the quantifiable improvement of business value derived from that outcome (e.g., $5M reduction in customer service operational costs).
• Common Trap (Projects Realize Benefits): Exam questions often test whether project delivery teams are responsible for benefits realization. They are not. Projects deliver outputs; the operational business units, led by BCMs, embed outcomes and harvest benefits during and after Process 5.