Workplace Tool Resistance: Strong Signs The Rollout Is The Problem

This voice experience is generated by AI. Learn more.This voice experience is generated by AI. Learn more. gettyA new workplace tool can look like a smart investment on paper and still get a lukewarm reception from the employees expected to use it. Introducing new technology means changing not just what people use but also how they work—and that transition doesn’t always go smoothly.

When employees are slow to embrace a new tool, it’s easy for leaders to assume they’re simply resistant to change. However, a lack of enthusiasm or engagement doesn’t necessarily mean employees are unwilling to adapt; the problem may lie in how the technology was introduced. Below, members of Forbes Technology Council share signs that a new tool’s rollout—not the workforce—may be the real obstacle to adoption.

We built CV-Tinder, an AI tool to match CVs to projects. Our team hated it. They stuck to their old habit: sending a quick chat to team leads instead of opening a new interface. We fixed it not with a smarter model but by moving the tool into the chat they already use. Now they just message the AI bot, which pulls matches instantly. Don’t fight habits; route through them. – Andrew Babkin, Azati

Look for consistent friction across the employee group. If people across roles and experience levels are creating workarounds, avoiding key features or taking longer to complete familiar tasks, that is a rollout signal—not simply resistance to change. Leaders should examine workflow fit, integrations, training and whether the tool’s value was clearly demonstrated. – Karan Alang, Versa Networks Inc.

Forbes Technology Council is an invitation-only community for world-class CIOs, CTOs and technology executives. Do I qualify?

When different employees keep asking the same things, that is often a signal of a poor rollout. Good adoption requires more than introducing a tool; people need to understand why it matters, how it fits their work and what changes for them. – Darko Pavic, Fiscal Solutions

Adoption requires motivation, opportunity and capability, and two out of three isn’t enough. Nonobvious intrinsic or nonintrinsic rewards can stop adoption; for example, if the tool democratizes someone’s expertise or credibility, they may fight it. Opportunity is about the resources required, with the scarcest resource typically being time; if the return on time from the new tool is lower than other pursuits, adoption fails. Capability is the expertise and experience needed to derive value from the new tool—as an analogy, “It’s a nice car; too bad it’s a stick shift.” – Rex Lee, Canadian Tire Corporation

Listen for “it can’t do it” when the real feeling underneath is, “I don’t know what it means for me if it does.” Self-preservation often shows up dressed as technical skepticism. When I’m hearing from engineers that the agent is slowing things down, I have to ask whether they actually believe that or whether they haven’t been given a clear picture of what success looks like for them on the other side of it. If I haven’t made them feel secure first, then I haven’t done my job as a leader. – Paul Deraval, NinjaCat

Ask anyone why the tool exists. If no one can say what it changes for their role, the rollout failed before training began. People do not resist technology; they resist uncertainty about their value. Leaders who communicate features instead of purpose manufacture the resistance they later blame. Explain the “why” and redesign the role, and adoption follows. – Brendan Hooft, ESPER

I look for resistance concentrated around the same workflow. If employees repeatedly need workarounds, extra steps or manual support despite training, the rollout may be the issue. Leaders should examine usability, timing, training and workflow fit before treating resistance as a people problem. – Natasha Bryan, AlphaRidge

If employees keep asking, “Why are we doing this?” that’s a sign to look at the rollout. At NU, we’ve seen that people engage when they understand how a tool changes their day-to-day work. As an AI-native executive search firm, we’ve had to make that connection clear as we rethink how the industry operates. – Nada Usina, NU Advisory Partners

Look for shadow workflows. If employees immediately return to spreadsheets, email or the old system, don’t assume they’re resistant to change. They may be telling you the new tool added friction or failed to fit the work. Adoption problems are often product feedback in disguise. – Cheryl Johnson, Betterworks

A key signal is consistent resistance across normally adaptable employees—especially when they report the same confusion, extra work, lack of training or unclear purpose. When people create workarounds instead of using the tool, leaders should examine the rollout, communication and workflow design before blaming the people. – Deepali Kaushik, NBCUniversal

Watch for resistance that’s consistent across high performers and low performers alike. Skepticism that cuts across skill levels and attitudes almost never points to a people problem; it usually means employees were not given enough context about why the tool was chosen, enough time to learn it without pressure, or enough input before the decision was made. – Philip Ellis, chrt

Having implemented supply-chain and commercial capabilities, I can point to three common reasons for poor adoption: 1. The tool does not solve a real user need. 2. It isn’t intuitive enough to fit the flow of work. 3. It’s disconnected from the business outcomes people are measured on. Address all three in design: Start with the business outcome, build around the user, and design for value. – Venky Ramesh, LatentView Analytics

One signal is when resistance is loudest among the most experienced employees. Senior staff who push back are often protecting institutional knowledge about why the old process worked that never surfaced during planning. That pattern points to a rollout that skipped understanding current workflows before designing the replacement. The people who knew the most weren’t consulted before something was built to replace what they built. – Dan Haiem, AppMakers USA

Watch what happens to productivity, not just adoption. If experienced employees who were productive with the old process suddenly take longer to complete basic work, that is a signal worth paying attention to. It may not be resistance to the new tool; the tool may simply be adding friction. Before blaming the people, leaders should ask what changed in the way they work. – Venkatesh Sankaran, Saguna Consulting Services LLC

One signal is when capable employees are not rejecting the goal but are struggling with unclear training, weak integration or extra steps that slow real work. In healthcare, this is like adding a tool that documents care but disrupts the clinical flow. If people create workarounds, duplicate tasks or ask the same basic “how do I use this?” questions, leaders should examine the rollout before blaming adoption. – Will Conaway, Tuxedo Cat Consulting

Check whether leadership appears in the usage data. When we roll out a tool, the first name I look for in the metrics is mine—if executives mandated it but never touched it, resistance isn’t defiance; it’s mimicry. Teams adopt what leaders do, not what they announce. A rollout where the org chart’s top half is invisible in the logs is a memo, not a change. Fix that before blaming the people. – Kiran Kodithala, N2N Services, Inc.

The clearest signal of employee resistance is high adoption for basic tasks but a total collapse of usage when it comes to more advanced features. If employees enthusiastically log in to conduct basic tasks but abandon the tool when workflows get complex, they aren’t lazy; they lack proper context. This pattern proves they want to use the tool, but poor training or bad process integration is blocking them. The rollout failed to map the tool to real-world work. – Mark Brown, The Mark of Security Ltd.

The real signal is upstream: You can’t say, with data, how people used the old tool. If you never measured the workflow you’re replacing, you can’t tell a bad fit from a bad attitude, so “they resist change” wins by default. We poll actual usage before switching. When there’s no baseline for the old workflow, the rollout is the problem, not the people. – Andrew Siemer, Inventive

Look for adoption that happens only after hours. If employees must learn the tool while meeting unchanged output targets, the rollout has made learning a personal cost. Give people protected practice time and temporarily adjust expectations. Someone who cannot afford to be slower this week has a rational reason to avoid a tool that might help next month. – Mani Padisetti, Almost Magic Tech Lab