5.7. Support Organizational Change

💡 First Principle: A project's deliverable can be technically perfect and still fail to create value if the organization around it isn't ready to adopt it — this task tests whether you actively assess organizational readiness and manage the change impact, rather than treating adoption as automatic once the deliverable ships.

Enablers: assess organizational culture, and evaluate the impact of organizational change on the project (and determine required actions).

This is the most compact task in the entire ECO (2 enablers) — but it sits at the intersection of the project and the receiving organization, and questions testing it often look like a project-management question on the surface while actually testing whether you recognized an organizational-change-management gap as the real root cause.

Technical acceptance is not adoption

Acceptance tests prove the deliverable works; they say nothing about whether anyone uses it. A team that declares success at deployment and finds most staff still on the old workaround three months later measured the wrong finish line. Projects deliver change, and change that is not adopted produces none of the intended benefits — which is why a PM needs working knowledge of organizational change management even though leading it is not the PM's primary role. When a finance team says it will keep its spreadsheets "until the new system proves itself," the response is to assess their concerns and working culture, then plan adoption support such as targeted training and an agreed cut-over date.

Assess culture and readiness properly

A new tool that automates work for a team known to resist process change, followed by very low adoption, points to a missing assessment of that team's culture and readiness. Two ways the assessment itself goes wrong are tested:

• Asking only leaders. Department heads say their teams are ready; frontline staff later reveal concerns the leaders never knew about. Probe the people whose daily work changes.
• Treating the organization as one audience. Three departments with different prior exposure to similar changes need readiness assessed separately and support tailored to each.

From impact to proportional action

Evaluating impact means asking how far the change disrupts established habits, workflows and relationships — then planning actions proportional to that disruption: tailored training, a phased rollout, direct engagement with the affected department. Support spans both sides of go-live.

⚠️ Exam Trap: Treating launch as the end of the project's change responsibility. When adoption is still low months later, the missing piece is ongoing monitoring of adoption after go-live, with support adjusted to what that monitoring shows.

Who leads the change, and how people come along

The project team implements the technology, but senior leadership and designated change sponsors or champions in the business lead and champion the broader organizational change. Respected, enthusiastic individuals inside an affected department are worth engaging as informal champions who model and advocate the change among peers, complementing formal communication and training. For resistant employees in a digital transformation, the most important piece is a communication plan that makes the What's In It For Me (WIIFM) clear and gives people channels for feedback. Treat resistance as information: find its root cause, listen, involve resistant stakeholders in decisions, and answer legitimate fears transparently.

Organizational change can also land on the project itself. When a reorganization brings in a new sponsor who wants more than a verbal status update, walk them through the current and previous status reports so they see the trajectory, not just today's snapshot.

Two change models the exam names

⚠️ Exam Trap: Diagnosing low adoption of a completed deliverable as a training gap or a communication gap alone, when the scenario's real signal is organizational culture resistance that wasn't assessed or managed.