A new process is announced with a polished deck, a confident launch date, and a calendar full of training sessions. The date passes, the software is technically live, and adoption flatlines. Product marketers keep sharing the old positioning document, sales engineers return to familiar demos, and operations teams maintain unofficial spreadsheets because the new workflow feels slower.

In my experience, the idea usually isn't the problem. The missing pieces are timing, ownership, role-specific guidance, and reinforcement. McKinsey's How to Beat the Transformation Odds survey found that only 26% of respondents considered the transformation they knew best very or completely successful at both improving performance and sustaining results over time. That finding is a useful reminder that implementation and adoption are different outcomes.

The change management best practices below form a practical sequence for product marketing, sales enablement, and operations teams. Each one gives you a way to decide what to do, who owns it, what can go wrong, and which signals to measure.

Quick answer: The most effective change management best practices are to pick a model that fits the change (Kotter, ADKAR, Lewin or Bridges), map stakeholders, build a champion network, pilot before scaling, give employees short just-in-time videos and guides for each task, and measure adoption at 30, 90 and 180 days. The common thread is connecting employee behavior to the business result the change is meant to deliver.

Table of Contents

• 1. How can Kotter's 8-Step Change Model create momentum?

• 2. How does the ADKAR model diagnose adoption problems?

• 3. When is Lewin's three-stage model useful?

• 4. How can Bridges' Transition Model reduce disruption?

• 5. How should stakeholder mapping shape engagement?

• 6. Why do change champion networks improve local trust?

• 7. How do phased rollouts and pilots lower change risk?

• 8. Why does just-in-time video enablement support adoption?

• 9. How should continuous feedback loops guide reinforcement?

• 9-Point Change Management Comparison

• Turning Nine Practices into One Change Plan You Can Actually Run

• How Trupeer Helps Teams Adopt Change Faster

• Frequently Asked Questions

  • What are the most important change management best practices?

  • Which change management model should I use first?

  • How do I measure whether a change has been adopted?

  • How can I reduce resistance to a new tool or process?

  • Can video replace live change management training?

1. How can Kotter's 8-Step Change Model create momentum?

Kotter's model works best when a complex transformation needs a visible sequence, strong sponsorship, and repeated proof that the new way is worth adopting.

I use it when a project crosses departments and can't be carried by one enthusiastic owner. The sequence moves teams from urgency and coalition-building through vision, communication, obstacle removal, short-term wins, continued momentum, and cultural reinforcement. That structure matters in a global enterprise where product marketing, sales, support, and operations may each interpret the same change differently.

A practical owner map looks like this:

• Executive sponsor: Makes the business case concrete and removes organizational barriers.

• Change lead: Coordinates the roadmap, risks, dependencies, and adoption measures.

• Functional leaders: Translate the vision into role-specific expectations.

• Local champions: Surface friction and make progress visible in each team.

A global IT services firm moving delivery teams to cloud-based project tooling might start by showing how fragmented workflows affect handoffs, then create a cross-functional coalition and publish early wins from teams already using the platform. A retail chain could pilot a new inventory process in three stores before expanding it, using those stores to refine training and create credible advocates.

Practical rule: Don't announce urgency as a slogan. Tie it to the workflow, customer experience, or business result people can see in their own work.

Create a short walkthrough video of the future state so every stakeholder hears the same story. Pair that vision with step-by-step guidance, using this change management process to connect leadership communication with the practical work employees must perform. Tools like Trupeer, which turn screen recordings into narrated videos and guides, can help you publish both assets together.

Track visible wins, unresolved blockers, active usage, and whether teams are still using the intended workflow after launch. The model is strongest when the sequence stays connected to evidence, not just communication activity.

2. How does the ADKAR model diagnose adoption problems?

ADKAR helps you identify whether a person lacks Awareness, Desire, Knowledge, Ability, or Reinforcement, then match the intervention to that gap.

I find this model especially useful when a team says, “We trained everyone, but they still aren't using the tool.” Training only addresses part of the problem. A sales team may understand a new CRM but avoid it because the workflow feels like extra administration. A finance team may want a new expense platform but still be unclear about the approval path.

Ask three or four people in each affected team questions such as:

• Awareness: Do you understand why this change is happening?

• Desire: Do you see a reason to participate?

• Knowledge: Do you know what to do?

• Ability: Can you complete the task during real work?

• Reinforcement: What will help you keep doing it?

