Skip to main content
Steady at the Top
← All articles

Why employees resist change that leaders think is obvious

Before responding to resistance, distinguish concerns about loss from warnings that implementation will fail. Ask for a concrete objection and the evidence behind it. Choose a response that addresses the source rather than assuming a more persuasive message will resolve every problem.

A psychological contract is a person’s belief about reciprocal obligations in a relationship, including what they understand has been promised. Rousseau and McLean Parks’ 1993 discussion of psychological contracts discusses these perceived obligations. A change objection may therefore concern a lost expectation as well as the proposed task. Distinguish that perceived promise from a legal contract; this article does not determine enforceable terms.

Revisit the objection you described as attitude

Composite scenario, not a client case: You recount a difficult rollout conversation at home and hear yourself describing employees as resistant. The next morning, someone explains that the new process requires the same team to meet two incompatible deadlines. The concern you interpreted as attitude contains an operating contradiction.

Read the incompatible deadlines as an operating claim. Ask which task each deadline requires and who authorized them. Then identify any separate concern about what the change means for the employee. An objection can contain both a feasible-work warning and a loss the person wants acknowledged. Do not force the whole account into whichever explanation makes the rollout easiest to defend.

Distinguish a new explanation from a changed routine

Levitt and March’s 1988 account of organizational learning describes learning through interpretations of experience encoded in organizational routines. Use that distinction to inspect the work after a rollout message. Find the instruction, system step or approval that employees are expected to use differently. An announced story does not establish that those routines changed. The paper does not certify your transformation plan or explain the cause of every employee objection.

Industrial/organizational psychology, the psychology of work and organizations, helps frame the relationship between expectations and implementation. The objection-source review below is a proposed management method. It classifies the concern so a decision owner can choose a response. It is not a diagnostic instrument for resistance, and it should not turn employees’ willingness to agree with leadership into a test of their fitness for the change.

Ask which part of the objection requires a decision

The decision is which objection needs clarification, which requires a resource or design change, and which reflects a tradeoff leadership must own. Explain what remains open.

Write the objection before drafting a rebuttal. Identify what the person predicts will happen and which part is a consequence they dislike. Ask what decision they want reconsidered. If they cannot yet provide a work example, leave that gap open and arrange a way to clarify it. Do not require a fully engineered alternative before hearing a credible warning about the plan’s feasibility.

For a perceived broken promise, ask what was understood and what created that expectation. Check the relevant communication without assuming that both parties shared the same account. For a feasibility warning, identify the workload, input or system behavior that would prevent the new task. The responses differ: acknowledging a loss is not a resource correction, and correcting duplicate work does not remove every consequence of the change.

Use the change-objection source review

  1. Record the specific objection. Ask what the person expects to happen and which event or work example supports that expectation. Preserve the account before assigning a cause to it. Identify the part of the rollout it concerns and the decision requested. If the concern is broad, choose a concrete instance to inspect. Do not replace an employee’s feasibility warning with a statement about their general openness to change.

  2. Separate consequence from feasibility. Identify the interest or perceived promise at risk, then ask whether the task can operate under the current constraints. Keep both entries when both apply. A person can dislike a change and correctly identify a missing input. They can also prefer the old arrangement when the new one is feasible. Choose a response after making that distinction instead of assuming one motive explains the entire objection.

  3. Verify the operating claim. Trace the relevant work with someone who performs it. Inspect the deadline, resource or system behavior at issue and the authority that can change it. Compare the employee’s example with the approved rollout instructions. Where the claim cannot be checked yet, identify the evidence needed. A senior sponsor’s assurance should not be treated as a demonstration that the task can actually be completed under those instructions.

  4. Choose a matched response. Change an implementation detail when the evidence shows the plan cannot work as designed and the decision is authorized. Explain a retained tradeoff where leadership accepts the consequence. Do not promise to remove a loss that the business decision necessarily retains. If another executive owns the resource or boundary, obtain their answer. Give managers a coherent instruction rather than asking them to persuade employees around an unresolved contradiction.

  5. Report the disposition. Tell the person what the review found, which instruction changes and which decision remains. Assign an owner and review point to any unresolved item. Show the practical correction when one is made. If the concern was not supported, explain the inspected evidence without alleging a hidden motive. Keep later implementation evidence welcome so a disposition does not become a prohibition on raising a genuinely different or newly observed problem.

