Designing for Friction: Why Resistance Is a Signal, Not a Symptom
Most organizations respond to AI resistance the same way: more communication, more enablement, more pressure to show usage. It rarely works. Not because the people are wrong, but because the diagnosis is.
In almost every AI adoption engagement we've worked on, there's a moment when slowing adoption gets reframed as a behavioral problem, and leadership attention shifts toward acceleration. Gartner predicts that by 2027, more than 40% of AI initiatives will be canceled. In most of those cases, failure won't stem from weak vision or insufficient technical capability. It will stem from a more subtle misdiagnosis: organizations mistaking friction for resistance and responding by pushing harder, rather than pausing to understand what the tension is revealing.
Resistance is rarely the root problem. More often, it's an early indicator of structural misalignment.
The cost of pushing past friction
When AI initiatives encounter hesitation, the natural response is to accelerate. Adoption targets are reinforced. Messaging is intensified. Managers are encouraged to model usage more visibly. These responses aren't misguided; they reflect a genuine desire to maintain momentum and demonstrate progress.
But when friction is treated primarily as a behavioral issue, organizations risk scaling technology before they've reconciled how it fits within existing decision structures, accountability models, and performance expectations. Adoption increases, but confidence remains uneven. Usage grows, but clarity lags.
Over time, that gap widens. Leaders see activity but struggle to tie it to measurable business impact. Employees comply without fully integrating new tools into how they actually work. What began as visible progress becomes incremental improvement rather than enterprise-level impact.
The issue isn't resistance itself. It's the failure to interpret what resistance is signaling.
Friction as strategic insight
Resistance during AI adoption tends to surface in predictable forms: employees questioning outputs, managers hesitating to rely on recommendations, teams raising concerns about accountability or transparency. These reactions are frequently labeled as fear of change. More often, they reflect something more rational — concerns about coherence.
When AI influences decisions, it shifts how authority is exercised and how outcomes are evaluated. When those shifts aren't made explicit, friction follows. Questions arise not because the vision is flawed, but because the operating implications remain unresolved.
Organizations that treat friction as strategic input have a real advantage. They use hesitation to identify where governance lacks clarity. They interpret skepticism as a prompt to increase transparency. They build feedback loops as mechanisms for refining use cases before scale amplifies misalignment.
That approach doesn't slow transformation. It strengthens the foundation.
Designing for friction
Designing for friction means treating resistance as a leading indicator of value realization risk — and using it to determine whether the organization is structurally prepared to scale, rather than accelerating past it.
This shifts how you sequence AI initiatives. Early success isn't measured solely by usage rates or pilot enthusiasm. It's measured by whether decision rights have been clarified, governance has been recalibrated, and performance metrics reflect the new sources of insight being introduced.
In practice, this means applying integration checkpoints before broadening rollout. Before expanding, ask: Have decision rights been clarified for AI-influenced decisions? Do performance metrics reflect the new inputs being introduced? Is accountability explicit or diffused? These aren't process questions, they're signals that your operating model is or isn't ready to absorb what you're scaling.
When tension surfaces, it's a signal to examine operating coherence before expansion continues. Friction becomes a gating mechanism — ensuring that capital deployed toward AI translates into durable improvement, not superficial adoption.
This approach may slow the initial rollout, but it protects the return on your investment over time.
Durability defines advantage
In many organizations we’ve worked with, friction is the moment when pressure to accelerate intensifies. Leaders want to maintain momentum, and teams feel the expectation to demonstrate progress.
The organizations that ultimately see meaningful impact tend to respond differently. Instead of pushing past that tension, they pay attention to what it reveals about how the change is landing inside the organization.
Over time, that difference matters. Adoption moves beyond experimentation and becomes part of how work actually happens.
Designing for friction isn't about slowing progress. It's about ensuring that progress endures.