The fix should follow the answer. Use leadership messaging for an awareness gap, manager conversations or incentives for a desire gap, short demonstrations for a knowledge gap, supervised practice for an ability gap, and usage reviews or recognition for reinforcement.

A healthcare network might discover that nurses understand a scheduling system but haven't had enough hands-on practice. The right response isn't another presentation. It's a role-specific walkthrough followed by supported practice during a real scheduling task.

I'd also keep the guidance searchable and current. A well-maintained change management documentation resource can give employees the exact procedure they need without forcing them to repeat a long course.

The takeaway is simple: check which outcome is missing before choosing the intervention. More training won't solve a trust problem, and another announcement won't create ability.

3. When is Lewin's three-stage model useful?

Lewin's Unfreeze, Change, Refreeze model gives teams a simple way to prepare people for the old workflow to end, support the transition, and make the new behavior stick.

Its simplicity is an advantage when a project team needs a shared mental model without adding another complicated governance layer. I use “unfreeze” to understand what people value in the current process, “change” to provide practical support, and “refreeze” to update the systems and routines that otherwise pull people back.

A manufacturing plant replacing paper quality checks with a digital checklist might begin by asking operators what the paper process helps them notice. During the transition, supervisors can provide short demonstrations at shift start. To refreeze the behavior, the digital checklist becomes part of shift handover reviews and quality reporting.

The same logic applies to knowledge work:

• Unfreeze: Document the cost, risk, or friction in the current process and acknowledge what people may lose.

• Change: Provide coaching, quick-reference guides, and time to practice.

• Refreeze: Update templates, reporting, onboarding, performance conversations, and access rules.

The weak version of this model rushes through preparation because leaders are eager to launch. That usually creates confusion later. If people don't understand why the old approach is changing, they'll treat the new system as a temporary preference.

People don't need endless persuasion. They need a credible reason, a usable replacement, and evidence that leaders won't quietly return to the old standard.

Short before-and-after videos can make the difference visible. Documentation should also survive staff turnover, so the new standard doesn't depend on the person who led the rollout.

4. How can Bridges' Transition Model reduce disruption?

Bridges' model separates the external change from the internal transition. It helps leaders plan for endings, the uncertain Neutral Zone, and the gradual beginning of a new operating state.

I've seen teams treat a system launch as if everyone moves instantly from old to new. That assumption creates bad timelines. People may understand the new structure while still grieving lost autonomy, familiar team identities, or responsibilities they handled confidently.

A bank introducing regional roles might acknowledge the loss of local team identity before discussing the organizational chart. A software company changing its pricing model could hold open office hours while product marketing, sales, and customer success teams work through new packaging, approval rules, and customer questions.

During the Neutral Zone, keep the operating environment deliberately supportive:

• Name the losses: Explain which responsibilities, tools, routines, or relationships will change.

• Protect capacity: Expect uncertainty and avoid scheduling the rollout as if normal productivity will continue without adjustment.

• Keep answers available: Maintain a living library of role-specific procedures and decisions.

• Create access to leaders: Let employees ask questions without turning every concern into a formal escalation.

A product marketer may need a temporary messaging guide while final positioning is still being approved. A sales engineer may need a safe way to show the new product workflow before every edge case is resolved. A searchable how-to library reduces dependency on a single change manager during this messy middle.

The trade-off is that transition support takes time before the organization can show a clean “new normal.” That time is usually cheaper than pretending uncertainty doesn't exist and then repairing workarounds later.

5. How should stakeholder mapping shape engagement?

Stakeholder mapping shows who can accelerate, block, influence, or secretly undermine a change. It turns a generic communication plan into a set of deliberate conversations.

I start with more than the org chart. A regional marketing lead may have no formal authority over a global rollout but still shape adoption because teams ask that person for advice. A frontline operations specialist may know where the process fails long before the project dashboard shows a problem.

Use a power-interest grid as a starting point, then add three practical questions:

• Who decides? Identify sponsors, budget owners, policy owners, and approval authorities.

• Who performs the work? Include employees whose daily behavior determines adoption.

• Who do people trust? Ask frontline staff who they contact for informal advice.

An insurance company redesigning its claims portal should involve claims managers early because they understand both operational impact and customer consequences. A global brand rolling out a new campaign workflow might give regional marketing leads early access, not because every lead owns the decision, but because they influence how the process is interpreted locally.

Revisit the map after leadership changes, pilot findings, or major scope decisions. Static maps age quickly.

