How and When to Create Your Change Management Plan + Free Template

A team of young coworkers crafting a change management plan together

Often, mid-sized teams switch to a new tool with real excitement, and still no’t get everyone using it. Three months into the change, half the team still works the old way. No one has officially decided which version is the source of truth, and that’s the gap a change management plan can close.

It's not a rare scenario. Gartner's 2025 HR research found only 32% of business leaders report their organization achieves healthy change adoption at all. The other 68% are living some version of the scene above. Change management within the organization requires managing employees' and stakeholders' expectations when new leadership comes in, or a new tech stack is adopted. 

Everything is in its place, but the lack of a change management plan means nobody owns the gap between announcing the change and it actually sticking, which is why you need a change management plan to intentionally close that gap.

What Is a Change Management Plan?

A change management plan is a documented set of decisions, in a specific order, that governs how an organization transitions from an old way of working to a new one. It clearly names who is responsible for each part of the transition, what gets communicated, and when, as part of change management planning and communication.

Change management

Source | Powerslides

Another key aspect this plan involves is documenting how the team will know the change is complete (included in our free change management plan template to download).

Responsibility for starting one usually falls to a business leader or manager who first identifies the need. Building and using the change management plan document rarely stays with one person for long. The project manager typically owns the timeline.

HR shapes how the change lands with the people affected. Department heads add a third view, since they tend to notice resistance before anyone else does.

A good change management plan addresses three different layers.

  • People need to understand their new roles under the change

  • Processes need updating so daily workflows actually reflect it

  • Technology needs to support whatever system the change depends on

When You Need a Change Management Plan

Honestly, not every change demands a formal plan. For small shifts, a quick note in a team channel is enough. You need a change management plan if it affects how people work day-to-day, not just what exists on paper.

Below, we’ve featured some key situations where that gap tends to show up most. For starters, begin the change plan early (before the change happens) to make adoption stick once it's underway.

A. Introducing New Technology

Decision-makers weigh vendors, pricing, and features carefully but often skip who owns the data move and who runs the training. 

Here, risk management is crucial because the current work is underway while the switch is happening. Someone finishes a task in the old system after the new one is already live, and now two versions of the same project exist, with no rule for which one counts.

This category covers any change where the tool itself is what's shifting:

  • Rolling out new software or a project management tool

  • Adopting a platform that changes daily workflows

  • Migrating data between systems

What This Looked Like for One Team

UPPAbaby had their Airtable contract expiring on a fixed date. It wasn’t feasible to pause the creative work during the migration.

The key issue: product details didn't enter the workflow at the same stage every time. Be it SKU numbers, fabric content, UPC codes, or even pack-out requirements. Whoever started a task filled in what they had on hand. Whoever picked it up next added whatever was missing, which left the team with no single version (of truth) anyone could trust as current.

Cirface rebuilt the workflow in Asana around SKU-level projects, embedding structured approvals and centralized product data to avoid the same gaps in a new tool. UPPAbaby hit the hard cutoff on schedule, and now saves roughly 12 hours a month that used to go into chasing down which version of a product's details was actually correct.

B. Organizational Restructuring

A prime example is a merger or acquisition, but sometimes there are also departmental splits where one team breaks into two or two departments become one. On paper, the organizational chart looks clean. 

But in practice, people keep sending sign-offs to their old manager for weeks because nobody's told them who actually holds that authority now. Which is why change of people bring friction to this change.

Organizational Change

Source | People-shift

It’s also because the new manager hasn't been looped into the tools where those approvals occur. Requests remain unapproved in the wrong inbox until someone finally notices and forwards them.

With a change management plan, you unlock:

  • A named decision owner for each function before the restructure takes effect, so approvals don't default to habit

  • Escalation paths that work from day one instead of getting sorted out on the fly

  • Coverage through the transition window so nothing sits stuck between the old structure and the new one

C. Process Reengineering

