Organizations often maintain a collection of thoroughly evaluated tools. After careful assessment, convincing demonstrations, and enthusiastic approval, a pilot group adopted the software. Yet, during the journey from “the pilot group loved it” to “everyone uses it,” the momentum gradually dissipated.
The tool didn’t fail because it was bad. Instead, it failed because it never crossed the gap between the people who were eager to use it and the far larger group who were not. That gap has a name. Understanding it is one of the most useful things an L&D or change practitioner can do.
The Curve Nobody Warns You About
More than 50 years ago, sociologist Everett Rogers described how new ideas and technologies spread through populations. Adoption, he observed, doesn’t happen all at once. Instead, it moves through predictable groups: a small band of innovators, then early adopters, followed by the early and late majorities, and finally the laggards.
Later, technologist Geoffrey Moore added an important insight for the business world. He noted that between early adopters and the early majority lies a “chasm.” This is where many promising technologies stall and never recover.
Most people think about this curve in the context of products spreading through markets. But the same dynamic plays out inside organizations whenever a new system is rolled out. It’s arguably more brutal internally because there’s no marketing budget to push it through—just a workforce being asked to change how it works. Mapping this onto the internal version of the enterprise technology adoption curve is the sharpest diagnostic for understanding why a rollout stalls.
Why the Majority Resists
Here’s the pattern: Innovators and early adopters—naturally curious, technically confident, and often pilot volunteers—adopt quickly and enthusiastically. Their success creates a dangerous illusion. Leadership sees high usage in this group and concludes the rollout is working. But these people were always going to adopt. They’re the easy 15%.
The real test comes next: reaching the early and late majority; those who didn’t volunteer, are busy, have workarounds, and are skeptical the new tool is worth the disruption. This internal chasm is where most enterprise technology quietly fails.
It’s tempting to label the majority’s reluctance as stubbornness or “resistance to change,” as if a stern email from leadership could fix it. This framing is both unfair and useless. The majority resists for reasons that, from their perspective, are entirely rational.
They have less tolerance for friction than early adopters. An innovator might wrestle with a clunky interface for the novelty, but a busy manager in the majority will abandon it if it costs more time than their old method saved. Poor integration and unintuitive navigation aren’t minor issues; they’re decisive. The majority doesn’t need a vision; they need the new way to be demonstrably easier at the exact moment they’re working.
They also face higher switching costs. The majority has muscle memory, informal shortcuts, and a network using the old system. Adopting the new tool means giving that up for a period of feeling slow and incompetent, an unpleasant experience training decks rarely address.
And they’ve been burned before. Most employees have lived through rollouts announced with fanfare, only to be abandoned months later. Their skepticism isn’t irrational; it’s pattern recognition. Why invest in learning something that might not last the year?
Where L&D Usually Goes Wrong at the Chasm
When a rollout stalls, organizations often double down on what worked for early adopters: more announcements, training sessions, or mandates. This approach rarely succeeds because it misdiagnoses the issue. Early adopters needed minimal support, driven by their own motivation. Applying the same model to the majority, then blaming them for failure, is a critical error.
One-time training events, in particular, fail the majority. After the session, employees return to their desks, encounter situations the training didn’t cover, and have no immediate support. Confidence falters, old workarounds resurface, and the tool loses another user. The training isn’t flawed; it’s delivered at the wrong moment. The majority needs assistance within the tool, during actual work tasks.
Crossing the Chasm Successfully
If the majority resists for rational reasons, crossing the chasm requires removing those barriers, not forcing compliance. Several principles consistently help:
First, stop interpreting early-adopter enthusiasm as proof of success. Measure adoption based on the majority’s behavior. The key question isn’t whether people are using the tool, innovators always will, but whether usage spreads beyond enthusiasts and sustains over time. This is the only reliable indicator of crossing the chasm or being stuck at its edge.
Second, make the new way genuinely easier at the moment of work. The majority performs a cost-benefit analysis every time they use the tool. Win this by embedding help directly into tasks, ensuring the new method feels lighter than old workarounds. If guidance is buried in a manual or forgotten training module, adoption will fail.
Third, treat this as change management, not just enablement. Adoption at scale is a human transition, not a knowledge transfer. Acknowledge the switching cost openly, allow the majority to feel slow temporarily, and provide structured support, not just a memo and a deadline. People cross the chasm when the transition feels safe, not when it’s forced.
Fourth, recruit the majority’s peers as guides. The majority distrusts innovators, who seem too different. They trust colleagues who share their skepticism. Identify respected members of the early majority and empower them as credible guides. This moves the middle more effectively than any executive endorsement.
Leave a Reply