For high-interest stakeholders, personalized video updates can be more effective than adding another meeting. A short account-based update can show what changed, what remains open, and what input you need. I'd pair that with a clear communication plan for change management, including audience, owner, channel, message, and feedback route.

The strongest stakeholder strategy doesn't try to make everyone equally involved. It gives each group the right level of access, influence, and information.

6. Why do change champion networks improve local trust?

Change champions make a transformation understandable inside the teams doing the work. They're effective when colleagues trust their judgment, project leaders equip them properly, and managers protect time for the role.

A hospital system introducing electronic charting might appoint nurse champions on each unit. Those champions can demonstrate the workflow in context, capture recurring questions, and explain where the system supports clinical work. A technology company changing its performance review process could use champions across regional offices to identify language, timing, and manager-coaching issues.

Don't select champions only because they're available or enthusiastic. Look for people who are credible, patient, and willing to report bad news. Then give them:

• Protected time: Champion work shouldn't be invisible overtime.

• A shared toolkit: Include FAQs, short videos, sample messages, escalation paths, and current procedures.

• A direct project connection: Let champions reach the product, HR, IT, or operations owner quickly.

• A question log: Record repeated issues so the central team can fix root causes.

A champion who repeatedly answers the same question is giving you product and documentation feedback, not just providing peer support. If the question concerns a confusing approval step, rewrite the guide or change the workflow instead of asking champions to compensate forever.

The super user training program approach is useful here because it treats peer support as an operating capability. Champions need enough understanding to coach others, but they shouldn't become the permanent help desk.

Measure champion participation, recurring issue themes, unresolved questions, and adoption by team. A network is working when it improves the signal flowing back to the project, not merely when it produces more messages.

7. How do phased rollouts and pilots lower change risk?

A pilot lets you test the workflow, training, documentation, and support model with real users before the change reaches everyone.

I'm cautious about pilots that use only the most enthusiastic team. They produce clean results but hide the constraints that matter later. Choose a group that reflects different roles, experience levels, locations, and workflow complexity. The pilot should be small enough to support closely and varied enough to expose real friction.

Set decision rules before the pilot starts:

• Adoption signal: Are intended users completing the new workflow?

• Quality signal: Are errors, rework, or escalations within an acceptable range?

• Support signal: Are questions declining, or are people repeatedly stuck at the same step?

• Readiness signal: Can managers and champions support the next group?

Microsoft's deployment-ring approach is a familiar example of staged software release, with updates reaching smaller groups before broader audiences. Adobe has also used staged approaches for Creative Cloud adoption. The practical lesson isn't to copy either company's exact method. It's to expand based on evidence rather than launch enthusiasm.

A pilot for a new sales enablement platform might reveal that the content is easy to upload but difficult to find. That finding should change taxonomy, search labels, and training before the next wave begins.

Treat each wave as a learning cycle. Update the SOP, video, stakeholder messages, and support route after each one. A pilot that produces no changes may indicate that the team didn't ask enough of users or didn't create a safe way to report friction. For a broader framework beyond pilots, see this software adoption strategy.

8. Why does just-in-time video enablement support adoption?

Short, single-task videos and searchable guides help employees solve problems while they're working, rather than asking them to remember a long training session.

A SaaS company might replace a large onboarding deck with role-based clips in its help center. A logistics firm could place short demonstrations near a warehouse management workflow, showing staff how to complete a new scanning step when they need it.

The content unit should be a task, not a product tour. Start with the five actions generating the most questions, then build outward. For each clip, answer one practical question:

• What outcome should the viewer complete?

• Which role is this for?

• What must happen before the task?

• What does success look like?

• Where should the user go if the screen differs?

Design for retrieval, not attendance. If an employee can't find the answer at the moment of need, the training asset is only partially useful.

Record the workflow once, then turn it into a narrated product video, written SOP, screenshots, and translated versions. This guide to creating change management training videos for enterprise software rollouts explains the content-production angle in more detail.

Tip: With Trupeer, one screen recording becomes a narrated video with AI voiceover, a step-by-step SOP with screenshots, and translated versions in 65+ languages. When the workflow changes, you update the source once instead of rebuilding every asset. See how change management teams use Trupeer.

Keep an owner and review date on every asset. A stale demo can be worse than no demo because it teaches confidence in the wrong process. When the interface changes, you can often update a training video without re-recording it.

