When a team objects to another platform, workflow or reporting rule, leaders often reach for a convenient diagnosis: people do not like change. That explanation may protect the proposal, but it tells you very little about the problem. The objection could be evidence of poor design, conflicting priorities, missing training, a reasonable concern about customers—or a team that has absorbed too many unfinished changes without time to stabilise.
Calling all hesitation “resistance” turns a management decision into a personality judgement. A better response is to review the organisation’s change load: the total demand created by changes that are being proposed, learned, repaired or still producing consequences.
This is not an argument for avoiding improvement. It is a method for deciding whether to proceed, redesign, sequence or pause—before the next useful idea becomes one more layer of work that nobody can use reliably.
The word resistance hides different signals
An objection is information. Its meaning depends on what the person is protecting and what evidence they can offer. At least five signals can sound like resistance in a meeting:
- Purpose disagreement: the person does not believe the change solves a priority problem.
- Design evidence: they can see a failure mode that the project team has missed.
- Capability gap: the new process requires knowledge, time or access they do not yet have.
- Loss concern: the change affects autonomy, status, relationships, working patterns or professional identity.
- Cumulative overload: the proposal may be sensible alone, but it lands on top of other unfinished changes.
These signals need different responses. A clearer presentation may address purpose confusion. A design objection requires investigation. A capability gap requires training or simplification. A genuine employment change may require formal consultation. Overload requires sequencing and removal of competing demands—not another motivational speech.
Map the live change portfolio, not just the new project
A leader usually sees the initiative they sponsor. An employee experiences the combined portfolio: a new customer system, revised targets, a changed rota, an artificial-intelligence assistant, a new approval route and the defects left by last month’s migration.
Create a one-page change-load register before approving another launch. Include formal projects and smaller changes that still alter how work is done.
| Question | Evidence to record | Warning sign |
|---|---|---|
| What is changing? | Tool, process, role, target, policy or customer promise | The change has no named outcome |
| Who absorbs it? | Roles, shifts, contractors, customers and support teams | The same small group appears in every row |
| What must be learned? | Training, practice, new judgement and error recovery | “It is intuitive” replaces a training plan |
| What work increases? | Data entry, checks, meetings, exceptions and reporting | Extra work is described as negligible without measurement |
| What stops? | Tasks, fields, meetings, tools or old rules to remove | Nothing is retired |
| What remains unstable? | Defects, workarounds, disputed ownership and backlogs | A previous launch is called complete while repair continues |
| When can the team recover? | Stabilisation window, reduced change and review date | Another launch begins immediately |
The register is not a score designed to make every change look risky. It creates a shared picture of simultaneous demand. It also prevents invisible repair work from disappearing behind a project’s “completed” status.
Ask what will stop when something new starts
Many organisations treat change as addition. A new tool arrives, but the spreadsheet remains “just in case”. A new meeting is created, but the old report still has to be produced. A faster channel is introduced, but expectations expand until every channel must be monitored.
For each proposal, require a retirement decision. Which task, tool, field, meeting or approval will be removed? If nothing can stop, say honestly that the change increases workload and decide whether the benefit justifies it.
This question also exposes double-running periods. Parallel systems may be necessary during migration, but they need an owner, an end date and criteria for switching off the old route. Without those controls, temporary duplication becomes permanent work.
Consult while the proposal can still change
The UK Health and Safety Executive’s Management Standard on change says employees should receive timely information, understand probable effects, know the timetable, have access to support and have opportunities to influence proposals. That is more demanding than announcing a finished decision and inviting questions.
Acas similarly describes consultation as a genuine two-way discussion. In its guidance on proposed contract changes, it says employers should listen to objections, consider alternatives and be prepared to revise proposals. Contract changes can carry specific legal duties and risks, so leaders should obtain appropriate advice rather than treating this article as a substitute.
Even where a proposal does not alter contractual terms, the underlying principle is useful: consultation is only credible if input can affect scope, timing, design or support. If every important decision is already fixed, call the meeting communication—not consultation.
Separate the objection from the objector
Evaluate the claim before evaluating the person. Ask for the specific task, customer, risk or dependency involved. Then test it.
- What is the predicted failure?
- Which users or customers would experience it?
- What current work would collide with the change?
- What evidence would show that the concern has been resolved?
- Could a small pilot distinguish a real risk from a preference?
This prevents two opposite errors. Leaders should not dismiss evidence because its messenger sounds anxious, tired or unpopular. They should also not allow a vague dislike to block necessary work indefinitely. Specific claims can be investigated; labels cannot.
Protect stabilisation as real work
Implementation is not finished when software goes live or a policy is announced. People still have to build accurate routines, recognise exceptions, repair mistakes, answer customers and decide which old habits no longer apply.
A July 2026 cross-sectional study of 1,769 nurse leaders in 76 hospitals in Hubei Province identified low, moderate and high change-fatigue profiles. The researchers found associations between profile membership and factors including health, income satisfaction and dimensions of job crafting. The study cannot establish causation, and its healthcare setting in one Chinese province limits generalisation to other sectors. It does, however, caution against treating change responses as one uniform attitude.
In practice, a stabilisation window can include fewer launches, protected training time, removal of temporary workarounds, defect resolution, updated documentation and a review of whether the intended benefit is actually appearing. Recovery is not inactivity. It is when a change becomes dependable enough to support the next one.
Illustrative example: a five-person online shop
Illustrative scenario—not a reported company result: a five-person online shop wants to introduce an AI-supported customer-service platform. The team is already migrating product data, learning a new returns process and clearing a backlog caused by a payment-system change.
The platform could still be useful. A change-load review shows, however, that the same two employees own all four changes. The original proposal expects them to configure the tool, write response rules, check generated answers and continue answering every ticket manually during the pilot.
Instead of labelling their objection resistance, the owner changes the sequence: finish the returns workflow, remove one duplicate spreadsheet, pilot the new platform on delivery-status questions only, reserve two hours a week for review and set a decision date after four weeks. The proposal becomes smaller, testable and reversible. It may still be rejected, but now the decision is based on evidence rather than pressure.
Use three gates before launch
1. Purpose gate
Can the leader name the user problem, desired outcome and evidence of success without referring to the tool itself? “We need AI” is not a purpose. “Reduce avoidable delivery-status enquiries while preserving accurate escalation” is.
2. Capacity gate
Has the team identified implementation work, training, parallel running, exception handling and the tasks that will stop? If capacity depends on unpaid overtime or invisible emotional labour, the plan does not yet have capacity.
3. Recovery gate
Is there a stabilisation period, an owner for defects, a rollback route and a date for evaluating the outcome? A launch without recovery criteria transfers uncertainty to employees and customers.
Know when to proceed, redesign, pause or stop
- Proceed when the purpose is clear, capacity is real, consultation has improved the plan and recovery is funded.
- Redesign when the outcome matters but the current scope, sequence or support model is weak.
- Pause when unresolved changes are competing for the same people or when critical evidence is missing.
- Stop when the proposal no longer solves a priority problem, duplicates an existing capability or creates more risk than value.
Stopping a weak change is not a failure of ambition. It preserves attention for work that can genuinely improve the organisation.
The leadership habit to keep
When someone says, “We cannot take on another change,” do not immediately agree or dismiss them. Ask them to show the load. Map the work, investigate the objection and decide what can stop. Then give the team a real opportunity to influence the answer.
Good leadership does not eliminate disagreement. It converts disagreement into evidence—and ensures that useful change arrives in a form people can learn, operate and sustain.
For a broader psychological framework, read Overcoming Change Fatigue: A Psychological Framework for Business Transformation.
Sources and research limits
- Health and Safety Executive: Management Standards—Change.
- Acas: Consulting about employment contract changes.
- Wu and colleagues (2026): Multicenter analysis of change fatigue and job crafting among nurse leaders in China.
Sources were checked on 16 October 2026. The empirical study is cross-sectional and sector- and location-specific; it should not be read as causal evidence for every workplace. This article provides general leadership and psychological decision support, not legal, clinical or occupational-health advice. The featured image is an original conceptual AI illustration created for this article.
Discover more from Marychuks.com AI, Psychology, Business & CreativeVerse
Subscribe to get the latest posts sent to your email.
