3.4 Leading Successful Change & Organizational Culture
Key Takeaways
- PRINCE2 establishes a rigorous value chain linking project outputs (deliverables), business outcomes (behavioral changes), and strategic benefits (measurable value).
- The Business Change Manager (BCM) plays a critical role bridging project delivery with operational adoption, ensuring the business is prepared to realize benefits.
- Established change frameworks—such as Kotter's 8-Step Process, the ADKAR model, and Lewin's Unfreeze-Change-Refreeze—provide structured guidance for guiding human transitions.
- Resistance to change is a natural human reaction to uncertainty, loss of competence, or perceived threats, requiring empathetic engagement rather than punitive discipline.
- PRINCE2 7 integrates sustainability and ethical culture as mandatory dimensions of project performance, holding leaders accountable to societal values.
3.4 Leading Successful Change & Organizational Culture
Practitioner Core Concept: Delivering a project on time, within budget, and to technical specifications does not guarantee success. If a state-of-the-art enterprise system is deployed but operational staff bypass it using legacy spreadsheets, the project has produced shelfware—consuming capital while delivering zero organizational value. PRINCE2 7 treats project delivery as the catalyst for organizational change. Project managers must lead beyond the product handover, ensuring that operational structures, human behaviors, and cultural values align to lock in strategic benefits.
The Value Chain: Outputs, Outcomes, and Benefits
The fundamental disconnect in troubled projects is confusing what the project builds with why the project was funded. PRINCE2 7 enforces a strict conceptual progression:
+--------------------------------------------------------------------------------+
| THE PRINCE2 VALUE REALIZATION CHAIN |
+--------------------------------------------------------------------------------+
| |
| PROJECT OUTPUT BUSINESS OUTCOME STRATEGIC BENEFIT|
| (Specialist Product) =====> (Operational Change)=====> (Measurable Value|
| |
| Example: Example: Example: |
| New Automated Cloud Dispatchers route 25% reduction in |
| Fleet Scheduling vehicles dynamically fuel expenditure |
| Software using real-time telematics and 40% drop in |
| delivery delays |
| |
| DELIVERY DOMAIN TRANSITION DOMAIN OPERATIONAL DOMAIN
| Accountability: Accountability: Accountability: |
| Project Manager / Business Change Manager / Project Executive / |
| Senior Supplier Senior User Corporate Mgmt |
+--------------------------------------------------------------------------------+
- Project Output: A specialist product created and handed over by the project (e.g., software, bridge, new medical diagnostic protocol).
- Business Outcome: The measurable change in business behavior, operational processes, or capability resulting from the operational utilization of the output.
- Benefit: The measurable improvement resulting from an outcome that is perceived as an advantage by the sponsoring organization (documented in the Business Case and tracked via the Benefits Management Approach).
- Dis-benefit: An outcome perceived as negative by one or more stakeholders (e.g., temporary drop in team productivity during system onboarding, redundancy costs).
Established Change Management Models in PRINCE2 Practice
To bridge the dangerous chasm between output handover and outcome adoption, project managers and business change managers leverage three foundational change frameworks.
1. Kurt Lewin's Three-Stage Change Model
Lewin conceptualizes organizational change as moving a system from one frozen state through a liquid transition to a stable refrozen state:
[UNFREEZE] [CHANGE / MOVE] [REFREEZE]
- Dismantle complacency. - Introduce new systems. - Institutionalize norms.
- Demonstrate why status quo - Train staff on new behaviors. - Decommission legacy tools.
is unsustainable. - Navigate uncertainty and - Align rewards & KPIs with
- Build executive urgency. operational dip. new processes.
- Unfreeze (During SU & IP): Establish why the current operational state cannot continue. Create psychological readiness for change.
- Change / Transition (During CS & MP): Deploy iterative releases, run pilot programs, and provide safe training environments. Expect temporary productivity dips.
- Refreeze (During CP & Post-Project): Lock in the change. Decommission old legacy systems so staff cannot revert to old habits. Update standard operating procedures (SOPs) and align corporate reward structures with the new baseline.
2. John Kotter's 8-Step Leading Change Process
Kotter's model maps exceptionally well to the PRINCE2 process lifecycle:
| Kotter Step | Objective & Operational Activity | PRINCE2 Alignment |
|---|---|---|
| 1. Create Urgency | Demonstrate the commercial, operational, or regulatory cost of inaction. | Starting up a Project (SU): Outlining the draft Business Case. |
| 2. Form Guiding Coalition | Assemble leaders with sufficient power, expertise, and credibility to drive change. | SU & IP: Appointing the Project Board (Project Executive, Senior User, Senior Supplier). |
| 3. Create a Vision | Define a clear, compelling picture of the post-change future state. | Initiating a Project (IP): Drafting the Project Brief and PID. |
| 4. Communicate the Vision | Broadcast the vision continuously across all available organizational channels. | IP & CS: Baselining and executing the Communication Management Approach. |
| 5. Remove Obstacles | Eliminate procedural roadblocks, disempowering managers, and siloed friction. | Controlling a Stage (CS): Managing issues, risks, and organizational impediments. |
| 6. Generate Short-Term Wins | Deliver visible, unambiguous early improvements to validate the investment. | CS & MP: Structuring stages to deliver early, demonstrable product releases. |
| 7. Consolidate Gains | Use momentum from early wins to tackle deeper systemic reforms. | Managing a Stage Boundary (SB): Reassessing Business Case and expanding scope. |
| 8. Anchor in Culture | Institutionalize changes into corporate DNA, succession planning, and promotion norms. | Closing a Project (CP): Handover to operational BAU and post-project reviews. |
3. Prosci's ADKAR Model (Individual Change Framework)
While Kotter addresses organizational architecture, the ADKAR model addresses the psychological progression of the individual employee:
- Awareness: Understanding why the change is necessary.
- Desire: The personal motivation to support and participate in the change.
- Knowledge: Understanding how to change (training and operational education).
- Ability: Demonstrating the capability to execute the new skills in daily operations.
- Reinforcement: Mechanisms to sustain the change and prevent backsliding.
Practitioner Exam Trap: When resistance occurs, inexperienced managers immediately schedule more training (Knowledge). In the ADKAR framework, providing Knowledge before establishing Awareness and Desire breeds cynicism and active resistance. If workers do not understand why a system is being replaced (Awareness) or fear it will cause redundancies (Desire), software training will completely fail.
Understanding and Overcoming Resistance to Change
Resistance to change is not malicious defiance; it is a natural, predictable psychological reaction to the threat of loss. Leaders must diagnose the root cause of resistance:
+--------------------------------------------------------------------------------+
| DIAGNOSING ROOT CAUSES OF USER RESISTANCE |
+--------------------------------------------------------------------------------+
| ROOT CAUSE | TYPICAL EMPLOYEE CONCERN |
| Loss of Autonomy & Control | "Management is imposing this without asking us"|
| Fear of Incompetence | "I was an expert in the old system; now I look |
| | like a fool who doesn't know what to click" |
| Workload Exhaustion | "I have to do my regular job PLUS learn this" |
| Lack of Trust / Broken Promises| "The last IT project was an unmitigated disaster"|
| Fear of Redundancy | "This automation is designed to eliminate my job"|
+--------------------------------------------------------------------------------+
Practical Strategies to Dismantle Resistance
- Co-Creation: Involve operational end users directly in Product Description drafting and user-acceptance test (UAT) design.
- Change Champions Network: Recruit respected frontline peers as "super-users" who provide peer-to-peer coaching and advocate for the system from within the operational ranks.
- Safe-to-Fail Sandbox Environments: Allow employees to practice on new systems without fear of corrupting live databases or facing performance penalties.
- Incentive Realignment: Transition operational KPIs away from legacy metrics and reward early adoption of the new workflows.
The Role of the Business Change Manager (BCM)
In PRINCE2 7, the Business Change Manager (BCM) represents the vital human bridge between the temporary project and permanent operational operations.
+-----------------------------------------------------------------------+
| THE BUSINESS CHANGE MANAGER (BCM) |
+-----------------------------------------------------------------------+
| |
| +---------------------------------------------------------------+ |
| | PROJECT BOARD (Senior User / Project Executive) | |
| +---------------------------------------------------------------+ |
| ^ |
| | (Ensures Benefit Feasibility) |
| v |
| +---------------------------------------------------------------+ |
| | BUSINESS CHANGE MANAGER (BCM) | |
| | - Defines desired operational outcomes | |
| | - Assesses operational readiness for transition | |
| | - Coordinates user training & support structures | |
| | - Owns post-handover benefits realization | |
| +---------------------------------------------------------------+ |
| ^ ^ |
| | (Receives Outputs) | (Drives Adoption) |
| v v |
| +------------------------+ +---------------------------+ |
| | PROJECT DELIVERY TEAM | | BUSINESS-AS-USUAL (BAU) | |
| | (Project Manager, | | (Operational Managers, | |
| | Team Managers) | | Frontline Workers) | |
| +------------------------+ +---------------------------+ |
+-----------------------------------------------------------------------+
- The BCM is frequently appointed from the permanent operational line hierarchy to work alongside or within the Senior User role on the Project Board.
- While the Project Manager is accountable for delivering project outputs, the BCM is accountable for embedding those outputs into operations to achieve outcomes and realize benefits.
- The BCM maintains the Benefits Management Approach post-closure, tracking whether forecasted operational gains materialize over subsequent quarters.
Aligning Project Culture with Sustainability, Ethics, and Societal Values
PRINCE2 7 broadens the definition of project performance. In addition to the classic six performance targets (Time, Cost, Quality, Scope, Risk, Benefits), PRINCE2 7 embeds Sustainability as an essential seventh project performance target.
+-----------------------------------------------------------------------+
| THE SEVEN PROJECT PERFORMANCE TARGETS IN PRINCE2 7 |
+-----------------------------------------------------------------------+
| 1. COST | 2. TIME | 3. QUALITY | 4. SCOPE |
|------------------+------------------+------------------+--------------|
| 5. RISK | 6. BENEFITS | 7. SUSTAINABILITY (NEW IN v7) |
+-----------------------------------------------------------------------+
The Human Dimension of Project Sustainability
Sustainability is not merely an environmental checklist; it encompasses the triple bottom line—People, Planet, Profit:
- Social Sustainability & Human Wellbeing: Protecting team members from burnout, excessive overtime, and unsafe physical or psychological environments. Ensuring fair labor standards across external supplier supply chains.
- Ethical Project Governance: Establishing transparent anti-corruption mechanisms, whistleblower protections, and honest reporting of technical debts.
- Environmental Responsibility: Minimizing carbon footprints during project execution, minimizing digital and physical waste, and embedding circular lifecycle disposal into final Product Descriptions.
A multinational retail bank completes a two-year digital core overhaul on schedule and £500,000 under budget. Six months after the project team disbands, corporate performance reports reveal that frontline branch tellers are actively avoiding the new cloud system, continuing to record customer loans on shadow desktop spreadsheets. Customer loan processing times have increased by 30%, and anticipated cost savings have failed to materialize. What fundamental failure occurred in this project?
An engineering enterprise is deploying an AI-driven predictive maintenance application for factory field engineers. The engineers are actively resisting adoption, claiming that management intends to use the software's location telemetry to cut maintenance jobs and micro-manage their work. The Business Change Manager decides to use Prosci's ADKAR framework to address this resistance. What step should the BCM execute first?
During the Closing a Project process for an automated logistics depot, the Project Manager and Business Change Manager are finalizing the operational handover to Business-as-Usual. In accordance with Kurt Lewin's Refreeze stage and PRINCE2 7 sustainability principles, what action must be taken regarding the legacy manual sorting conveyor belts and obsolete operational procedures?