Study guide
1.6 How the Principles Are Built Into Each Theme
MSP Foundation Managing Successful Programmes
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Programme Management Concepts & MSP Overview
1.1 What is a Programme? 1.2 The MSP Framework Structure 1.3 Outputs, Capabilities, Outcomes, and Benefits 1.4 The 3 Lenses, Enterprise Agility & the Programme Environment 1.5 Programme Strategy, Governance & the PDCA Cycle 1.6 How the Principles Are Built Into Each Theme
2 Chapter 2: The 7 MSP Principles
2.1 Lead with Purpose & Collaborate Across Boundaries 2.2 Deal with Ambiguity & Align with Priorities 2.3 Deploy Diverse Skills & Realize Measurable Benefits 2.4 Bring Pace and Value & Tailoring MSP Principles
3 Chapter 3: Organization Theme & Governance Roles
3.1 Programme Governance Structure 3.2 Senior Responsible Owner (SRO) & Programme Manager 3.3 Business Change Manager (BCM) & Programme Office 3.4 Stakeholder Engagement Approach
4 Chapter 4: Design Theme & Target Operating Model
4.1 The Design Theme & Vision 4.2 Target Operating Model (TOM) 4.3 Benefits Definition & Mapping
5 Chapter 5: Justification Theme & Business Case
5.1 Purpose of Justification Theme 5.2 The Programme Business Case 5.3 Funding & Financial Management
6 Chapter 6: Structure Theme & Delivery Planning
6.1 Structure Theme & Delivery Strategies 6.2 The Programme Plans & the Delivery Plan 6.3 Resource & Dependency Management 6.4 Pace, Multimodal Delivery & Landing Points
7 Chapter 7: Knowledge Theme & Information Management
7.1 Knowledge Theme Fundamentals 7.2 Information Management & Digital Assets 7.3 Programme Lessons & Communities of Practice
8 Chapter 8: Assurance & Decisions Themes
8.1 Assurance Theme & The Three Lines of Defence 8.2 Integrated Assurance Strategy 8.3 Decisions Theme & Risk Management 8.4 Issue Resolution & Decision Registers 8.5 Data Gathering, Reporting & Options Analysis
9 Chapter 9: Programme Lifecycle: Identification & Design Processes
9.1 Process 1: Identify the Programme 9.2 Process 2: Design the Outcomes 9.3 Process 3: Plan Progressive Delivery
10 Chapter 10: Programme Lifecycle: Delivery & Embedding Processes
10.1 Process 4: Deliver the Capabilities 10.2 Transition Management 10.3 Process 5: Embed the Outcomes
11 Chapter 11: Programme Lifecycle: Evaluation & Closure Processes
11.1 Process 6: Evaluate New Information 11.2 Tranche Reviews & Gate Decisions 11.3 Process 7: Close the Programme
1.6 How the Principles Are Built Into Each Theme
Key Takeaways Explain This Topic AI
The principles are not a separate chapter of MSP — they are built into governance through the themes, and every theme has a defined relationship with every principle.
Organization is the theme through which "collaborate across boundaries" and "deploy diverse skills" are enacted, because both are ultimately questions of who is in the structure and how they work together.
Design carries "lead with purpose" and "realize measurable benefits", because the vision and the benefits map are where purpose and measurability are made concrete.
Justification carries "align with priorities", since the business case is the mechanism that keeps the investment tied to current corporate strategy.
Structure carries "bring pace and value" and "deal with ambiguity" through tranches, landing points, and rolling-wave planning.
Last updated: September 2026
1.6 How the Principles Are Built Into Each Theme
Note
A directly examined relationship : For every one of the seven themes, the syllabus contains an assessment criterion asking you to describe the key relationships between that theme and the principles. The chain to remember is: principles are built into programme governance through the themes, and enacted through the processes . The themes are how a principle stops being a slogan and becomes a control.
Every principle touches every theme to some degree. What follows identifies, for each theme, the principles it most directly enacts and the specific mechanism through which it does so.
Organization
Principle How the Organization theme enacts it
Lead with purpose Establishes the SRO as a single, named, accountable leader rather than a committee, so that purpose has an owner
Collaborate across boundaries Builds cross-organizational governance — the sponsoring group and programme board span the investing organizations, not one department
Deploy diverse skills Defines complementary roles (SRO, programme manager, BCM, programme office) so that strategic, delivery, and operational-change expertise are all represented
Align with priorities Places the sponsoring group, which owns corporate priorities, at the top of the delegation chain
Deal with ambiguity Sets risk appetite and delegated tolerances so decisions can be made without certainty
The Organization theme is where collaborate across boundaries and deploy diverse skills primarily live, because both are ultimately questions of who is in the structure and how they are expected to work together.
Design
Principle How the Design theme enacts it
Lead with purpose The vision statement is the articulation of purpose that every later decision is judged against
Realize measurable benefits Benefit profiles and the benefits map require each benefit to have an owner, a measure, and a baseline before delivery starts
Deal with ambiguity The target operating model is progressively elaborated — near tranches in detail, far tranches at concept level
Align with priorities The gap between current and future state is defined against corporate strategy, not against departmental wish lists
Design is where lead with purpose and realize measurable benefits are made concrete: a vision without a benefits map is rhetoric, and a benefits map without a vision is a spreadsheet.
Justification
Principle How the Justification theme enacts it
Align with priorities The business case is re-validated at each tranche boundary against current strategy, so drift is detected rather than accumulated
Realize measurable benefits Benefits are the numerator of the investment case; unmeasurable benefits cannot justify anything
Bring pace and value Tranche-based funding releases capital only as value is demonstrated
Deal with ambiguity Optimism bias, financial contingency, and options analysis are explicit responses to not knowing
Justification is the principal home of align with priorities , because the business case is the mechanism that ties continued investment to continuing strategic fit.
Structure
- Principle How the Structure theme enacts it
- Bring pace and value Tranches and landing points deliver usable value early rather than at the end
- Deal with ambiguity Rolling-wave planning commits detail only where detail is knowable
- Realize measurable benefits The benefits realization plan schedules measurement, not just delivery
- Deploy diverse skills The resourcing approach acquires the mix of skills each tranche actually needs
- Collaborate across boundaries Dependency management coordinates work owned outside the programme
Structure is where bring pace and value becomes operational, because pace is a planning decision bounded by organizational capacity and ability.
Knowledge
Principle How the Knowledge theme enacts it
Deal with ambiguity Each tranche converts uncertainty into evidence, so later decisions rest on data rather than assumption
- Deploy diverse skills Communities of practice spread scarce expertise instead of trapping it in one team
- Collaborate across boundaries Lessons and knowledge are shared across organizational and supplier boundaries
- Bring pace and value Reusing what already works removes rework, which is the cheapest source of pace available
- Lead with purpose Information integrity ensures leaders are steering on a true picture
Knowledge is the theme that makes deal with ambiguity survivable across tranches: ambiguity is reduced by learning, not by planning harder.
Assurance
Principle How the Assurance theme enacts it
Lead with purpose Assurance tests whether delivery still serves the vision, not merely whether milestones were hit
- Realize measurable benefits Benefits assurance checks that measurement is real and baselines exist
- Deal with ambiguity Independent review surfaces the risks that delivery optimism conceals
- Align with priorities Assurance at multiple levels connects programme performance to corporate expectations
Collaborate across boundaries Integrated assurance coordinates internal, corporate, and external reviewers into a single plan
The three lines of defence are the structural expression of lead with purpose : leadership requires an honest picture, and self-assessment alone cannot supply one.
Decisions
Principle How the Decisions theme enacts it
Deal with ambiguity Decision points, options analysis, and risk responses are designed for choosing without certainty
Bring pace and value Delegated authority reduces decision latency, which is one of the most common causes of lost value
- Align with priorities Escalation routes strategic decisions to the body that owns the priorities
- Realize measurable benefits Data gathering and reporting keep benefits visible in every decision
Lead with purpose The decision register records why choices were made, preserving intent across leadership changes
Decisions is the theme through which deal with ambiguity is finally acted on: the other themes reduce or describe uncertainty, but this is where the programme commits.
Using This in the Exam
Two question shapes recur:
"Which theme primarily supports principle X?" — work from the mechanism. If the answer involves a role or a governance body, it is Organization. If it involves the vision, TOM, or benefits map, it is Design. If it involves money or continued justification, it is Justification. If it involves tranches, pace, or plans, it is Structure. If it involves lessons or information, it is Knowledge. If it involves independent review, it is Assurance. If it involves a choice, a risk response, or an issue, it is Decisions.
"How does theme Y reflect the principles?" — the safe general answer is that the theme provides the governance mechanism (roles, approaches, plans, registers) through which the principle is applied continually across the lifecycle. Options claiming a theme replaces a principle, or that principles apply only to certain themes, are wrong: the principles are universal and apply to every theme.
Caution
Common trap — principles are not tailorable : The themes and processes are tailored to context. The principles are not. An option describing an organization that "tailored out" a principle because it did not suit their culture is describing a programme that is no longer following MSP.