Resistance to Change Worksheet
Resistance to Change Worksheet
The new code review process met pushback in week one, so leadership scheduled a second launch session. The pushback was four different problems, and one of them was correct.
A platform group made two-approver reviews mandatory. A staff engineer warned it would block incident hotfixes. Others wanted it phased in by service, a few expected it to be abandoned like the last process, and the long-time gatekeeper of the payments code objected to everything. All of them got the same deck, the hotfix warning went quiet, and the first incident under the new rule ran an hour longer than it needed to.
(Composite example, assembled from patterns common in engineering organisations rolling out new process and tooling. The figures are illustrative.)
This worksheet treats resistance as information about your change, your plan, your trust level or what the change means to someone, not as a person problem. It starts from the objection: log it, sort it, then answer the cause you found.
Step 1: log the signal before you argue
☐ What exactly was said, and by whom? ______
☐ Do I respect this person's judgement on similar topics? (Y / N)
☐ Is the objection specific, technical and falsifiable, or vague?
☐ Are several people raising different objections (independent observation) or the same one (coordinated)?
☐ Does the objection include data I don't have?
Rule of the road: one of the most expensive leadership failures is refusing to update on real evidence. Read the signal before you defend the plan.
Step 2: run the four-case check
Work from the top, starting honestly at case 1.
Case | Signs to tick | Response |
1. The change is wrong | ☐ Resisters whose judgement I respect ☐ Specific, falsifiable objections ☐ Objections differ from each other ☐ They hold data I lack | If two or more are ticked, stop defending and evaluate the claim on its merits. Say publicly if the direction was off. |
2. The plan is wrong | ☐ They back the goal if you ask them outright ☐ Objections are about how, not whether (order, timeline, scope, rollback) ☐ They can name a better plan | Revise in the open and bring resisters into planning. Adopt one credible objection where everyone can see it. |
3. Trust is low | ☐ Vague objections ☐ References to past changes that went badly ☐ The same group resists every change ☐ New hires don't share it | Ship in smaller, lower-risk pieces, or name what went wrong last time and what is different now. Don't insist trust is fine: the team hears that their experience didn't happen. |
4. Identity or power | ☐ Objections out of proportion to the change ☐ Their role is directly affected ☐ Each answered argument is replaced by a new one | Raise it gently in a private 1:1, never in a meeting: "The technical objections don't quite add up for me. What else is going on?" |
For case 4, once the loss is named ("I'd go from expert to beginner"), rebuild the role around existing expertise. The reorg transition playbook covers that kind of loss.
Step 3: run the 1:1 conversation
Ask these in order. Listen and don't argue.
"Help me understand what you'd recommend instead."
"What's the strongest version of your concern: the worst case you're worried about?"
"What conditions would make this workable for you?"
The last question opens space. Resisters often haven't articulated their own conditions, and what they need can turn out smaller than the resistance suggested.
☐ I asked all three.
☐ I wrote down their conditions: ______
☐ The conditions are smaller than the resistance implied. (Y / N)
Step 4: decide whether to push through
Push through only for a compliance deadline, an existential threat, or a decision made above you after input was sought. Then:
☐ Say the change isn't optional and that I've heard the concerns.
☐ Explain why, without spin.
☐ Be honest about what I can and cannot change.
☐ Don't claim a consensus that doesn't exist.
☐ Don't penalise disagreement that still respects the decision.
Many teams will execute a change they don't love, as long as nobody insults them by pretending they love it.
Step 5: check the anti-patterns
Circle anything you catch yourself reaching for.
Compliance theatre: mandated sign-off, so the team complies on paper only.
Villain framing: talk of "a few negative voices", which turns the team against itself.
Asymmetric urgency: "no time to discuss" alongside "we need everyone on board".
The PIP threat: performance-managing the people who push back. They are usually the early warning, and removing them removes the warning.
Step 6: check for silence
Active resistance is information. A sudden silence can matter more.
☐ Has a previously vocal engineer recently gone quiet? Name: ______
If yes, treat it as more urgent than the loud pushback. That engineer has often concluded engagement is pointless (job-hunting, quiet-quitting or burning out), or their concern was resolved. Don't assume which: ask.
How to use it
Who: the change lead, with one peer who will challenge the diagnosis. Thirty minutes per round of objections, plus the 1:1s.
Output: a log of objections sorted into the four cases, a response for each case, and the conditions people named.
Done when: every objection has a case and a response, at least one credible objection has been visibly acted on, and every quiet engineer has had a conversation.
Where this changes
For a small change on a small team, skip the table and just run step 3. In large or regulated organisations, keep the step 1 log as a record, because "we heard the concerns" may need evidence later.
Run the change readiness checklist before the change and this worksheet when pushback arrives. For the reasoning behind the four cases, read managing resistance to change in software teams.
Final takeaway
Pushback is a reading of your change, not a verdict on your people. Sort it before you answer it, act visibly on the objection that is right, and worry most about the engineer who has stopped objecting.
Sources
Ford, J. D., Ford, L. W. and D'Amelio, A., "Resistance to Change: The Rest of the Story," Academy of Management Review 33(2), 362–377, 2008.
Piderit, S. K., "Rethinking Resistance and Recognizing Ambivalence: A Multidimensional View of Attitudes toward an Organizational Change," Academy of Management Review 25(4), 783–794, 2000.
Morrison, E. W. and Milliken, F. J., "Organizational Silence: A Barrier to Change and Development in a Pluralistic World," Academy of Management Review 25(4), 706–725, 2000.
Edmondson, A., "Psychological Safety and Learning Behavior in Work Teams," Administrative Science Quarterly 44(2), 350–383, 1999.
