The scene
«I don’t need it. The old way works fine.»
That’s what Ray, a driver with eleven years on the job, told his ops manager when the new AI-assisted check-in app rolled out. No shouting, no drama — just a flat refusal, delivered the same way three other drivers had already said some version of the same thing that week.
The ops manager’s read was simple: Ray doesn’t like change. Write him up if it keeps happening and move on.
Except Ray wasn’t the same case as the other three. One of those drivers was scared the app would be used to track and penalize him. Another genuinely didn’t understand how to use it and was too embarrassed to ask twice. Ray’s actual problem was that his regular route runs through two dead zones with no signal for twenty minutes at a stretch — the app simply doesn’t work there, full stop.
Three «no’s.» Three completely different problems. One blanket response — a warning about attitude — that fixed exactly none of them.
The pattern
Most owners hear resistance and treat it as a single problem: attitude, stubbornness, «doesn’t like change.» That instinct feels reasonable and it’s almost always wrong, because resistance isn’t one thing. It’s three different things wearing the same face, and they call for three completely different fixes.
Using the W-R-A lens:
- Willingness resistance — rooted in fear or safety. This is directly connected to issue #1: someone doesn’t trust that flagging a problem, or being watched by a new system, is safe. The fix is trust-building, not enforcement.
- Readiness resistance — the skill or confidence genuinely isn’t there yet. Someone was told to use a tool, not actually trained on it, and won’t admit that out loud. The fix is real training, delivered without embarrassment attached.
- Ability resistance — a structural blocker that has nothing to do with attitude at all. No signal in a dead zone. No device. No time in the shift to do it right. The fix is removing the actual obstacle — no amount of trust-building or training touches it.
Ray’s case was pure Ability. The ops manager’s response — treat it like a Willingness problem and threaten a write-up — didn’t just fail to fix anything. It taught Ray that raising a real, structural problem gets you disciplined instead of heard, which quietly makes every future issue #1-style safety problem worse too.
The reframe
This is the domain where «resistance» stops being a character judgment and starts being free diagnostic data. Every «no» is telling you something specific — Willingness, Readiness, or Ability — if you slow down long enough to ask which one instead of reaching straight for compliance.
It also explains why domains #1 through #4 keep showing up here in disguise. A Willingness problem is often issue #1’s psychological safety failure wearing a different name. An Ability problem is sometimes issue #4’s undesigned communication flow — someone genuinely never got the information or tool they needed to comply. Resistance isn’t a new problem this domain introduces. It’s where the first four domains’ failures become visible, all at once, in the form of someone saying «no.»
One thing you can check this week
Take one real, current case of someone resisting a tool or process on your team, and sort it with a few quick questions:
- Willingness check: Have they seen leadership admit the tool gets things wrong sometimes? Do they trust what happens to the data it collects on them?
- Readiness check: Were they actually trained, or just told to use it and left to figure it out? Would they be embarrassed to ask a basic question about it right now?
- Ability check: Do they have the device, the signal, and the time in their actual shift to comply — even if they wanted to, right now, today?
- One usable action: run this sort on exactly one person before making any policy change or issuing any warning. Not a fleet-wide rule. One real case, correctly diagnosed, before deciding what to do about it.
Where this fits
This is domain five of twelve. Misdiagnosing resistance is one of the most common — and most expensive — mistakes in a rollout, because the wrong fix doesn’t just fail to help, it actively damages the trust you need for the other eleven domains to work. Sorting out what’s actually behind a specific case of resistance is usually a short conversation. Happy to help you think through one if it’d be useful.
YBOR Logistics AI
Helping logistics companies turn AI, automation and operational data into better decisions… Visit YborLogistics.ai
