Change Strategy

A change strategy answers the question "how will we approach this change?" before anyone answers "what will we do, and when?". It sits between the decision to change and the detailed plans for communication, learning, support and delivery.

A good strategy does four jobs:

• Shared understanding. The sponsor, leaders and project team agree on what the change is, why it matters and how it will be led.
• A basis for decisions. When time, money or attention is short, the strategy shows which trade-offs fit the intent.
• Consistency. Communication, training, HR and delivery workstreams follow the same logic rather than inventing their own.
• A reference point. When circumstances shift, the team can see what assumptions have changed and adjust deliberately.

A change strategy is therefore the agreed logic of a change, from which the detailed plans are derived.

Texts and professional standards use different headings, but most cover the same ground:

• Context and case for change: what is driving the change, what happens if nothing changes, and the desired future state.
• Scope and impacts: what is in and out of scope, and which groups are affected and how much.
• Stakeholders: who has influence or interest, and their likely position.
• Approach: how fast and in what order the change will roll out, how directive or participative it will be, and which levers will be used.
• Roles and governance: sponsor, change manager, line managers, change agents, and how decisions are made.
• Risks and assumptions: readiness, capacity, competing initiatives and dependencies.
• Measures: how adoption and benefits will be tracked.
• Timeline: the main phases and milestones.

A short strategy that covers these points and is agreed is worth more than a long one that nobody reads.

A change strategy should therefore be complete in scope but brief in form.

The approach should follow from the context, not from habit.

Michael Beer and Nitin Nohria (2000) contrasted two archetypes. Theory E pursues economic value, top-down, through structure, systems and financial incentives. Theory O builds organizational capability, participatively, through culture and learning. They argued that the most effective changes combine the two in a deliberate way.

Julia Balogun and Veronica Hope Hailey offer a more detailed method, the change kaleidoscope. It asks the change team first to analyze features of the context, such as time available, scope, what must be preserved, diversity, capability, capacity, readiness and power, and only then to make design choices such as the change path, the start point, the change style and the levers to use.

Choosing the approach in a change strategy is therefore a diagnosis of context followed by a combination of design choices.

The two are often merged, which makes both weaker.

The plan is derived from the strategy. If a planned activity cannot be traced back to a strategic choice, either the activity or the strategy needs a second look.

A change strategy and a change plan are therefore two levels of the same thinking, and the strategy comes first.

Harbourside Council is moving resident requests, from missed bin collections to parking permits, to a single online service with a shared case team. The change manager drafts a six-page strategy with the sponsor, the director of customer services.

• Case for change: requests are spread across nine phone lines, and residents chase answers repeatedly.
• Impacts: high for contact-center staff and back-office teams, moderate for councillors, low for most other staff.
• Approach: a pilot with one service, then phased waves by service area; participative design with front-line staff; no parallel phone lines after each wave.
• Roles: the director sponsors; each service head is a local sponsor; one change agent per team.
• Risks: a budget-setting period overlaps the first wave; union consultation is required.
• Measures: share of requests handled online, repeat contacts, staff confidence scores.

The strategy fits on a few pages, and every later plan refers back to it.

A change strategy in practice is a concise set of decisions that the sponsor has signed off.

• Writing it after the plan, so the strategy only describes activities already chosen.
• Filling a template without analyzing the context, which produces the same approach for every change.
• No sponsor agreement, so the strategy has no authority when trade-offs arise.
• Ignoring other changes competing for the same people's time and attention.
• Never revisiting it, even when scope, timing or readiness change.
• Treating the communication plan as the strategy, when communication is only one part of the approach.

A change strategy fails most often because it is skipped, copied or left unchanged, not because its content is wrong.