Reducing Workflow Friction
Ask most organizations how they plan to drive adoption of a new system, and they'll describe a training plan. Sessions, modules, a launch webinar, maybe a certification. It's a reasonable answer, and it's also aiming at the wrong target. Because the single biggest determinant of whether people actually use enterprise software isn't how well they were trained. It's what using the software feels like, every day, in the middle of real work. That daily felt experience—the friction, the confusion, the small frustrations that accumulate into abandonment—is the digital employee experience. And it, far more than any training plan, is your real adoption strategy.
Software Doesn't Get Abandoned For Lack Of Features
There's a persistent myth in enterprise technology that usage problems are capability problems—that if a tool isn't sticking, it must be missing something, and the fix is more functionality. The evidence points the other way. Research from SaaS-management platforms consistently finds that somewhere between 30% and 50% of enterprise software licenses go unused, depending on how you define it, and a large share of installed software sits effectively idle. That waste is rarely because the tools couldn't do the job. It's because people never folded them into how they actually work.
The lived reality behind those numbers is quietly grinding. The average enterprise now runs hundreds of applications, and employees reportedly toggle between them well over a thousand times a day, losing a meaningful slice of every workday to context-switching alone. Each new tool arrives into an already-crowded, already-exhausting digital environment. It doesn't get a fresh, patient user; it gets someone who is cognitively taxed, mid-task, and one frustration away from reverting to whatever they were doing before.
In that environment, features don't drive adoption. The absence of friction does. As eLearning Industry's own examination of the challenges of enterprise software adoption reflects, the barriers are overwhelmingly experiential—poor integration, confusing navigation, and the sense that the tool is fighting the user rather than helping them.
Friction Is The Real Adoption Killer
It helps to be concrete about what "friction" actually means, because it's easy to wave at abstractly and hard to design against unless you name it. Friction is the moment an employee reaches a screen they don't understand and has no idea where to get help—so they guess, get it wrong, and quietly conclude the tool is "too complicated."
Friction is having to leave the tool to find out how to use the tool: opening a separate manual, searching a knowledge base, messaging a colleague, or filing a support ticket and waiting. Every one of those detours breaks concentration and adds a small tax to using the software, and small taxes compound fast.
Friction is cognitive load—being asked to hold too many steps in your head at once, in a tool you use occasionally, under time pressure. The early adopter tolerates this; the ordinary employee does not.
And friction is inconsistency: when the new tool behaves differently from everything else the employee uses, forcing them to context-switch not just between apps but between mental models. Each of these frictions is individually small. Collectively, they are the difference between a tool that gets adopted and one that gets abandoned—regardless of how good its feature list looks in a demo.
Why This Is An L&D Problem, And An Opportunity
At first glance, digital employee experience sounds like something for IT, or for a UX team, or for whoever procured the software. But look at what actually reduces friction and the L&D fingerprints are everywhere. Reducing friction means anticipating where people will get stuck and putting help exactly there. It means designing for the occasional user, not the power user. It means building confidence at the moment of need rather than in a session weeks earlier. Those are learning-design competencies, applied to the flow of real work rather than to a course.
This is the deeper promise of learning in the flow of work. Its usual framing is about continuous development—learning without leaving your desk. But it's equally a friction-reduction strategy. When guidance surfaces contextually—the right tip on the right screen at the right moment—the employee never has to leave the tool to learn the tool. The detour disappears. The cognitive load drops. The small tax on usage that was quietly killing adoption is removed. Framed this way, in-context learning isn't a nice-to-have layered on top of adoption; it is the adoption strategy.
Designing For The Experience, Not Just The Rollout
If the digital employee experience is what determines adoption, then the work shifts from planning a rollout event to designing an ongoing experience. A few things change in practice:
- Map the friction before you map the training.
Before designing a single module, walk the actual workflows and find the moments where an ordinary employee—not an enthusiast—will get stuck, confused, or forced to leave the tool. Those friction points, not the feature list, are your real curriculum. Design support to meet each one where it occurs. - Design for the occasional user.
Most enablement is unconsciously built for the person who'll use the tool constantly and become fluent. But adoption lives or dies with the majority who use it occasionally and never build muscle memory. That user needs help to be available every time, in context, because they will forget between uses—and that's normal, not a failure on their part. - Measure the experience, not just completion.
A completion rate tells you people attended. It says nothing about whether the tool feels usable at 3 p.m. on a busy Tuesday. Track the signals that actually reflect experience: whether usage sustains past the launch spike, where people repeatedly get stuck, how often they abandon a task partway through. Those are the metrics of a digital employee experience worth managing. - Reduce the total load, don't just add to it.
It's worth remembering that every new tool, and every new training requirement, adds to an already-overloaded digital day. Sometimes the most powerful adoption move is subtraction—removing steps, consolidating tools, or eliminating a detour—rather than adding another layer of guidance on top. The goal is a lighter experience, not a more instrumented one.
The Strategy Hiding In Plain Sight
The organizations that win adoption aren't the ones with the most sophisticated tools or the most exhaustive training catalogs. Plenty of companies have both and still watch their software sit unused. The winners are the ones who understood that adoption is an experience problem—that people use tools which help them and abandon tools which fight them, and that the entire game is played in the small moments of daily work where friction either appears or doesn't.
As eLearning Industry's roundup of the learning technology trends shaping 2026 makes clear, the center of gravity in workplace learning is moving decisively toward the flow of work—toward support that lives inside the tools and workflows people already use. That's not only a learning trend. It's an adoption trend, because the two turn out to be the same thing.
So before you build the next training plan, ask a different question. Not "how will we teach people this tool?" but "what will using this tool actually feel like, every day, for the ordinary employee—and how do we make that experience good enough that they choose to keep using it?" Answer that, and you've built an adoption strategy that a training calendar could never deliver. The digital employee experience was the strategy all along.
