Workflow failures typically stem from poor rollout strategies rather than flawed processes. A manager might introduce a new approval system and supply a user guide on Monday, yet find that half the team continues emailing files back and forth by Friday. Although documented, the new workflow remains unused.
By leveraging change management theory, managers gain a structured framework to navigate team transitions from established habits to new operations, turning adoption into an achievable, planned objective. It’s also a learnable skill: some managers pick it up through trial and error on the job, while others study it formally as part of a business or management education. Below, we explore the underlying reasons teams push back against new workflows, examine three key frameworks, and walk through a step-by-step implementation plan.
Why Teams Resist New Workflows
Resistance is rarely about stubbornness. It usually comes from a few predictable sources.
The first is loss of familiarity. Even an inefficient process is comfortable once people know it well. Switching means a period of feeling slower and less competent, and few people enjoy that, especially when deadlines haven’t moved; the second is unclear benefits. If the team can’t see what’s wrong with the current process, the new one looks like extra work imposed from above. “Leadership wants us to use a new tool” doesn’t convince many people.
The third is change fatigue. Teams that have been through several reorganizations, software migrations, or policy updates in a short time often stop investing in new initiatives. They expect each one to be replaced soon anyway.
Knowing which of these is at play shapes your response. A team worried about competence needs training and patience. A team that doesn’t see the point needs a clearer case for the change.
Three Frameworks Worth Knowing
Psychologist Kurt Lewin’s Unfreeze, Change, Refreeze model, developed in the 1940s, describes change in three stages. First, you loosen attachment to the current way of working. Then you introduce the new process. Finally, you reinforce it until it becomes the norm. The model is simple, which is both its strength and its limit. It’s good for explaining change to a team but too general to work as a detailed plan.
ADKAR, developed by Prosci founder Jeff Hiatt, focuses on the individual rather than the organization. The letters stand for Awareness, Desire, Knowledge, Ability, and Reinforcement. The model is useful for diagnosing where a specific person is stuck. Someone who understands the new workflow but still avoids it may have a desire problem, not a knowledge problem.
Kotter’s 8 Steps, introduced by Harvard Business School professor John Kotter in his 1996 book Leading Change, break organizational change into eight sequential stages. It’s the most action-oriented of the three.
These frameworks come from decades of research in psychology and organizational behavior, and they remain a standard part of business and management education at multiple levels. Someone who decides to study for an online bachelor’s degree in business or psychology will often meet Lewin, ADKAR, and Kotter in management and organizational behavior courses, and studying online makes it possible to test those ideas on a real team while still working. Experienced managers who want to go further can find the same models at the master’s level, where they’re usually examined through detailed case studies of organizations that handled change well, or badly. Either way, studying them in context is what turns a list of steps into judgment about when and how to use them.
Applying Kotter’s 8 Steps to a Workflow Rollout
Whether you’re studying these models or using them on the job, they make the most sense when you see them applied. To make Kotter’s steps concrete, imagine a 12-person marketing team moving content approvals from long email threads to a shared project tracker such as Lark Base, Asana, or Trello. The tool matters less than the process around it.
1. Create a sense of urgency
Show the cost of the current system with a recent example, such as a blog post that sat in someone’s inbox for six days or a campaign that launched with an outdated asset. Specific, recent problems create urgency far better than general claims about efficiency.
2. Build a guiding coalition
Recruit two or three respected team members to help shape the rollout, and include at least one skeptic if you can. When people the team trusts are involved early, the change stops feeling like a top-down mandate.
3. Form a strategic vision
Describe success in one or two sentences, for example: “Every piece of content has one visible status, one owner, and one place for feedback.” A clear vision gives people something to measure the new workflow against.
4. Communicate the vision
Repeat the vision in team meetings, one-on-ones, and written updates. Most managers underestimate how often a message needs to be heard before it sticks. Invite questions and answer them openly, including the uncomfortable ones.
5. Remove barriers
Find out what’s actually stopping people. It might be missing permissions, a confusing setup, or a senior stakeholder who still sends feedback by email. That last one is common and will undermine the change faster than anything else, so address it directly.
6. Generate short-term wins
Run one small project entirely through the new workflow, then share the results. If approvals took two days instead of six, say so. Early, visible wins give skeptics evidence instead of promises.
7. Sustain acceleration
After the first wins, expand gradually. Move more project types into the new system, refine the process based on feedback, and resist calling the job finished. This is where many rollouts stall.
8. Institute the change
Make the new workflow part of how the team operates. Add it to onboarding materials, reference it in team norms, and stop accepting approvals through the old channel. When new hires learn only the new way, the change has stuck.
Common Mistakes Managers Make
The most frequent mistake is announcing instead of involving. A process designed without input from the people who will use it tends to miss practical details and earns little goodwill.
Skipping training is another. Sending a link to documentation is not training. A short live walkthrough, plus a go-to person for questions during the first few weeks, makes a noticeable difference.
Declaring victory too early is a mistake Kotter specifically warns against. A good first month doesn’t mean habits have changed, and old workarounds often creep back once attention moves elsewhere; finally, running several changes at once divides attention and feeds change fatigue. Where possible, sequence changes so the team can absorb one before the next begins.
Measuring Whether the Change Stuck
Set check-ins at 30, 60, and 90 days and track a few simple indicators. Adoption rate shows what share of work moves through the new workflow rather than old channels. Cycle time shows whether approvals are faster than before. Errors and rework reveal whether fewer outdated files or missed comments are slipping through. A short anonymous survey can surface frustrations people won’t raise in meetings.
These numbers only mean something against a baseline, so record how the old process performed before you start.
Conclusion
Rolling out a new workflow is as much a leadership task as a technical one. The tools and process need to be sound, but adoption depends on whether people understand why the change matters, feel involved in shaping it, and get support through the awkward early weeks. Frameworks like Kotter’s 8 steps won’t eliminate resistance, but they give managers a clear plan for working through it instead of waiting for it to fade.