Your team isn’t resisting change—they’re protecting what works

Teams that appear resistant to change may actually be protecting the knowledge, relationships, and routines that keep work dependable. Organizational change is the deliberate shift in how an organization operates; successful change therefore requires more than announcing a new direction—it requires understanding what existing practices accomplish. That distinction matters: Gallup has reported that only 23% of employees worldwide were engaged at work in 2023, while Prosci’s change-management research identifies employee adoption as a central factor in realizing change outcomes. Leaders can respond more effectively by diagnosing the value behind current habits, involving employees in redesign, and measuring whether new ways of working improve results without discarding what already works.

Organizational Change and the Value of Existing Practices

Organizational change includes shifts to strategy, structure, technology, processes, or workplace culture. The accompanying resistance is not automatically opposition to progress. It can be a signal that a proposed change threatens a useful safeguard, creates new risks, or overlooks practical knowledge held by employees.

In its classic account of organizational change, researcher Kurt Lewin described change as a process involving preparation, movement toward a new state, and stabilization of new practices. Later change frameworks, including John Kotter’s, emphasize urgency, a guiding coalition, communication, and reinforcement. Although these models differ, they point to a shared principle: change is more likely to endure when people understand why it is needed and can help make it workable.

Resistance as information, not disloyalty

Resistance is a response to a perceived cost or risk of change. It may appear as questions, delay, reduced participation, or continued use of familiar processes. Treating these behaviors as information—not proof of bad intent—helps leaders discover whether the barrier is unclear communication, lack of training, inadequate tools, or a genuine flaw in the proposed design.

A useful first question is not “Why are people being difficult?” but “What does this current practice protect, and what would have to be true for a better alternative to feel safe?” That inquiry turns a conflict into a problem-solving conversation.

What existing routines may protect

A routine is a repeated way of coordinating work. Some routines preserve quality checks, customer trust, institutional memory, safety, or speed under pressure. Others may simply reflect outdated assumptions. The task is to distinguish the function of a routine from its familiar form: a team may need a reliable review step, for example, without needing the same paper-based approval process.

This distinction is especially important during digital transformation. The OECD’s work on public-sector innovation describes how established capabilities and institutional knowledge can support adaptation, while rigid procedures can constrain it. The practical implication is to preserve useful outcomes while remaining open to changing the means.

Employee Adoption and the Change-Management Process

Change management is the structured support that helps people move from current ways of working to intended future practices. Prosci defines its individual change model, ADKAR, through five outcomes: awareness, desire, knowledge, ability, and reinforcement. These categories help explain why agreement with a change announcement is not the same as being able to adopt the change in daily work.

Prosci’s 2023 Best Practices in Change Management report found that projects with excellent change management were seven times more likely to meet or exceed objectives than those with poor change management. This is an association reported from Prosci’s research, not a guarantee that a particular intervention will cause success. It nevertheless underscores the value of treating adoption as part of implementation rather than an afterthought.

Awareness and desire: explain the reason and invite participation

Awareness means understanding why change is necessary; desire is the willingness to participate. Leaders can build both by explaining the problem with concrete evidence, acknowledging trade-offs, and asking employees what could go wrong in practice. Participation is meaningful when feedback can influence the design—not when consultation occurs only after decisions are final.

For example, a service team asked to adopt a new case-management platform may be concerned not about technology itself but about losing visibility into urgent customer cases. Mapping that concern allows the implementation team to test alerts, escalation paths, and reporting before broad deployment.

Knowledge and ability: make the new behavior practical

Knowledge is knowing how to change; ability is being able to apply that knowledge in real conditions. Training should therefore include practice with actual tasks, accessible support, and time to learn. If the new process adds steps or requires unavailable equipment, resistance may reflect a capability gap rather than an attitude problem.

The U.S. Bureau of Labor Statistics reported that 37.7% of employed people in the United States teleworked or worked at home for pay in 2021, during the pandemic-era shift in work arrangements. That rapid transition illustrates why organizations must adapt tools, training, and coordination practices together; changing where work happens without supporting how it happens can create avoidable friction.

Reinforcement: keep what improves performance

Reinforcement consists of the feedback, recognition, resources, and management practices that help a new behavior continue. Leaders should track both adoption and outcomes: Are employees using the new process? Is it reducing errors, wait times, or rework? What new problems has it introduced?

A pilot can provide a low-risk way to answer these questions. Teams can compare a new workflow with the old one, document exceptions, and revise the design before scaling it. The goal is not to reward compliance alone, but to reinforce the practices that produce better results.

Psychological Safety and Employee Voice During Change

