You've chosen a solid platform. The workflows make sense. The demos looked clean. You can already see how a tool like monday.com could replace scattered spreadsheets, endless status meetings, and that one shared inbox everyone hates.
Then the rollout starts.
One team member says they're “all good” but never logs in. Another keeps updating the old spreadsheet “just in case”. Managers nod in meetings and then ask for progress reports by email. Nothing looks openly hostile, yet the new system never quite becomes the way work happens.
That's resistance to change. Not always loud. Not always irrational. And not always something to crush.
In practice, resistance is one of the best signals a business gets during transformation. It tells you where trust is thin, where communication failed, where training was too generic, or where the new process doesn't fit the reality of the work. If you treat resistance as sabotage, you'll miss the message. If you treat it as data, you can fix the rollout before it hardens into disengagement.
Why Your Team Pushes Back on New Ideas
A familiar pattern shows up in small and mid-sized businesses. The owner or operations lead finds a better way to run work. Maybe it's monday.com for project delivery, approvals, sales handovers, or job scheduling. The intention is good. The old setup is messy, visibility is poor, and everyone agrees something has to improve.
The surprise comes after the announcement. Nobody says, “I refuse.” Instead, you get partial adoption. Tasks sit incomplete. People ask questions that were already answered. Teams keep one foot in the old process and one foot in the new one. Leaders often read this as stubbornness.
Most of the time, it isn't.
Resistance to change usually starts as a practical human reaction to disruption. People are asking themselves ordinary questions. Will this make my day easier or harder? Will I look slow while I learn it? Is leadership serious this time? What happens to the shortcuts I rely on to get work done?
What owners often misread
A business owner might think, “I've bought a better system. Why is this so hard?” The answer is that people don't adopt software. They adopt new habits, new expectations, and new risks.
That's why the same rollout can produce very different reactions inside one company:
- The high performer worries the new workflow will slow them down.
- The experienced admin worries their hard-won knowledge will be overlooked.
- The manager worries they'll lose control of how information flows.
- The already-stretched team member sees one more thing to learn on a full plate.
Resistance is often less about the tool and more about what the tool changes in daily work.
When you look at it that way, the pushback becomes easier to interpret. It's not proof your team is broken. It's a sign that the rollout has collided with reality.
The better question
Instead of asking, “How do I get them to stop resisting?”, ask, “What is this resistance telling me?”
That shift changes how you lead. You stop trying to win an argument and start diagnosing friction. For a software rollout, that's the difference between forcing logins and building real adoption.
Understanding the Human Side of Resistance
People don't experience change as a flowchart. They experience it as uncertainty.
The brain works a bit like a prediction machine. It likes patterns it already understands. Familiar routines reduce mental effort. When you introduce a new tool, process, or reporting line, you interrupt that prediction system. Even if the change is sensible, the interruption can feel like risk.
That's one reason resistance to change often shows up before anyone has properly tested the new way of working. The reaction is emotional first, rational second. Leaders who miss that tend to over-explain features and under-address fear.
Why good changes still feel threatening
Three forces show up again and again.
First, people protect what already works for them. Even a clunky spreadsheet gives someone a sense of control if they know exactly how it behaves.
Second, learning has a cost. A new board structure in monday.com may be simple on paper, but it still demands attention, memory, and practice. If someone is already under pressure, that extra cognitive load can feel like a penalty.
Third, change can threaten identity. The person who knows how to “get things done around here” may hear “new system” as “your old expertise matters less now”.
What the New Zealand data tells us
In New Zealand, resistance to change underpins 70% of organisational change failures, with employee resistance cited as the primary reason. The same New Zealand data points to key drivers: lack of trust in leadership (41%), insufficient awareness about why change is happening (39%), fear of the unknown (38%), and inadequate information (28%) according to Growth Development's analysis of change resistance in NZ organisations.
Those figures matter because they tell leaders where to look first. Not at attitude. At trust, clarity, fear, and information.
How this shows up in a software rollout
When teams resist a new platform, their behaviour usually maps to one of those drivers:
- Low trust in leadership means staff assume this initiative will fade, get replaced, or create more admin than value.
- Poor awareness of the why means they see the tool as extra work instead of a better operating system.
- Fear of the unknown means they imagine worst-case outcomes. More scrutiny, more mistakes, less autonomy.
- Inadequate information means they can't connect the training session to the actual jobs they do each day.
Practical rule: If people can't explain why the change matters in their own words, they haven't bought in. They've only heard the announcement.
What actually helps
You don't solve a human concern with a licence key. You solve it by reducing uncertainty in concrete ways.
That includes:
- Naming the reason for the change clearly so staff understand what business problem the new system is fixing.
- Showing the future workflow rather than describing it abstractly.
- Giving role-specific training so accounts, operations, sales, and leadership each see what changes for them.
- Creating safe practice time so people can be clumsy before the work becomes live.
- Supporting managers first because teams take their cues from direct supervisors, not from rollout emails.
If your team needs capability support rather than another generic walkthrough, structured monday.com training for teams and leaders is often where adoption work begins.
When Your Company Culture Resists Change
Sometimes the problem isn't the software. It's the environment the software lands in.
A company can say it wants better systems while rewarding the opposite behaviour. It can ask people to adopt a shared workflow while praising heroics, side conversations, and fast fixes outside the system. That's how culture resists change without ever saying so directly.
In smaller businesses, culture is especially powerful because habits travel quickly. If the founder still asks for updates by text, the team learns that the official board is optional. If managers skip the new process when things get busy, staff conclude that adoption only matters when it's convenient.
Signs the system is fighting the change
Cultural resistance usually looks like a pattern, not an isolated complaint.
You have change fatigue
Teams that have lived through failed rollouts remember them. They become cautious with their effort. If past initiatives created more noise than improvement, staff protect themselves by waiting to see whether this one sticks.
That caution is rational. People don't want to invest energy in a tool that leadership won't reinforce.
Questions don't feel safe
When people don't feel comfortable saying, “I don't get this,” they'll hide confusion. That hidden confusion often turns into workarounds, mistakes, or selective compliance.
You can spot it when meetings are quiet but errors keep surfacing later.
Metrics punish the new behaviour
A classic example is asking a team to document all work in monday.com while still judging performance mainly by speed. People then choose the faster short-term path. They skip updates, rely on memory, and treat the system as admin overhead.
The problem isn't motivation. It's misalignment.
Silent resistance is the one leaders miss
The most damaging resistance is often silent resistance. It doesn't arrive as argument. It arrives as delay, ambiguity, avoidance, and polite agreement without follow-through.
Research focused on New Zealand and Australia highlights this pattern. Existing guidance often overlooks covert, non-confrontational behaviours such as delaying meetings or pseudo-compliance, even though they are prevalent in local workplaces. A 2024 New Zealand study of family SMEs also found entrenched traditions can block change during succession, with silent resistance showing up as passive non-participation, as discussed in this Emerald article on silent resistance to organisational change.
That rings true in many SMB environments. People don't always want open conflict. They keep smiling, keep nodding, and keep doing the old thing.
Silent resistance is dangerous because leaders read the tone as support while the behaviour says otherwise.
What silent resistance looks like
Pseudo-compliance
Staff attend training, agree in meetings, and then continue using the old process.Strategic delay
Decisions, approvals, or setup tasks take just long enough to stall momentum.Passive non-participation
People don't object. They don't engage enough for the change to stick.Selective use of the system
Teams update the visible parts of a workflow but keep critical steps offline.
If you're reviewing your rollout and those behaviours sound familiar, the issue isn't just software setup. It's operating culture. In that case, a broader look at monday.com implementation and adoption support helps because the fix usually sits at the intersection of process, management habits, and tool design.
Calculating the Real Cost of Unmanaged Resistance
Unmanaged resistance isn't just frustrating. It's expensive.
Most owners first notice the visible costs. The rollout takes longer than planned. Meetings multiply because nobody trusts the system yet. Leaders pay for software while teams still rely on email, spreadsheets, and manual follow-ups. That creates a double-cost period where you're funding both the old way and the new way at once.
The deeper cost shows up in drift. Work starts happening in different ways across the business. One team uses the board properly. Another updates only when asked. A third keeps a shadow tracker. Once that happens, reporting becomes unreliable and managers spend time reconciling competing versions of reality.
Where the loss actually lands
A new tool is supposed to remove friction. If resistance goes unmanaged, it does the opposite.
- Execution slows down because staff hesitate, duplicate work, or wait for clarification.
- Managers get dragged into basic coordination instead of focusing on planning and decisions.
- Customers feel inconsistency when jobs, requests, or approvals move differently depending on who handled them.
- Your best people carry the load because they compensate for colleagues who haven't adopted the new process.
That last point matters. High performers often become the unofficial glue in a weak rollout. They chase updates, clean up data, and bridge gaps between systems. Over time, that creates fatigue and resentment.
The opportunity cost most businesses ignore
The biggest loss is often the value you never realise.
You didn't adopt monday.com just to own another piece of software. You adopted it to improve visibility, speed up handovers, tighten accountability, and make better decisions. If resistance blocks consistent use, you don't get those benefits. You only get the disruption.
A stalled rollout doesn't fail all at once. It fails through a hundred small decisions to keep the old way alive.
That's why managing resistance early is a commercial discipline, not a soft skill. The longer confusion, distrust, and workaround behaviour remain untouched, the harder they are to unwind.
A Practical Playbook for Leading Successful Change
If resistance is data, your job is to read it properly and act on it fast. For most SMBs, a simple sequence works best. Diagnose what's happening. Plan the rollout around actual concerns. Implement in a way that reduces risk and builds confidence.
Start small, but be deliberate.
Diagnose before you persuade
Don't start with another motivational speech. Start by identifying the form of resistance in front of you.
Some people are confused. Some are overloaded. Some don't trust the rollout. Some privately believe the old process is still better. Those are different problems and they need different responses.
Here's a simple diagnostic table you can use in leadership meetings.
| Symptom (What you're observing) | Potential Cause | Action to Consider |
|---|---|---|
| Team members attend training but don't use the board consistently | Training was too generic or didn't match real workflows | Run role-based sessions using actual jobs, not demo data |
| Managers keep asking for updates outside the system | Leadership habits are undermining adoption | Require project reviews to happen from the board, not from side channels |
| Staff say the tool is fine but deadlines still slip | Silent resistance or unclear ownership | Review where tasks stall and assign visible owners for each stage |
| People maintain parallel spreadsheets | They don't trust the new workflow yet or key fields are missing | Audit the spreadsheet use, then redesign the board to cover the missing need |
| One team adopts quickly while another lags | Local manager behaviour or process fit differs | Compare how each manager reinforces the change and adjust support accordingly |
| Users log in but avoid certain steps | That step may be confusing, unnecessary, or poorly configured | Simplify the workflow, rename fields, or add examples at the point of use |
Plan the message people actually need
Communication plans fail when they sound like launch announcements. Staff don't need slogans. They need context.
Build your message around four questions.
Why are we changing
State the business problem in plain language. For example: “Jobs are being tracked in too many places, which means handovers get missed and leaders can't see bottlenecks early enough.”
That's stronger than “We're improving collaboration.”
What is changing
Be specific. Name the process, not just the platform. “From next month, all client implementation tasks, deadlines, and blockers will be managed in monday.com. Email will no longer be the source of truth for project status.”
How will the change happen
Explain the sequence. Pilot first. Training next. Live date after that. Support channels available throughout. People cope better when they can see the path.
What's in it for me
Every role asks this, even if nobody says it aloud.
- For project managers, fewer status-chasing messages.
- For team leads, clearer workload visibility.
- For executives, cleaner reporting.
- For admins, less duplicate data entry when the board is designed properly.
If your communication doesn't answer the personal impact question, staff will answer it themselves. Usually badly.
For leaders who want a stronger structure around rollout planning, this guide to driving project success is a useful reference because it breaks change planning into practical operating steps rather than theory.
Implement in phases, not in one dramatic launch
Big-bang change sounds efficient. It usually isn't.
A phased rollout gives you room to learn. Start with one workflow that matters and can be observed easily. Project delivery is often a good candidate because task ownership, status, and deadlines are visible.
Then tighten the loop:
- Pilot with a real team so you see where the board design breaks under live conditions.
- Watch for workarounds because they usually reveal missing fields, confusing automations, or poor handovers.
- Adjust quickly rather than defending the original setup.
This matters even more in capability-heavy transformations. The NZ AI Index 2025 shows 87% adoption but only 12% scale in New Zealand, with 32% of leaders identifying lack of internal capability or skills as the top barrier to scaling AI, according to this summary of the NZ AI Index 2025 and barriers to scale. The lesson goes beyond AI. Initial enthusiasm isn't enough. If capability doesn't catch up, scaling stalls.
Train for the real job
Generic training creates false confidence. People leave the session thinking they understand the system, then freeze when they hit the first messy real-world scenario.
Use examples drawn from actual work:
- A delayed supplier task
- A client approval that's blocking delivery
- A sales handover with incomplete information
- A recurring finance review that needs clear ownership
That's also where process design matters. If your workflow is clunky before digitisation, software will merely make the clunkiness more visible. A proper process improvement approach helps clean up the work before you automate it.
A short demo can help teams visualise what a smoother setup looks like in practice.
Build feedback into the system itself
The best change leaders don't wait for quarterly reviews to learn what's failing. They create feedback loops inside the rollout.
In monday.com, that can be as simple as:
- A feedback board where staff log friction points by workflow step
- A weekly adoption review with managers using examples from the board
- An issue owner for each recurring complaint, so concerns don't vanish into discussion
- A visible backlog of improvements so staff can see that feedback leads to changes
This turns resistance into operational input. If several users avoid the same status column or automation, that's not a morale problem. It's a design clue.
Choose champions carefully
Many businesses pick champions based on seniority. That's a mistake. The best champions are credible, practical, and close enough to day-to-day work that colleagues trust them.
Look for people who:
- Translate clearly between business language and team reality
- Stay calm under ambiguity when the rollout gets messy
- Give honest feedback upward instead of protecting the plan
- Model the new behaviour consistently in front of peers
Champions shouldn't act like cheerleaders. They should act like field sensors with influence.
Turning Resistance into Your Greatest Asset
Resistance to change becomes useful when you stop treating it as disobedience.
A missed update can signal that a task owner isn't clear. A parallel spreadsheet can reveal that your board is missing something important. Quiet disengagement can expose low trust in leadership. Slow adoption can tell you the training wasn't good enough for the full complexity of the work.
That's valuable information.
The strongest change leaders listen for what the pushback is saying. They separate noise from signal. They don't overreact to every complaint, but they don't dismiss friction either. They know that a rollout succeeds when the system fits the work, the managers reinforce it, and the team feels capable of using it well.
If you're hitting a wall with change, that doesn't automatically mean your people are the problem. It may mean the message is unclear, the process is misaligned, or the support is too shallow. Those are fixable issues.
Treat resistance as feedback early enough, and it becomes a design tool. Ignore it, and it becomes culture.
If your business is rolling out monday.com, redesigning workflows, or trying to make change stick without burning out the team, Wisely can help you turn scattered processes into practical, supported systems that people use.
