Resistance is information.

The new scheduling system went live on a Monday. By Wednesday the field crews were pushing back. Jobs were being reassigned by hand. One supervisor was keeping a paper diary next to the screen. In the programme meeting, the slide said "change resistance" and the action was "more communications".

A month later someone finally rode along with a crew for a day. The system was sending them across the county in an order that made sense on a map and none on the road. It didn’t know which streets flooded, which sites needed two people, or which customers were never in before ten. The crews did. The paper diary was the only accurate schedule the organisation had.

The resistance wasn’t a problem with the people. It was the people telling the organisation about a problem with the work.

Why we treat friction as noise

Organisations like things to run smoothly, so friction looks like failure. A team that pushes back looks difficult. An exhausted department looks like a performance issue. The person who keeps asking awkward questions gets a reputation.

So the friction gets managed. More communications. A change champion. A conversation about attitude. Sometimes the person who raised the issue moves on, and the friction seems to stop.

It hasn’t stopped. It has gone underground, into workarounds, spreadsheets and paper diaries, where nobody in charge can see it. The organisation has lost its most honest feedback and congratulated itself on the quiet.

Resistance is not always a problem to fix. Often it is information about the system.

What the research says

In 2008 three researchers, Jeffrey Ford, Laurie Ford and Angelo D’Amelio, published a paper with a pointed subtitle: Resistance to Change: The Rest of the Story. They argued that resistance is often a label applied by the people leading a change to the people receiving it, and that it can be a resource rather than an obstacle. Pushback, they suggested, frequently carries knowledge the change was missing, and engaging with it can make the change better.

Manufacturing worked this out long before. In the Toyota Production System, any worker who spots a problem can pull a cord to stop the line. Stopping is not treated as disruption. It is treated as help, because a problem found at the station is far cheaper than one found by a customer. The friction is the system working.

Most offices have the opposite arrangement. Stopping the line is a career risk, so problems travel downstream until they become someone else’s crisis.

How to tell it’s happening

These are the signs I look for:

• Workarounds are everywhere, and nobody has asked why.
• "Change resistance" appears on a slide without a single example of what people actually said.
• The same concern comes up in every team, and is answered with communications rather than changes.
• The people who raise issues are seen as the issue.
• Exhaustion is treated as a resilience problem rather than a design one.
• Things went quiet after a difficult conversation, and everyone took that as success.

What to do about it

The instinct is to push through. Sometimes that is right: not all friction is wisdom, and some of it really is just discomfort with something new. The skill is telling the difference, and you can only do that by looking.

Keep a friction log. For two weeks, have a team record every complaint, workaround, delay and pushback in one place. Then sort each one: is this about a person, or about how the work is designed? In my experience, most of it turns out to be design.

Go and see. Before deciding what resistance means, spend time where it is happening. A day with the people pushing back will usually tell you more than a month of status reports.

Thank the person who stops the line. If someone raises a problem that turns out to be real, say so publicly. People watch what happens to the first person who speaks up, and decide accordingly.

Read exhaustion as a signal. When a team is worn out, look at how the work is designed before looking at the people. Tired people are often doing the system’s job for it.

Where this connects

Friction as data sits in the See phase of the Oppositism map, alongside Inherited assumptions and Borrowed capability, because it is one of the clearest ways an organisation can see itself. Ignored, it turns into What goes unsaid: friction that has given up. Heard, it often reveals Decisions nobody made, and it is closely tied to What change costs, because some resistance is simply grief for what is being lost.

If you only take one question away, let it be this: what is the friction in our organisation trying to tell us that our reports can’t?