Study guide
3.5 Organizational Change Management (OCM)
PRINCE2 7 Foundation Certification Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Key Concepts, Framework & Integrated Elements
1.1 PRINCE2 7 Method Overview & Project Context 1.2 Seven Performance Aspects & Delivery Approaches 1.3 Outputs, Outcomes, Benefits & Value Creation 1.4 Management Products vs Specialist Products 1.5 PRINCE2 Governance, Tailoring & Distinct Features
2 Chapter 2: The Seven PRINCE2 7 Principles
2.1 Principle 1: Continued Business Justification 2.2 Principle 2: Learn from Experience 2.3 Principle 3: Define Roles, Responsibilities and Relationships 2.4 Principle 4: Manage by Stages 2.5 Principle 5: Manage by Exception 2.6 Principle 6: Focus on Products 2.7 Principle 7: Tailor to Suit the Project
3 Chapter 3: The People Element in PRINCE2 7
3.1 Capable People & Organizational Culture 3.2 Project Teams & Team Dynamics 3.3 Leading Project Teams 3.4 Communication & Stakeholder Engagement 3.5 Organizational Change Management (OCM)
4 Chapter 4: The PRINCE2 7 Practices - Strategy, Organization & Planning
4.1 Business Case Practice 4.2 Organizing Practice & Project Management Team 4.3 Commercial & Stakeholder Aspects of Organizing 4.4 Plans Practice & Levels of Plans 4.5 Product-Based Planning Technique 4.6 Quality Practice & Quality Control
5 Chapter 5: The PRINCE2 7 Practices - Risk, Change & Progress Control
5.1 Risk Practice & Risk Management Approach 5.2 Issues Practice & Issue Management Approach 5.3 Change Control & Configuration Management 5.4 Progress Practice & Control Mechanisms 5.5 Management Reports & Logs/Registers 5.6 Sustainability & Digital Integration in Practices
6 Chapter 6: The PRINCE2 7 Processes - Pre-Project & Initiation
6.1 Overview of PRINCE2 7 Process Model & Flow 6.2 Starting Up a Project (SU) Process 6.3 Directing a Project (DP) Process 6.4 Initiating a Project (IP) Process 6.5 Assembling the Project Initiation Documentation (PID)
7 Chapter 7: The PRINCE2 7 Processes - Delivery, Boundary & Closure
7.1 Controlling a Stage (CS) Process 7.2 Managing Product Delivery (MP) Process 7.3 Managing a Stage Boundary (SB) Process 7.4 Closing a Project (CP) Process 7.5 End-to-End PRINCE2 7 Process Flow & Exam Walkthrough
3.5 Organizational Change Management (OCM)
Key Takeaways Explain This Topic AI
Organizational Change Management (OCM) bridges the critical gap between technical project delivery (outputs) and operational business adoption (outcomes and benefits realization).
Projects create outputs (deliverables), but business value is achieved only when people adopt and embed changes into Business-as-Usual (BAU) operations to achieve outcomes and benefits.
PRINCE2 7 explicitly integrates OCM into management products, ensuring change readiness, stakeholder buy-in, and capability building are planned alongside technical tasks.
Classical change models (such as ADKAR, Kotter's 8 Steps, and Lewin's Freeze-Change-Unfreeze) inform PRINCE2 OCM activities.
The PID Change Management Approach defines how the organization will move from current to target state so outcomes and benefits can be realized.
Last updated: July 2026
- 3.5 Organizational Change Management (OCM)
- Introduction: Bridging Technical Delivery and Business Realization
A common point of failure in project management is delivering a technical output on time, within budget, and to specification—only for the organization to reject or fail to adopt it. A state-of-the-art enterprise software system is worthless if staff continue using legacy spreadsheets.
Recognizing this gap, PRINCE2 7 incorporates Organizational Change Management (OCM) as an essential component of the People element. OCM is the structured approach to transitioning individuals, teams, and organizations from a current state to a desired future state to achieve intended business outcomes and benefits.
The Value Chain: Outputs, Outcomes, and Benefits
To master OCM in PRINCE2 7, candidates must understand the fundamental distinction between Outputs , Outcomes , and Benefits : +------------------+ +------------------+ +------------------+
- | OUTPUT | ======> | OUTCOME | ======> | BENEFIT |
- | Deliverable Built| Change | Operational Use | Realized| Measurable Value |
- | by Project | Adopted | by Business | Value | Realized by Org |
- +------------------+ +------------------+ +------------------+
- Example: New IT Example: Staff Example: 20% Cost
- CRM Software Using CRM Daily Reduction & Sales
- System Installed to Log Leads Growth of 15%
Element Definition Responsible Role Timing
Output Any specialist deliverable produced by the project (e.g., a new system, building, training course, process document). Project Manager (with Team Managers delivering specialist products) (delivered via Project Manager) Produced during project stage execution.
Outcome The change in operational behavior or capability achieved when business operations utilize the project's outputs. Senior User & Operational Business Managers Achieved during transition and operational use.
Benefit The measurable improvement resulting from an outcome that is perceived as an advantage by one or more stakeholders. Senior User & Executive Realized during and post-project (tracked via Benefits Management Approach).
Integrating OCM into PRINCE2 Governance and Lifecycle
OCM is not an add-on activity executed at the end of a project; it must be embedded across the PRINCE2 process lifecycle and management products:
The Business Case : Must account for OCM costs (e.g., training, change management consultants, communications campaigns) and include adoption risks alongside technical risks.
The Project Plan & Stage Plans : Incorporate explicit OCM work packages—such as stakeholder readiness assessments, training delivery, pilot trials, and user support frameworks—alongside technical development milestones.
The Communication Management Approach : Integrates OCM messaging designed to build awareness, desire, and commitment among affected staff.
The Benefits Management Approach : Defines how post-project operational adoption will be measured and sustained to confirm that outcomes translate into realized benefits.
Core OCM Frameworks in PRINCE2 Context
PRINCE2 7 synthesizes established organizational change models to guide project leaders:
1. The Prosci ADKAR Model
ADKAR outlines the five individual building blocks required for successful organizational change:
Awareness : Understanding why the change is necessary.
Desire : The personal decision and motivation to support and participate in the change.
Knowledge : Understanding how to change (training, skills acquisition).
Ability : Demonstrating the capability and performance in the new operational state.
Reinforcement : Mechanisms to sustain the change (incentives, recognition, ongoing support).
2. Kotter's 8-Step Change Model
John Kotter's strategic change framework aligns smoothly with PRINCE2 stage-gate governance: 1. Create Urgency ======> 2. Build Coalition ======> 3. Create Vision
- | |
- 4. Communicate Vision <==== 5. Empower Action <==== 6. Short-Term Wins
- |
- 7. Consolidate Change ======> 8. Anchor in Culture
Steps 1-3 : Align with Starting up a project and Initiating a project (establishing business mandate, executive sponsorship, and Project Brief).
Steps 4-6 : Align with stage execution (communication, removing operational barriers, delivering early stage releases).
Steps 7-8 : Align with Managing a stage boundary , Closing a project , and post-project operational transition.
3. Lewin's Change Management Model
Kurt Lewin's classic three-stage model simplifies organizational transition:
Unfreeze : Breaking down existing mindsets and operational habits; preparing the organization for change.
Change (Transition) : Moving to the new operational state through training, new processes, and trial runs.
Refreeze : Anchoring new behaviors into corporate culture, policies, and standard operating procedures to prevent backsliding.
Managing Resistance and Fostering Change Readiness
Resistance to change is a natural human reaction driven by fear of job loss, loss of status, perceived increase in workload, or lack of trust in leadership.
Strategies for Overcoming Resistance
Early Engagement : Involve operational end-users in requirement gathering and solution design rather than imposing finished products upon them.
Active Sponsor Engagement : Ensure the Executive and Senior User visible champions demonstrate active support and model new behaviors.
Change Champions Network : Nominate peer leaders within operational teams to act as local advocates, answering questions and coaching colleagues.
Targeted Training & Support : Provide adequate training and post-go-live hypercare support to build confidence and reduce anxiety.
Transitioning to Business-As-Usual (BAU) and Sustaining Change
The final test of OCM is the smooth handover of project deliverables to operational ownership during the Closing a project process.
Key Transition Activities
Operational Readiness Reviews : Assessing whether operational teams possess the knowledge, capacity, and support structures to receive the output.
Handover of Residual Risks & Issues : Documenting open risks and maintenance requirements for ongoing operational management.
Decommissioning Legacy Systems : Removing old tools and legacy workflows to lock in the new operational method ("refreezing").
Post-Project Benefit Reviews : Conducting scheduled reviews defined in the Benefits Management Approach to verify that operational outcomes continue to yield expected business benefits.
Change Management Approach (PID Management Product)
PRINCE2 7 requires a Change Management Approach as part of the PID. This is a People-element management product (not the Issues practice's change-control procedure).
The Change Management Approach defines:
The current state , any interim states , and the target organizational state required for the project to meet its objectives
How the business will transition people, processes, and ways of working from current to target state
Skills/capabilities needed, impacted organizational areas, stakeholder relationships to consider, and resources for transition
Responsibilities for organizational change activities and how readiness/adoption will be measured
Exam distinction:
Product Focus
Change Management Approach (People / PID) Organizational transition & adoption (people affected by the project)
Issue Management Approach (Issues practice / PID) How project issues, RFCs, and off-specifications are controlled
Communication Management Approach (People / PID) Stakeholder communication methods, frequency, and responsibilities