# Organizational Change Management

A structured practice for helping an organization move from a current way of working to a desired state while managing operational and human consequences.

- Type: practice
- Domain: Market & business
- Level: Advanced
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/organizational-change-management/>)

## What it means

Organizational change management coordinates the people, process, governance, communication, training, and reinforcement needed to make a change workable and durable. It complements project delivery: installing a system or publishing a policy is an output, while changed behavior and improved organizational performance are outcomes.

## Why it matters

Adoption is shaped by incentives, authority, workload, identity, skills, local practices, and trust—not communication alone. Change management makes these conditions visible, prepares affected groups, and creates feedback and support mechanisms. It can reduce disruption while helping leaders distinguish resistance from legitimate evidence that the proposed change is flawed.

## When to use it

Apply it to changes that materially alter roles, workflows, decision rights, measures, tools, policies, or culture. The greater the number of affected groups, dependence on behavior, operating risk, or history of failed change, the more deliberate the approach should be.

## How it works

1. Clarify the intended outcomes, case for change, scope, constraints, sponsorship, and assumptions about affected work.
2. Map stakeholder groups, impacts, incentives, readiness, influence, accessibility needs, and likely sources of loss or benefit.
3. Co-design the future workflow and implementation with representative people rather than merely announcing a finished solution.
4. Sequence communication, manager support, training, documentation, pilots, transition capacity, and escalation routes around real work.
5. Measure behavior and outcomes, gather dissent safely, remove structural barriers, reinforce improvements, and adapt the change.

## A practical example

A company replaces annual purchasing approvals with a continuous procurement workflow. It maps changed responsibilities, pilots with two departments, trains managers using real cases, adjusts performance measures, staffs migration support, and tracks cycle time, policy exceptions, employee effort, and supplier delays.

## Where it breaks

No framework guarantees acceptance, and treating people as obstacles can make change coercive. Training cannot fix poor incentives, missing capacity, unsafe conditions, or a weak product. Change programs may also overemphasize compliance while ignoring whether the intended state produces better outcomes.

## Common mistakes

- Reducing change management to announcements and training sessions.
- Labeling disagreement as resistance without investigating causes.
- Measuring attendance or communications sent instead of behavior and outcomes.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/organizational-change-management/#visualization-organizational-change-management>)

## Sources

1. [What Is Change Management?](<https://www.prosci.com/change-management>) — Prosci · Professional change-management guide
2. [Organizational Change Management Guide and Resources](<https://www.ucop.edu/local-human-resources/resources/manager-resources/change-management/ucop-organizational-change-management-guide-resources.html>) — University of California Office of the President · Institutional change-management guidance

## Related topics

- [Stakeholder Map](<https://wiki.soroush.uk/topic/stakeholder-map/>)
- [DesignOps](<https://wiki.soroush.uk/topic/design-ops/>)
- [Sales Enablement](<https://wiki.soroush.uk/topic/sales-enablement/>)
