Support Organizational Change

Introduction

This lesson covers task 7 of the Business Environment domain in the July 2026 PMP Examination Content Outline: assess organizational culture, evaluate the impact of organizational change on the project, and evaluate and deliver the required actions using change management models. The Business Environment domain carries 26% of the exam.

Most projects exist to change something: a process, a system, a structure, a way of serving customers. Yet the best product delivered on time can fail if the people who must use it do not adopt it. Conversely, organizational changes that are not initiated by the project, such as a merger, a reorganization, or a new strategy, can alter the project's scope, sponsor, priorities, and team. The exam tests both directions. Be careful to separate this task from task 3, "manage and control changes", which covers changes to the project's own scope, schedule, and cost through the change control process. Here the subject is organizational change and people.

After this lesson you will be able to assess a culture, analyze how a change affects a project, choose among change management models (ADKAR, Kotter, Lewin, Bridges), build an adoption plan, and handle resistance.

Learning objectives

• Explain how organizational culture and structure affect a project.
• Assess culture and change readiness with practical methods.
• Evaluate the impact of an organizational change on project scope, schedule, cost, risks, and stakeholders.
• Describe and apply the main change management models.
• Plan and deliver actions: communication, training, sponsorship, reinforcement.
• Manage resistance and measure adoption.
• Distinguish organizational change management from project change control.

1. Organizational culture and why it matters

Culture is the set of shared values, beliefs, norms, and behaviors that shape how things get done. It is rarely written down, but it decides whether a new way of working will be embraced or quietly ignored.

Elements of culture that affect a project include:

• Decision making: centralized or distributed, fast or consensus-driven.
• Attitude to risk: risk-averse or experimental.
• Communication style: formal and hierarchical, or open and direct.
• Authority and structure: functional, matrix, or projectized organization.
• Attitude to authority and hierarchy, particularly in multinational teams.
• Work ethic and working hours, local holidays, and legal frameworks.
• Appetite for change: history of previous changes, and whether they succeeded.

Organizational structures in brief

Assessing culture and readiness

You cannot adapt to a culture you have not observed. Practical methods:

• Interviews and listening sessions with sponsors, managers, and front-line staff.
• Surveys that measure change fatigue, trust in management, and understanding of the vision.
• Observation of how decisions are made and who really influences them (informal networks).
• Analysis of history: previous change programs, their outcome, and the stories told about them.
• Review of artifacts: policies, org charts, performance metrics, rewards. What the organization rewards is what it values.
• Readiness assessment: compares the demands of the change with the capacity of the people and processes, covering awareness, desire, knowledge, ability, and reinforcement.

The result should be actionable: where support is strong, where resistance is likely, and what kind of communication and leadership style will work.

Worked example: matching the approach to the culture

Scenario. A utilities company with 4,000 employees wants to replace its paper-based field inspection process with a tablet application. The project team plans a "big bang" launch to all 600 field technicians on one date. Interviews reveal that technicians distrust head-office initiatives because the last system, 5 years ago, was withdrawn after 8 months and cost them overtime. Supervisors are respected and informal opinion leaders exist in each depot. The CFO wants the savings in 12 months.

Step 1: read the culture. Low trust in head office, strong local loyalty, change fatigue from a failed history, and high influence of supervisors.

Step 2: assess the impact on the project. A big-bang launch has high adoption risk. A rushed schedule would increase rework and support costs, hurting the benefits case.

Step 3: choose actions. Phase the rollout by depot (pilot with 2 depots), recruit supervisors and respected technicians as champions, involve technicians in design testing, add on-the-job coaching, and give honest messages about what failed last time and what is different now.

Step 4: adjust the plan. Update the schedule, the resource plan (champion time, trainers), the communication plan, and the risk register through change control. Explain to the CFO that early benefits come from the pilot and that a failed launch would cost more.

Why not the alternatives? Forcing the date ignores the evidence; sending only an e-mail announcement does not build trust; delaying the whole project indefinitely loses the opportunity.

2. Impact of organizational change on the project

Organizational change may begin outside the project. Examples: a merger, a new CEO and strategy, a cost-cutting program, a reorganization, a regulatory shift, outsourcing, or a new technology platform. The project manager's duty is to detect it early, analyze it, and respond through governance.

What can be affected

• Business case and benefits: the project may no longer be aligned with strategy.
• Scope and requirements: new priorities may add, remove, or alter deliverables.
• Schedule and budget: funding freezes, delays in decisions.
• Resources: team members reassigned, new reporting lines, loss of key people.
• Stakeholders: new sponsors or executives, changed power and interests.
• Governance: different approval paths, a new PMO.
• Risk profile: new threats and opportunities.

The analysis steps

1. Understand the change: what, why, when, who is affected, who sponsors it.
2. Analyze impact on the project using the dimensions above; involve the sponsor and key stakeholders.
3. Update the stakeholder register and engage new stakeholders quickly.
4. Identify options: continue as is, adjust, pause, accelerate, or recommend termination.
5. Process changes through integrated change control when baselines are affected, with a clear recommendation.
6. Communicate the decision and its reasons.