9. How should continuous feedback loops guide reinforcement?

Continuous feedback combines short pulse surveys, usage data, support questions, and manager observations so the change team can act before friction becomes a permanent workaround.

A single post-project survey arrives too late and usually asks people to summarize a complex experience from memory. I prefer short pulses with no more than three questions, followed by a visible response. If employees share feedback and never hear what changed, the survey becomes a ritual instead of a feedback loop.

A retail bank running a branch software rollout might ask whether employees feel confident completing the core task, where they get stuck, and what guidance would help. If one region reports low confidence, the team can adjust practice sessions or documentation instead of sending the same training everywhere.

Pair perception with behavior:

• Ask: What feels unclear or difficult?

• Observe: Which workflows are being used as designed?

• Inspect: Where do support tickets and search failures cluster?

• Act: What will change in the next release or guidance update?

• Report back: What did the team change because of the feedback?

Google's Project Oxygen is an example of using employee and manager data to identify effective management behaviors. The broader lesson is to treat feedback as an input to decisions, not as a satisfaction score collected for reporting.

Track adoption at 30, 90, and 180 days as distinct checkpoints, as recommended in this change-management adoption metric framework. Define adoption as the share of the target population actively using the new behavior as designed, then segment the view by role, country, business unit, and workflow. For the specific measures to track, see these end user adoption metrics.

9-Point Change Management Comparison

Turning Nine Practices into One Change Plan You Can Actually Run

These practices work better as a connected operating plan than as nine separate boxes to tick. Kotter can provide the sequence and sponsorship structure, ADKAR can diagnose individual adoption gaps, and Lewin can help the team think about preparing, transitioning, and reinforcing the new state. Bridges adds the human reality that people may understand the change before they feel ready for it.

I'd run the plan in this order:

• Define the outcome: State what must improve, who owns it, and how you'll know the improvement persists.

• Map the people: Identify decision-makers, affected roles, informal influencers, champions, and teams carrying the highest workload.

• Diagnose the gap: Use ADKAR conversations to separate missing awareness, motivation, knowledge, ability, and reinforcement.

• Pilot the workflow: Test with a representative group, then revise the product experience, SOPs, videos, and manager guidance.

• Scale with local support: Equip champions and managers with role-specific materials and a direct route for escalation.

• Measure behavior: Track active use, successful task completion, error patterns, support demand, and business outcomes.

• Reinforce the standard: Update onboarding, templates, operating reviews, recognition, and documentation so the old process loses its pull.

The measurement discipline matters. Prosci's benchmark, based on more than 10,800 respondents across 101 countries, reported that 88% of projects with excellent change management met or exceeded objectives, compared with 13% of projects with poor change management. The Prosci research resources also emphasize that these are survey-based associations, not controlled causal experiments. I still find the benchmark useful because it points to an operational truth: change management capability should be measured as an outcome driver, not treated as a communications workstream.

Sponsorship needs the same discipline. Prosci reported a 79% likelihood of meeting objectives when sponsorship was extremely effective, compared with 27% when it was extremely ineffective. That doesn't mean an executive video can rescue a broken workflow. It means leaders need to stay visible, make decisions, remove conflicts, and reinforce the expected behavior after launch.

Start this week with one upcoming change. Write the target behavior in plain language, assign an owner for stakeholder mapping, diagnosis, champions, rollout, enablement, and measurement, then agree on two metrics. One should show adoption, and the other should show whether the business or operational result is improving. Review both after launch and keep reviewing them after the attention moves elsewhere.

Trupeer can support the content layer by turning one screen recording into product videos, SOPs, searchable guides, and translated materials. That's useful when workflows change frequently, but governance still matters. Give every asset an owner, audience, version, review date, and retirement rule.

How Trupeer Helps Teams Adopt Change Faster

Several of the practices above, especially just-in-time enablement, champion toolkits and pilot rollouts, depend on giving people clear, current instructions at the moment they need them. That is where Trupeer fits:

• Record the new workflow once: A process owner captures the change with the Trupeer Chrome extension.

• Get a video and a guide together: Trupeer turns the recording into a short video with AI voiceover and a step-by-step guide with screenshots.

• Equip champions: Publish everything to a searchable knowledge base so champions and managers can share the same answers.

• Support global rollouts: Translate videos and guides into 65+ languages for every region.

• Update after each pilot wave: Re-record only the steps that changed instead of rebuilding the training.

See Trupeer for change management.