Frontline adoption suffers when technology is designed for systems instead of people, no matter how much companies invest.

By Elie Mélois
Companies are rushing to implement AI across all business functions, with as many as 64% actively scaling or in early deployment of the technology.
Field workers are especially concerned about technological change and the least willing to adopt it. As AI rollouts progress, 70% of companies are facing some form of “internal pushback.” And in a recent survey of 5,000 frontline workers, the majority (85%) said they’re worried AI and technology will take their jobs, despite only 34% of those workers using AI in their day-to-day work.
While manufacturing and field service companies will need the new tech to stay competitive and sustain productivity, many are accelerating their technology investments faster than they are preparing the people who have to use the tools.
On the frontline, especially, technology must be easy to access, reliable and reflect actual on-the-ground tasks. Organizations that skip those fundamentals and go straight to layering on advanced features like AI assistants, predictive analytics and automated workflows will continue to see poor adoption.
Digital friction is part of the problem. Too often, organizations add technology to existing systems without considering how it is actually used or how it will impact employees’ daily workflows.
The result is a fragmented tech stack that leaves the worker jumping between platforms that don’t speak to one another. A frontline worker may have one app for scheduling, one for payroll and an entirely separate one to access safety documentation, communicate across the floor or make HR requests. Each one adds another icon to a phone screen and another step between a worker and the information they need.
For a frontline employee who’s already managing physical tasks with their hands, it’s not convenient or maybe even possible to stop what they’re doing just to navigate multiple platforms.
Over time, this friction compounds and affects operations. In the LumApps Future of Work Index, leaders listed rapid technological advancement as one of the top workforce disruptions affecting their teams. Another 60% of senior leaders report that digital friction makes internal alignment harder.
When technology fails to meet workers’ needs and is added too quickly, details get missed. Important internal comms get ignored. And change management and adoption stalls.
The tools that earn frontline adoption are the ones workers barely notice. They’re embedded in existing workflows, not layered on top of them.
Here’s what that looks like in practice. When a manager marks a shift as open, AI identifies the right replacement, sends the notification and logs the update automatically. When a technician arrives at a job site, the relevant safety checklist appears in their feed based on what they’re working on, eliminating the need to search across platforms. When a compliance deadline is approaching, the right person receives a reminder without anyone having to manually set it.
None of those examples requires a worker to learn a new interface, attend a training session or change how they do their job. Instead, the technology adapts to the work, not the other way around.

AI on the frontline has a trust problem. One survey found that 36% of frontline workers don’t trust AI, and another third say they don’t understand how it would apply to their work. Addressing that skepticism requires more than a good deployment plan — it requires consistent, clear change management and communication.
A cross-functional approach, involving IT, internal communications, HR and frontline managers, gives workers the context they need before a new platform goes live: What’s changing? Why is it changing? What will it mean specifically for their role?
Measurement matters too. Too many organizations declare a rollout successful based on activation rates or login counts. Those numbers tell you whether workers opened the platform, but they won’t convey whether it’s working. Real success looks like fewer escalations to managers, faster task completion, safer operations and higher employee satisfaction scores. Tying evaluation back to the specific business objectives that drove the investment in the first place is the only way to know whether the technology is actually delivering value.
The value of a new tool isn’t self-evident to someone whose existing habits already get the job done. If the benefit isn’t explained in terms specific to a worker’s actual tasks, resistance is a rational response. A slow platform or a confusing interface gets abandoned quickly.
Successful programs are designed with empathy. Workers need to be shown exactly how a new tool fits into what they already do, from day one. Programs that fail expect workers to figure it out on their own.
Look for mobile-first design, consolidation capability and AI that’s embedded in workflows rather than added on top so the technology can support frontline employees with flexibility. Before committing to a new solution, leaders should involve frontline employees in the process and iterate based on real feedback from the floor.
Technology deployment will keep failing on the front lines as long as it ignores the realities of the work and the people who use the tools every day. Companies that build around the worker — with tools that are simple, consolidated and embedded in how work actually happens — will see the adoption they’ve been chasing. Those that don’t will keep investing in platforms that never reach their full potential.

About the Author:
Elie Mélois brings more than eight years of experience in IT and cloud innovation to his role as CTO of LumApps. He is deeply committed to building cutting-edge solutions and nurturing talented, high-performing teams, driving both technical excellence and product impact.
As manufacturers offer more customization than ever before, managing product complexity has become a critical challenge. Tune in with Dan Joe Barry, Vice President of Product Marketing at Configit, who explores how companies are tackling the growing number of product configurations across engineering, sales, manufacturing, and service. He explains how Configuration Lifecycle Management (CLM) helps organizations maintain a single source of truth for configuration data. The result: fewer errors, faster quoting, and the ability to deliver customized products at scale.