Psychological safety is a shared belief that people can speak up with questions, concerns, or mistakes without being punished or humiliated. Harvard Business School professor Amy Edmondson introduced the construct in research on team learning. In a changing organization, psychological safety helps teams surface risks early enough to address them.

Google’s Project Aristotle, an internal study of team effectiveness, identified psychological safety as the most important of five dynamics associated with effective teams in its analysis. This finding does not mean that comfort alone ensures performance. Rather, it supports the practical case for making it safe to challenge assumptions while maintaining clear goals and accountability.

Listen for the workarounds and exceptions

Workarounds are informal methods employees use when formal processes do not fit the task. They can reveal hidden expertise or serious control gaps. During a change initiative, leaders should ask frontline staff to walk through edge cases, handoffs, and customer scenarios instead of relying only on policy documents.

For instance, a hospital introducing a new documentation system should examine how clinicians handle urgent care, downtime, and handovers. A concern about an extra data-entry step may point to a usability issue or a patient-safety risk. The appropriate response is investigation and testing, not an assumption that the employee opposes modernization.

Close the feedback loop

Employee voice is useful only when people can see what happened to their input. A simple feedback loop records the concern, identifies an owner, communicates the decision, and explains whether the proposal was adopted, tested, or declined. This reduces rumor and shows that participation is consequential.

The Chartered Institute of Personnel and Development’s guidance on employee voice emphasizes mechanisms that allow employees to express views and influence workplace decisions. In practice, organizations can combine manager check-ins, anonymous channels, workshops, and pilot reviews, choosing methods that fit the sensitivity and scale of the change.

A Practical Method for Changing Without Losing What Works

Leaders can protect valuable capabilities while changing outdated processes by treating implementation as a cycle of diagnosis, experimentation, and learning. The following approach links employee concerns to evidence and operational results.

Map the current practice and its purpose

Document who performs each step, what decision it supports, and what risks it controls. Include informal knowledge held by experienced employees. This creates a baseline and helps distinguish essential functions from habits that no longer serve the work.

Define measurable outcomes before choosing a solution

Set a small number of indicators tied to the problem, such as processing time, error rates, customer satisfaction, safety incidents, or employee effort. A new system should not be judged solely by launch completion or usage counts; it should be evaluated by whether it improves the outcomes it was meant to address.

Test with affected employees and revise

Run a pilot with representative users, including people who handle uncommon or high-risk cases. Compare results against the baseline, invite candid feedback, and adjust the design. Pilots are most informative when leaders define what evidence would prompt them to change course.

Scale, support, and revisit

Once a change works in practice, provide role-specific training, clear escalation routes, and enough time and resources for adoption. Reassess after rollout: a process that succeeds in a pilot may behave differently at scale. Keep a route for reporting problems so that continuous improvement does not end at launch.

Conclusion: Treat Protection as a Clue to Better Change

Organizational change is more effective when leaders recognize that resistance can protect useful knowledge, safety, service quality, or coordination. Change management turns that insight into adoption through awareness, participation, capability, and reinforcement. Psychological safety makes it easier to surface risks, while pilots and measurable outcomes help determine what to preserve, revise, or retire.

Before labeling a team resistant, ask what its current approach makes possible. Map the underlying function, invite the people closest to the work to test alternatives, and measure whether the new approach performs better. Further reading on ADKAR, employee voice, and psychological safety can help managers build a change process that respects experience while making room for improvement.

Sources: Gallup, State of the Global Workplace: 2024 Report, https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx; Prosci, Best Practices in Change Management, 12th Edition, https://www.prosci.com/resources/articles/change-management-best-practices; Prosci, The ADKAR Model, https://www.prosci.com/methodology/adkar; Lewin, Kurt, “Frontiers in Group Dynamics,” Human Relations, 1947, https://doi.org/10.1177/001872674700100103; Kotter, John P., “Leading Change: Why Transformation Efforts Fail,” Harvard Business Review, 1995, https://hbr.org/1995/05/leading-change-why-transformation-efforts-fail; OECD, The Innovation Imperative in the Public Sector, 2015, https://doi.org/10.1787/9789264236561-en; U.S. Bureau of Labor Statistics, “Telework during the COVID-19 pandemic,” Monthly Labor Review, 2022, https://www.bls.gov/opub/mlr/2022/article/telework-during-the-covid-19-pandemic.htm; Edmondson, Amy, “Psychological Safety and Learning Behavior in Work Teams,” Administrative Science Quarterly, 1999, https://doi.org/10.2307/2666999; Google re:Work, Understand Team Effectiveness, https://rework.withgoogle.com/intl/en/guides/understand-team-effectiveness; Chartered Institute of Personnel and Development, Employee Voice, https://www.cipd.org/en/knowledge/factsheets/voice-factsheet/.