Study guide
5.1 Organizational Change Management: Definition, Stakeholders and Culture
PRINCE2 Agile Foundation Version 2
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: The Version 2 Exam & PRINCE2 Agile Essentials
1.1 About the PRINCE2 Agile Foundation (Version 2) Exam 1.2 What PRINCE2 Agile Is and How to Blend Project Management with Agile 1.3 PRINCE2 Agile Key Terms You Must Be Able to Define
2 Chapter 2: Agile and the Agile Mindset
2.1 What Agile Is, Why It Is Needed, and Agile in Projects and BAU 2.2 Being Agile vs Doing Agile, and the Benefits of Both 2.3 The Agile Mindset and the Agile Onion 2.4 The Agile Manifesto and Popular Agile Approaches
3 Chapter 3: Key Agile Concepts and Techniques
3.1 User Stories, Agile Estimation, and the Definitions of Ready and Done 3.2 MVP, Burn Charts, Workshops and Agile Events
4 Chapter 4: PRINCE2 Project Management Foundations
4.1 Projects, Project Management and the Seven Performance Targets 4.2 Project Contexts and the Five Integrated Elements 4.3 The Seven PRINCE2 Principles 4.4 Agile Scaling and Agile Transformation Success Factors
5 Chapter 5: People and Organizational Change Management
5.1 Organizational Change Management: Definition, Stakeholders and Culture 5.2 How Agile Supports Change Management and How PRINCE2 Addresses People 5.3 Project Teams, Leading Effective Teams and Communication
6 Chapter 6: PRINCE2 Agile Essentials — Principles and Practices
6.1 How the PRINCE2 Principles Support the Agile Context 6.2 The Purpose of the Seven PRINCE2 Agile Practices
7 Chapter 7: The Practices (Part 1) — Business Case, Organization, Plans
7.1 The Business Case Practice in an Agile Context 7.2 The Organization Practice in an Agile Context 7.3 The Plans Practice in an Agile Context 7.4 Plans Artifacts and Techniques: Release Maps, Timeboxes and Estimation
8 Chapter 8: The Practices (Part 2) — Quality, Risk, Issues, Progress
8.1 The Quality Practice in an Agile Context 8.2 Quality Artifacts and Techniques: Ready, Done and Continuous Testing 8.3 The Risk Practice in an Agile Context 8.4 The Issues Practice in an Agile Context 8.5 The Progress Practice in an Agile Context 8.6 Progress Artifacts and Techniques: Burn Charts and Dashboards
9 Chapter 9: The Eleven PRINCE2 Agile Roles
9.1 Directing and Managing Roles 9.2 Delivery Roles: Coaches, Product Owner, Developer and Tester
10 Chapter 10: The Processes and Their Agile Workshops
10.1 The Purpose of the Seven PRINCE2 Agile Processes 10.2 Starting up a Project and Its Agile Workshops 10.3 Directing a Project and Its Agile Workshops 10.4 Initiating a Project and Its Agile Workshops 10.5 Controlling a Stage and Its Agile Workshops 10.6 Managing Product Delivery and Its Agile Workshops 10.7 Managing a Stage Boundary and Its Agile Workshops 10.8 Closing a Project and Its Agile Workshops
11 Chapter 11: The Wider Context, AI, and Exam Preparation
11.1 PRINCE2 Agile Beyond the Project Environment 11.2 How AI Can Support PRINCE2 Agile 11.3 Version 1 to Version 2: What Changed and Common Traps 11.4 Final Review and Exam-Day Strategy
5.1 Organizational Change Management: Definition, Stakeholders and Culture
Key Takeaways Explain This Topic AI
Organizational change management is the structured approach to moving people and the organization from the current way of working to the new one, so that the project's benefits are actually realized.
A stakeholder is anyone who is affected by, can affect, or perceives themselves to be affected by the change initiative.
The project delivers outputs; OCM is what turns those outputs into adopted outcomes and therefore into benefits.
Culture is the shared assumptions, values and behaviours of an organization, and it is the strongest single determinant of whether a change is adopted or quietly rejected.
OCM is a distinct discipline from change control: OCM manages people through change, while the issues practice controls changes to the project's baseline.
Last updated: August 2026
5.1 Organizational Change Management: Definition, Stakeholders and Culture
Quick summary: Organizational change management (OCM) is the structured approach to moving people and the organization from the current state to the desired future state, so that the change is actually adopted and the benefits are realized. A stakeholder is anyone affected by the change initiative. Culture decides whether the change survives contact with the organization.
Why OCM is in this syllabus at all
This is a Version 2 addition, and if you studied from older PRINCE2 Agile material you will not have seen it. It arrived with PRINCE2 7's people integrated element, and it sits inside learning outcome 1 — the 30% block.
The reason it matters is a gap that has existed in project management for decades. A project delivers outputs : a system, a process, a building, a policy. Outputs on their own change nothing. They have to be adopted — people have to use the system, follow the process, occupy the building — before they produce outcomes , and only outcomes produce benefits .
Outputs → adoption → outcomes → benefits
A project that delivers a flawless system nobody uses has produced a perfect output and zero benefit. OCM is the discipline that owns the arrow between output and outcome. It is the reason continued business justification can fail even when delivery succeeds.
Defining OCM
Organizational change management is the structured approach to transitioning individuals, teams and the organization from a current state to a desired future state, in order to realize the intended benefits of a change initiative.
Three features of that definition:
Structured. It is a planned discipline with its own activities, not goodwill and an all-staff email.
Individuals, teams and the organization. It operates at all three levels; a change can be understood by an individual and still be rejected by the organization's structures and incentives.
In order to realize benefits. OCM is not communications for its own sake. Its success measure is adoption, and therefore benefit realization.
Typical OCM activities: stakeholder analysis, impact assessment, communications planning, training and coaching, identifying and supporting change champions, surfacing and addressing resistance, and measuring adoption after go-live.
Stakeholders
A stakeholder is any individual, group or organization that is affected by, can affect, or perceives itself to be affected by the change initiative.
If a question asks which of the following is affected by the change initiative , the answer is stakeholder . Project roles such as project assurance, product owner or team coach are participants in the project — they hold defined project responsibilities. The general category of people affected by the change is the stakeholders.
Note the three clauses in the definition, all of which matter:
Affected by — the change alters their work, their role or their outcomes.
Can affect — they have the power to help or obstruct, whether or not they are affected themselves. A regulator, a union, an IT security function.
Perceives itself to be affected — perception is sufficient. A group that wrongly believes the change threatens it will behave exactly as though it did, so the perception must be addressed.
Stakeholder groups typically include: the people whose day-to-day work changes; their line managers, who must lead through the change; the sponsor and senior leaders, whose visible support is decisive; operational and support teams who will run the product afterwards; customers and end users; and external parties such as regulators, suppliers and partners.
Stakeholders are not a static list. They change as the project progresses, so stakeholder analysis is repeated rather than done once. The user groups defined and prioritized in the project canvas workshop are one concrete expression of this analysis.
Culture
Culture is the set of shared assumptions, values, norms and behaviours that determine how an organization actually works — as distinct from how its process documents say it works.
Culture is the most powerful single determinant of whether a change is adopted, because it governs the informal system, and the informal system is where the real decisions are made. Three ways it shows up:
Culture defeats process. If a documented process conflicts with what the culture rewards, the culture wins and the process is ignored. Publishing an agile way of working into a culture that punishes visible failure produces teams that report green until the deadline.
Culture determines what is sayable. This is where culture meets psychological safety. In a culture where challenging a senior person is career-limiting, transparency is unobtainable regardless of the tooling.
Culture is learned from behaviour, not statements. People read what leaders do, especially under pressure. A stated value of "quality first" is worth nothing if the first schedule squeeze produces an instruction to skip testing.
Because culture is so decisive, an OCM plan that ignores it addresses the visible layer only. Practically, that means understanding what the current culture rewards, identifying where the change conflicts with it, and enlisting leaders and champions who can model the new behaviour credibly.
OCM is not change control
This distinction is worth being explicit about, because the two share a word and sit in different parts of the syllabus.
- Organizational change management Change control (issues practice)
- Object People and the organization The project's baseline
Question Will the change be adopted? Should this alteration to what we agreed be approved?
- Owner Business change roles, senior user, sponsor Project manager, project board, change authority
- Where in the syllabus Learning outcome 1.4, people Learning outcome 2, the issues practice
- Success measure Adoption and benefit realization Baseline integrity and controlled decisions
Both are needed and they interact — a change request may arise precisely because adoption is going badly — but confusing them in an exam answer is a straightforward loss of a mark.