Worked example: a merger mid-project

Scenario. Your company is 7 months into a 15-month, 2,400,000 CRM project. It announces a merger with a competitor that already uses a different CRM. The sponsor says to "keep going for now". Two of your eight developers are reassigned to integration work. Procurement has frozen new purchase orders for 60 days.

Step 1: assess the impact. Resource loss (25% of developers), a procurement freeze that may block licences, and strategic uncertainty about whether the new CRM will be retained.

Step 2: quantify. The lost capacity could add around 8 weeks; the licence purchase planned in month 9 is at risk; 1,400,000 of the budget is already spent or committed.

Step 3: prepare options for the sponsor. (a) Continue with a reduced scope and replacement staff. (b) Pause non-critical work until the merger decision, preserving the sunk work. (c) Recommend closing early if the merged strategy chooses the other CRM.

Step 4: act through governance. Document the risk, request a decision date from the steering committee, submit change requests for the staffing and schedule effects, update the risk register, and tell the team honestly what is known.

Why not the alternatives? Continuing silently hides growing risks; stopping on your own authority exceeds your role; asking the team to absorb the loss with overtime creates a quality and morale problem.

3. Change management models

Models give structure to the human side of change. The exam does not usually require you to recite a model, but it expects you to recognize the logic and apply the principles. Know these four well.

ADKAR (Prosci)

An individual-level model: the change succeeds when each person passes through five stages.

ADKAR is useful for diagnosing where adoption is stuck: if training is excellent but people do not use the tool, the gap is Desire or Reinforcement, not Knowledge.

Kotter's eight steps

An organization-level model: (1) create urgency, (2) build a guiding coalition, (3) form a strategic vision, (4) enlist a volunteer army, (5) enable action by removing barriers, (6) generate short-term wins, (7) sustain acceleration, (8) institute change in the culture. It stresses leadership, vision, and early wins.

Lewin's three stages

Unfreeze (prepare people to let go of the current state), change (move to the new state), refreeze (anchor the new state in habits, policies, and rewards). Simple and helpful for explaining the logic to executives.

Bridges' transition model

Distinguishes change (the external event) from transition (the internal psychological process): ending (letting go), neutral zone (confusion and experimentation), new beginning. It reminds the manager that people need time and support in the neutral zone.

Choosing and combining

In practice combine them: Kotter to mobilize leaders, ADKAR to track individuals, Bridges for emotional support. Tailor to size, culture, and urgency.

4. Planning and delivering the required actions

A change adoption plan converts the analysis into work that is part of the project plan. Key components:

1. Sponsorship: the most important success factor. An active, visible sponsor explains the "why", removes barriers, and holds managers accountable.
2. Stakeholder and impact analysis: which groups are affected, how much (low to high), and what must change in their daily work.
3. Communication plan: the right message, in the right channel, from the right person (often the direct manager), repeated and two-way.
4. Training and support: content by role, timing close to use, floor-walkers and help desks, quick reference guides.
5. Champions network: respected peers who test, explain, and give feedback.
6. Resistance management: listen, find the cause, address legitimate concerns.
7. Reinforcement: align incentives, performance goals, and procedures with the new way; retire the old system.
8. Measurement: adoption and benefit indicators, reviewed regularly.

Managing resistance

Resistance is information, not an enemy. Common causes and appropriate responses:

Do not label people as "difficult" before understanding the reason. Do not force adoption by punishment as a first resort.

Measuring adoption and success

Useful indicators: usage rates, process compliance, time to proficiency, error rates, support tickets, survey scores on readiness and satisfaction, and benefits realized against the business case. Compare against targets and adjust. Adoption is part of value: a delivered but unused product produces no benefits.

Worked example: diagnosing stuck adoption with ADKAR

Scenario. Three months after a new expense-reporting tool launched, only 38% of 1,200 employees use it; the target was 85%. Training attendance was 92% and satisfaction with the training was 4.5 out of 5. Interviews show people find the old spreadsheet faster and managers still approve the spreadsheet.

Step 1: map to ADKAR. Awareness is fine, Knowledge is fine (training worked). Desire is weak (the old way is easier), Ability is partial (the app is slow on mobile), Reinforcement is absent (managers accept both).

Step 2: choose actions. Fix the mobile performance (Ability), set a cut-off date for the old spreadsheet and have finance reject it (Reinforcement), explain benefits like faster reimbursement (Desire), and brief managers.

Step 3: measure. Track weekly adoption and reimbursement time.

Why not the alternatives? More training addresses a gap that does not exist; blaming employees ignores system and management causes; ending the project ignores recoverable benefits.

5. Change in agile and hybrid contexts