Changes within the organization also introduce new processes that replace how a task has always been done. Without a plan, the old way of working never formally retires due to obstacles to process improvement. So people default to the version they already know, especially when they’re functioning under deadline pressure. And when two methods run in parallel until their outputs start to diverge.

With a change management plan, process reengineering helps manage expectations in the following manner:

  • Providing a fixed cutover date after which the old process is no longer used

  • Step-by-step documentation of what actually changed, not just that it did

  • A way to catch anyone still using the old method before their output causes a problem

D. Cultural Transformation

Leadership says decisions should move faster, with fewer approvals needed. Months later, some of the key decisions would still move through the same three people. It’s because managers are graded on how closely they track their team's work, and the grading hasn't changed.

A change management plan redefines these review criteria, going beyond simple cultural transformation announcements. That’s when managers get scored on how much they've delegated, not how tightly they've held on, and that number actually drives behavior.

Cultural transformation backed by a change management plan includes:

  • Specific, observable behavior that counts as evidence, so the shift means something beyond a slide

  • Manager check-ins on a real schedule, not a one-time mention

  • Permission to name the old pattern out loud when it shows back up, since it will

E. Compliance and Regulatory Change

A privacy law can affect how you manage customer data and its impact on how your organization remains compliant. This means it changes how you store customer data and even how you work around it. For example, not retaining data beyond a certain period or acting on the customer's request to delete their data sooner than before. 

The legal team signs off on the update. The retention window shrinks, and certain fields now need to be masked before a record leaves the system, but that change reaches the legal team and stops there. The person pulling customer records every day never hears about it, so they keep saving full purchase history the same way they did last year.

A change management plan can offer the following in this case:

  • Training tied to the exact fields, retention periods, or deletion steps that changed, not a generic policy refresher

  • A record of who was trained and when, ready the moment an audit asks

  • One named person accountable for closing the gap between legal and daily practice

F. Market Expansion or Product Launch

When a product launches, or you expand into a new market, the support needs to be aligned with it, not just told about it after the fact. Skipping this would mean customers learn more about the product before support.

product launch plan

product launch: without a plan vs with a plan

Sales and support are supposed to know the product better than the customer does. When representatives themselves are learning what was rolled out from the ticket in front of them, they're behind the person they're supposed to be helping.

A change management plan helps:

  • Sales and support team get briefed on the real details before the announcement goes out, not after

  • One shared answer to the first wave of customer questions, instead of five reps improvising five different ones

  • A clear owner for that first 48 hours, so nothing falls between teams

The Change Management Plan Template

Download a free change management plan template with fifteen fields, grouped so you're not scrolling through a flat list. Each one below explains what actually goes in it, not just the label. Fill in what applies to your change and skip what doesn't; this isn't a form you need to complete top to bottom.

Here’s a quick snapshot of what to expect.

A. Foundation — Executive Summary, Background, Objectives, Scope of Change

B. People — Stakeholder Analysis, Change Management Team

C. Execution — Communication Plan, Training Plan, Implementation Timeline

D. Risk and Measurement — Risk Management Plan, Success Metrics and Monitoring, Feedback Mechanisms

E. Admin — Budget Details, Approval, Appendices

[DOWNLOAD FREE CHANGE MANAGEMENT TEMPLATE]

Wrapping Up

A change management plan doesn't prevent every rough patch. It gives someone a place to look when things stall, who owns the decision, what was supposed to happen by when, and what still needs to happen before it's actually done. That's the difference between a change that eventually sticks and one that quietly runs on two systems for the next year.

Use the template above to build your own, whether that's a straightforward rollout or something closer to what UPPAbaby went through. If you'd rather walk through it with someone who's run this a few hundred times, book a Connect Call and we'll look at where you're starting from.


We help enterprises audit their current tool stack and simplify change management through right structure, making change a seamless activity with å right workflow in place.

Book a call with our team to map your path.

Previous
Previous

How to Set Up and Organize Your SOPs in Asana

Next
Next

Using Asana for Scrum Project Management: A Quick Guide