Before You Call It Resistance, Ask What the Change Requires
When employees push back on a new process, leaders need to understand what they are being asked to give up, take on, or figure out. Resistance can reveal the work an implementation plan has missed.
Imagine this situation.
A probation department introduces a new case management system. Leadership expects clearer documentation, better coordination, and fewer disconnected spreadsheets.
At the rollout meeting, a veteran officer asks whether staff will have to enter the same information in two places during the transition.
Another asks what happens to appointments already scheduled in the old system.
A supervisor wants to know who will cover the front desk while employees attend training.
By the afternoon, someone describes the team as “resistant to change.”
That label arrives awfully early.
The questions concern duplicate work, continuity, and coverage. Before deciding that employees have an attitude problem, leadership needs to determine whether it has an implementation problem.
The announcement leaves a lot unanswered
From the executive chair, a change may look straightforward: approve the purchase, communicate the benefits, schedule training, and set a launch date.
From the employee’s chair, the questions are more immediate.
What happens to my workload? Which task takes priority when both cannot get done? Who helps when the system fails during a client appointment? Will I be held responsible for a mistake caused by an unclear process?
An announcement can explain the purpose of a change without answering any of those questions.
Employees still have to make it work on Tuesday morning.
That gap deserves attention. Calling it resistance does little to close it.
Listen closely enough to identify the objection
“People don’t like it” is too vague to act on.
A leader needs to know what, specifically, people are concerned about. The same objection can contain several different problems.
“This takes too long” might mean an employee needs more practice. It might mean the workflow contains unnecessary steps. It might mean the new task is reasonable, but nothing has been removed from an already full day.
Each explanation calls for a different response.
More training will not fix duplicate data entry. A revised workflow will not resolve uncertainty about who has authority to make a decision. Another motivational speech will not create time for practice.
Useful questions include:
Which part of the new process is difficult to carry out?
What existing responsibility competes with it?
What decision remains unclear?
What would help you perform this correctly tomorrow?
Ask employees to describe the work, then examine it with them.
Participation needs a visible consequence
Inviting feedback is easy. Showing what happened to that feedback takes discipline.
If staff identify a problem, leaders should close the loop. Explain what will change, what needs further investigation, and what must remain because of an actual requirement.
Sometimes the answer will be no. Leaders still owe people a clear explanation.
“We reviewed your concern. This step must remain, but we can remove the second approval” gives employees something concrete.
“We appreciate your feedback” followed by silence leaves them guessing whether anyone considered it.
Participation has value when it helps shape the implementation and makes decisions understandable.
Make the new practice observable
Broad instructions create room for confusion.
“Use the system consistently” sounds clear until people encounter a complicated case, an unavailable document, or a task that does not fit the standard sequence.
Leaders should identify the specific actions employees need to perform and demonstrate them using realistic situations.
In the hypothetical probation department, that might mean walking through how to document a contact, update a case plan, and flag a concern for supervisory review. Staff should also see what to do when information is incomplete.
Then let them practice.
A supervisor can observe the task, identify where the employee gets stuck, and provide feedback. The employee can try again before completing the process during a live appointment.
That is more useful than discovering misunderstandings through a backlog of incorrect records.
Keep accountability clear
Listening to concerns does not mean every employee gets to decide whether to participate.
Leaders can be firm about a required change while taking responsibility for making it workable.
Be explicit about expectations, available support, and the point at which employees should be able to perform the task independently. Address refusal when it occurs. First, distinguish refusal from confusion, lack of preparation, and a process that cannot reasonably be completed as designed.
Those distinctions matter to fair supervision.
They also help leaders spend their effort on the actual problem.
Try the work before declaring the organization ready
Before the next launch, choose one representative task. Have an employee perform it from beginning to end under realistic conditions.
Watch the handoffs. Count the repeated steps. Identify the questions that require someone to improvise. Ask what other work would be waiting during that time.
Then revise, practice, and test again.
At TTS, we believe change needs to connect leadership decisions with the daily practice required to carry them out.
Before calling people resistant, make sure you understand what the change asks them to do, and whether you have equipped them to do it.