2.4 Bring Pace and Value & Tailoring MSP Principles
Key Takeaways
- Principle 7 ('Bring pace and value') advocates maintaining relentless delivery momentum and realizing early value through incremental tranches and agile capability drops.
- Monolithic 'big bang' transformations create stakeholder fatigue, heighten operational risk, and risk delivering obsolete capabilities after multi-year delays.
- The 7 MSP principles are universal (applying to all programmes), self-validating (proven by empirical practice), and empowering (enabling contextual autonomy).
- While MSP principles are absolute and non-negotiable, the themes, processes, and documentation must be tailored to organizational scale, complexity, sector, and culture.
- Public sector programmes emphasize societal value, regulatory compliance, and multi-stakeholder transparency, whereas private sector programmes prioritize speed-to-market and financial ROI.
2.4 Bring Pace and Value & Tailoring MSP Principles
[!NOTE] Balancing Momentum and Context: The final principle in Managing Successful Programmes (MSP 5th edition)—Bring pace and value—ensures that transformational change does not collapse under its own weight. Programmes that drag on for years without demonstrating visible, tangible progress suffer from change fatigue, leadership turnover, and eventual cancellation. Furthermore, understanding how the 7 principles operate as a cohesive, universal system—and how the framework must be tailored to specific organizational contexts—is central to mastering the MSP Foundation syllabus.
Transformational programmes require substantial investments of organizational capital, time, and emotional energy. To justify this investment and sustain organizational commitment, programmes must establish delivery momentum early and maintain a consistent cadence of value release. Principle 7 provides the pacing framework, while the concept of tailoring ensures that MSP's principles, themes, and processes are applied appropriately across different sectors, scales, and cultures.
Principle 7: Bring Pace and Value
Principle 7 establishes that programmes must be structured to deliver value incrementally and maintain a tempo that prevents stagnation. It directly challenges the outdated, high-risk philosophy of "big bang" transformation.
Maintaining Delivery Momentum
Change initiatives face a relentless enemy: organizational inertia. When a programme is announced, initial stakeholder enthusiasm is high. However, if months or years elapse without visible operational progress, cynical attitudes take root ("this is just another executive initiative that will produce nothing"). Team members become fatigued, key sponsors move on to other corporate roles, and operational leaders lose faith.
- Establishing a Rhythm of Delivery: Programme leaders must establish a steady, predictable cadence of delivery. Regular milestones, interim capability drops, and early operational wins create positive momentum, reassuring stakeholders that their investments and efforts are generating tangible returns.
- Combating Analysis Paralysis: A frequent trap in complex environments is endless planning and governance deliberation. Principle 7 demands sufficient governance to control risk without allowing governance to choke execution pace.
Incremental Tranches and Early Value Realization
The core mechanism in MSP for realizing pace and value is the division of the programme lifecycle into tranches:
+-------------------------------------------------------------------------+
| Tranche-Based Value Realization Architecture |
+-------------------------------------------------------------------------+
| [ Tranche 1: Foundation & Early Value ] |
| - Delivers initial core capability |
| - Realizes early 'quick-win' benefits |
| - Validates business assumptions & tests operational readiness |
| |
| [ Tranche 2: Core Capability Expansion ] |
| - Broadens operational capabilities across main business units |
| - Harvests intermediate financial & operational benefits |
| - Calibrates operating model based on Tranche 1 learnings |
| |
| [ Tranche 3: Full Target Operating Model & Optimization ] |
| - Implements full Target Operating Model |
| - Achieves end-state strategic benefits |
| - Embeds permanent continuous improvement into BAU |
+-------------------------------------------------------------------------+
- Tranche Definition: A tranche is a structured cohort of projects organized to deliver a discrete step-change in organizational capability and realize a defined package of intermediate benefits.
- Early Value Realization: Rather than waiting for the entire 5-year programme to finish, Tranche 1 (typically 6–12 months) delivers early capabilities that operational teams can use immediately. This early value justifies past investment and builds organizational confidence for subsequent tranches.
The Fatal Hazards of the 'Big Bang' Model
In a big-bang transformation, all project outputs are accumulated over a multi-year development cycle and deployed simultaneously in a single massive transition. MSP strongly discourages this approach.
| Dimension | Big-Bang Transformation Model | Incremental Tranche Delivery (Principle 7) |
|---|---|---|
| Time to First Value | 3 to 5+ years (value deferred until end) | 6 to 12 months (early value realized in Tranche 1) |
| Operational Disruption | Massive shock to operational BAU; high failure risk | Manageable, absorbable transitions across tranches |
| Feedback & Learning | Zero live operational feedback during development | Rich operational learnings feed into next tranche design |
| Risk Exposure | Concentrated at a single catastrophic point of failure | Dispersed and mitigated progressively across tranches |
| Stakeholder Confidence | Wanes over time due to lack of tangible evidence | Strengthened continuously with each capability release |
Agile Capability Drops and Minimum Viable Products (MVPs)
Modern MSP implementations blend programme-level tranche governance with agile project execution:
- Agile Integration: Individual project teams within a tranche may operate in 2-week Scrum sprints or continuous Kanban flows, producing rapid technical iterations.
- Minimum Viable Products (MVPs): Projects deliver the smallest functional version of a capability that can be safely transitioned into operations. Frontline staff begin using the MVP, generating real-world data that refines future capability drops.
[!TIP] Exam Tip: When questions describe a programme board debating whether to deploy all systems in a single cutover after 4 years or break delivery into 12-month tranches that release intermediate capabilities, the correct MSP answer is rooted in Principle 7: Bring pace and value—deliver incrementally through tranches to harvest early benefits and reduce transition risk.
The Foundational Nature of the 7 MSP Principles
To excel in the MSP Foundation examination, you must understand the overarching characteristics that define all seven principles:
- Universal: They apply universally across every programme. Whether a programme is building a nuclear submarine, rolling out an enterprise cloud ERP, restructuring a municipal social services department, or executing a corporate merger, the 7 principles apply without exception.
- Self-Validating: The principles are not theoretical hypotheses; they are empirical truths derived from extensive post-programme reviews spanning decades of successes and catastrophic failures. Adherence to them consistently correlates with transformational success; disregarding them consistently correlates with project delays, cost overruns, and strategic failure.
- Empowering: Principles do not dictate prescriptive actions or create bureaucratic bottlenecks. Instead, they provide decision-makers with the confidence, clarity, and authority to navigate ambiguity and design contextual solutions.
- Non-Negotiable: Principles cannot be tailored out. An organization cannot claim to be managing an MSP programme while ignoring Principle 6 (Realize measurable benefits) or Principle 4 (Align with priorities).
+-------------------------------------------------------------------------+
| The 7 Universal MSP Principles |
+-------------------------------------------------------------------------+
| 1. Lead with purpose 5. Deploy diverse skills |
| 2. Collaborate across boundaries 6. Realize measurable benefits |
| 3. Deal with ambiguity 7. Bring pace and value |
| 4. Align with priorities |
+-------------------------------------------------------------------------+
│
UNDERPIN AND INFORM (Cannot Tailor Out)
▼
+-------------------------------------------------------------------------+
| The 7 MSP Themes & 7 Lifecycle Processes |
| (TAILORED to Scale, Sector, Culture, Complexity, and Maturity) |
+-------------------------------------------------------------------------+
Tailoring the Application of MSP Principles
While the principles themselves are immutable and mandatory, how they are applied through themes, lifecycle processes, and governance documentation MUST be tailored to the unique environment of the programme.
The Tailoring Dimensions
When tailoring MSP, the governance team evaluates four critical dimensions:
- Scale and Complexity: A £5 million departmental workflow upgrade requires lightweight governance—perhaps combining the roles of Programme Manager and Business Change Manager, holding monthly boards, and utilizing simplified risk logs. A £2 billion national high-speed rail initiative requires dedicated assurance teams, full-time BCMs per operational division, formal Gateway reviews, and multi-tier board structures.
- Organizational Maturity: An organization with high process maturity (e.g., CMMI Level 4/5 or mature P3O offices) can rely on established enterprise standards. An organization with low maturity requires explicit, hands-on governance frameworks and external coaching.
- Delivery Culture (Agile vs Waterfall): In highly agile environments, programme governance adapts by aligning tranche boundaries with agile release trains (ARTs) and replacing heavy documentation with digital collaboration boards, while still enforcing business justification and benefits realization.
Sector-Specific Tailoring: Public vs Private Sectors
The operating environment of the public sector differs fundamentally from the private sector, requiring distinct tailoring approaches:
| Tailoring Dimension | Public Sector Programmes | Private Sector Programmes |
|---|---|---|
| Primary Objective | Public value, societal outcomes, policy execution, citizen welfare | Shareholder value, financial return on investment (ROI), competitive market share |
| Accountability & Scrutiny | High political scrutiny, parliamentary committees, Freedom of Information (FOI), public media | Corporate board of directors, institutional investors, commercial confidentiality |
| Procurement Framework | Heavily regulated statutory procurement rules (e.g., public tender directives, strict fairness) | Flexible commercial negotiations, strategic equity partnerships, direct sourcing |
| Funding Mechanisms | Multi-year government spending reviews, public tax revenues, ministerial appropriations | Corporate balance sheets, commercial debt, equity issuance, venture financing |
| Benefits Focus | Often qualitative/societal: reduced crime, improved healthcare outcomes, carbon reduction | Primarily quantifiable financial: revenue uplift, margin expansion, cost reductions |
[!WARNING] Common Exam Trap: Be vigilant regarding the exact boundary of tailoring. Themes, processes, management products, and role structures are tailored. Principles are NEVER tailored. Any exam option that proposes "tailoring out" or "omitting" an MSP principle is incorrect.
Real-World Transformation Case: National Digital Tax Platform
- Context: A national revenue department undertook a 6-year transformation to migrate 18 million taxpayers and 2.5 million corporate entities to a fully digital self-service tax platform.
- Applying Principle 7 (Bring Pace and Value): The department avoided a massive big-bang cutover. Instead, it structured delivery into three distinct 18-month tranches. Tranche 1 delivered an MVP portal allowing small sole-proprietor businesses to file VAT digitally, achieving early value within 14 months and testing core payment integrations. Tranche 2 expanded to corporate payroll taxes, and Tranche 3 integrated complex cross-border corporate filings. Each tranche delivered immediate operational cost savings that funded the next phase.
- Tailoring to Context: Because this was a high-profile public sector programme, tailoring addressed extreme public accountability. Freedom of Information protocols and statutory privacy compliance were woven into the Design theme, while independent parliamentary audit gateway reviews were aligned to tranche boundaries. However, all 7 principles—from leading with purpose to realizing measurable benefits—were rigorously enforced without compromise.
Exam Tips and Common Exam Traps
[!TIP] Exam Tip: Remember the three foundational adjectives that describe MSP principles: Universal (apply to all programmes), Self-validating (empirically proven by historical practice), and Empowering (enable practitioner autonomy). These terms appear frequently in exam questions.
[!WARNING] Common Exam Trap: Do not confuse bringing pace with rushing recklessly. Bringing pace means designing for momentum through structured, incremental tranches and agile capability drops; it never means bypassing safety gates, skipping assurance reviews, or abandoning governance control.
A programme office consultant is advising a charitable foundation launching a mid-sized community outreach transformation. The foundation director suggests omitting Principle 6 ('Realize measurable benefits') and Principle 4 ('Align with priorities') from the governance framework, arguing that non-profit organizations do not need formal business alignment or quantifiable metrics. According to MSP guidance on tailoring, how should the consultant respond?
A regional hospital authority is planning a 4-year transformation to replace its clinical diagnostics infrastructure across 12 facilities. The engineering team proposes a single 'big bang' launch at the end of Year 4, keeping all new systems offline until all 12 hospitals can switch over simultaneously. What primary operational risk does this create, and how does MSP Principle 7 ('Bring pace and value') address it?
Which statement accurately describes the three core characteristics of all 7 principles in the MSP 5th edition framework?