Agile development delivers value in small increments, which spreads the change over time: users see frequent small changes rather than one big one. This can reduce shock but may increase fatigue if users must relearn often. Good practice: involve users in reviews, release to pilot groups first, align communication with release cadence, and include adoption items in the backlog (training, migration of users, documentation). The definition of done may include "users trained and support ready". Culture matters especially: a command-and-control organization may struggle with self-organizing teams, and the project manager may need to coach leaders about their role as servant leaders.

6. Organizational change versus project change control

7. Common pitfalls and exam tips

• Pitfall: treating the change as a technology matter. Technical delivery without adoption planning produces no value.
• Pitfall: communicating once. One announcement is not communication.
• Pitfall: ignoring culture. The same approach does not work in every organization.
• Pitfall: no sponsor involvement. Without sponsorship, change efforts stall.
• Pitfall: confusing the two meanings of change. Read the question: "change request" means change control; "organization is restructuring" means change management.
• Pitfall: celebrating too early. Without reinforcement people drift back.

Exam tip: When the question describes people not using a delivered product, look for answers that analyze the reason (awareness, desire, ability, reinforcement) and engage sponsors and managers. Retraining everyone is rarely the best first step unless the data shows a knowledge gap.

Exam tip: When an external organizational change affects the project, the best sequence is usually: assess the impact, consult the sponsor and key stakeholders, update the plans through change control, and communicate. Stopping the project alone or ignoring the change are almost always wrong.

Comparison: responses by situation

Mini case study

Case. A hospital network launches an electronic medication system across 14 wards over 10 months (budget 1,800,000). The pilot ward shows 90% adoption, but ward 3 reaches only 40% after 6 weeks. Nurses say that scanning every dose adds 10 minutes per round and that the ward manager told them to "do the paper chart as backup". Meanwhile the hospital's board announces a restructuring that will merge wards 5 and 6 and move the clinical director who sponsors the project to another site in 3 months. The go-live of the next four wards is in two weeks.

Question. What do you do?

Solution (commented).

1. Diagnose ward 3. Awareness and Knowledge exist (the pilot worked). The gap is Ability (scanning workflow slow) and Reinforcement (the manager allows paper). Interview nurses to confirm and observe a medication round.
2. Fix causes. Work with nurses and the vendor to reduce the scan steps, adjust workflows, add floor-walkers for two weeks, and meet the ward manager to align on the cut-off date for paper with the clinical director's support.
3. Assess the restructuring impact. Merging wards 5 and 6 changes the rollout plan, user counts, and training schedule; the sponsor's move threatens decision speed and political backing.
4. Engage governance. Ask the clinical director to name a successor sponsor and brief them; update the stakeholder register; submit change requests for the revised rollout sequence.
5. Adjust the go-live. Consider delaying go-live for the next four wards by one or two weeks, until the fixes are verified, and use the pilot ward's nurses as champions.
6. Communicate openly. Share adoption data and the fixes with nurses; tell staff in wards 5 and 6 what the merger means for the rollout.
7. Measure. Weekly adoption by ward, scan time per round, medication errors, nurse satisfaction.
8. Do not blame nurses, force adoption by threats, ignore the restructuring, or push the schedule regardless of patient-safety risk.

Key terms

• Organizational culture: shared values and behaviors that shape how work is done.
• Change readiness: the degree to which people and processes can absorb a change.
• Organizational change management: the discipline of preparing and supporting people to adopt change.
• ADKAR: Awareness, Desire, Knowledge, Ability, Reinforcement.
• Kotter's eight steps: a leadership-based model of organizational transformation.
• Unfreeze-change-refreeze: Lewin's three-stage model.
• Transition: the psychological process people go through during a change (Bridges).
• Change champion: a respected peer who supports adoption.
• Sponsor: the senior person who provides resources and authority and champions the change.
• Resistance: a reaction to change that signals unmet concerns.
• Adoption: the degree to which people actually use the new way of working.
• Reinforcement: actions that make the change last.

Summary checklist

• I assess culture, structure, and readiness before choosing an approach.
• I detect organizational changes early and analyze their impact on scope, schedule, cost, resources, stakeholders, and risk.
• I take the options to the sponsor and process effects through change control.
• I recognize ADKAR, Kotter, Lewin, and Bridges and use them to diagnose and plan.
• I plan sponsorship, communication, training, champions, and reinforcement.
• I treat resistance as information and look for the cause.
• I measure adoption and benefits and adjust.
• I distinguish organizational change management from project change control.
• I adapt change actions to agile and hybrid delivery.

Official sources

• PMI, PMP Examination Content Outline (July 2026): https://www.pmi.org/-/media/pmi/documents/public/pdf/certifications/new-pmp-examination-content-outline-2026.pdf (opens in a new tab)
• PMI, About the new PMP exam: https://www.pmi.org/certifications/project-management-pmp/new-exam (opens in a new tab)
• PMI, Project Management Professional (PMP): https://www.pmi.org/certifications/project-management-pmp (opens in a new tab)
• PMI, Standards: https://www.pmi.org/standards (opens in a new tab)