If the reported contradiction creates an immediate operational risk, obtain the authorized ruling needed for current work. State whether that ruling is temporary or changes the rollout. Do not leave local managers to choose between instructions set by different executives. Return the underlying conflict to the decision owner so the exception does not become an informal way for each team to implement a different version of the change.

Ask for the example before explaining the tradeoff

Use this proposed question to separate concerns without suggesting that either category guarantees reversal. Tell the employee who can change the plan and which parts are already decided.

I want to understand whether this concern is about a consequence we need to discuss or a reason the plan cannot work as designed. Show the example. I will explain which parts can change and who decides.

Summarize the objection back in its own terms and ask whether you captured the practical concern. Identify what will be checked and what can be reported afterward. The person may understand your retained decision while continuing to oppose it. Keep that disagreement separate from the accuracy of their work example. Do not make public support for the rollout a condition of receiving an answer to the warning.

Remove duplicate entry without pretending every concern is resolved

Hypothetical application: Employees object to a new reporting requirement. The review finds both concern about visibility and duplicate entry that consumes real capacity. Leadership resolves the duplicate work while explaining the reporting decision directly.

In the reporting hypothetical, trace the duplicate data through the existing and proposed systems. Confirm who needs the information and whether one source can serve the approved purpose. Address the avoidable entry separately from the concern about greater visibility. If leadership retains the reporting decision, explain that tradeoff directly. Do not present a technical correction as proof that employees’ remaining objection was irrational or had disappeared.

Walk the rollout through the task it changes

Ask an employee to demonstrate the proposed reporting task with an ordinary work item. Note the input, system step and approval required. Compare them with the manager’s announced instructions and the existing deadlines. If the system still demands an old step, assign the correction to someone who can change it. A local team should not be asked to demonstrate adaptability by somehow meeting two incompatible requirements.

Keep consultation honest about its limits

Do not make critics prove loyalty before their evidence is heard. Avoid promising that every loss can be removed. Use employment and privacy advice where the change affects terms, monitoring, or sensitive information.

Identify what employees can influence and what leadership has retained. Obtain employment or privacy advice when the change affects terms, monitoring or access to personal information. Do not imply that consultation guarantees agreement or that refusal to endorse the plan is automatically misconduct. Confirm resources and training before describing them as available. An accurate explanation should help employees understand the actual decision, including the choices that remain constrained.

Return with a disposition for the objection

Review whether verified objections changed implementation and whether the chosen response addressed the underlying issue. Keep disagreement visible when the decision remains contested.

Give the objector the result of the check: confirmed design problem, unresolved evidence question, changed plan or retained tradeoff. Explain the reason and the next owner. Where you corrected the plan, show the revised instruction or system behavior. Where you kept the decision, state what support will be provided. Do not report the concern closed merely because the employee attended the follow-up meeting.

Ask for a case that still fails after the announced correction. If another deadline or system dependency remains, put it into the implementation review rather than treating it as a new attitude problem. Keep the objection’s original meaning visible so a partial response can be recognized as partial. Also record a concern that was not supported by the inspected work without converting that finding into a judgment about the person’s motives.

Edmondson’s 1999 study of team psychological safety defines team psychological safety through a shared belief about interpersonal risk taking. Use that distinction to question how objections are received. An invitation to speak is not evidence that a team feels safe doing so. The paper does not validate this objection review; it helps distinguish hearing a warning from demanding that the speaker prove loyalty before their evidence is examined.

Choose a communication response after identifying the source

Use the change-story framework once the operating decision is clear. Communicating uncertainty addresses questions without settled answers. Handle circulating claims through the rumor response protocol. A decision shaped by threatened loss may need the separate loss-aversion review. None of these is a substitute for checking a concrete implementation warning against the actual work.

Classify an objection so it reaches an owner capable of answering it. Correct a demonstrated design failure, acknowledge a real tradeoff and explain a retained decision. Preserve disagreement where it remains. The useful result is a more accurate account of the change and its consequences, rather than a new label for employees who have not endorsed the rollout.

Sources

Steady at the Top