Why Do We Treat Friction Like a Broken Machine?
How to design systems that use resistance, tension, and failure to move forward.
The Signal Hidden in Pushback
Think about riding a bicycle. If you found a patch of perfectly frictionless ice, you could turn the pedals, but the tires would slip, the brakes wouldn't hold, and you would slide to a halt. In organizations, we tend to treat friction—fear, pushback, and conflict—as design flaws. We try to bypass the person resisting a change or smooth over a tense meeting. But a functional system doesn’t eliminate friction; it relies on it to steer.
When someone pushes back against a new strategy, they aren't just being difficult. Resistance operates exactly like an immune response. It is a localized alarm pointing directly to an unexamined risk or a shared value that feels threatened. If a team member is anxious about an upcoming transition, that anxiety contains concrete data about the system's vulnerabilities. When you stop trying to override their fear and instead ask what they are trying to protect, you discover the blind spots on your own map.
The Flexible Joints of a Team
Some tensions cannot be resolved, and they aren't supposed to be. Take the balance between safety and risk. If a team optimizes entirely for safety, work slows to a crawl under the weight of risk avoidance and bureaucracy. If it pursues risk without boundaries, it burns out its people and damages its reputation.
These opposing forces are not errors to be fixed by choosing one over the other. They function like the opposing muscle groups in a human body. You need both pulling against each other to maintain posture and move forward. Managing this tension means naming the conflicting priorities out in the open, rather than pretending a superficial compromise satisfies both. Beneath every conflicting stance is a human interest trying to keep the entire structure stable.
Learning From Cheap Failures
When people are afraid that a mistake will be treated as a final verdict on their competence, they hide their errors. They stop experimenting, and the entire organization grows rigid. In a healthy system, failure is not a moral failing; it is simply a gap between what you expected to happen and what actually happened. It is the real world testing your assumptions.
The simplest way to lower the stakes is to change the scale of the experiment. Instead of spending six months planning an unverified strategy on paper, build a rough, basic tool or a one-page process in an afternoon. Test it immediately. When you intentionally design small, fast experiments, failure becomes cheap and rich with data. It clears away unearned assumptions and returns the team to a practical, adaptive state of mind.
Closing
The next time a project hits heavy pushback or an experiment falls apart, resist the urge to force your way through it. The friction isn't blocking the work; it is showing you exactly how the system operates.
Key Takeaways
- Treat resistance as an immune response: Look past the emotion to find the unexamined risk or value being protected.
- Stop trying to solve permanent polarities: Use the natural tension between safety and risk to keep the organization balanced.
- Shorten the feedback loop: Build rough, fast prototypes to fail safely before investing deep resources.
- Explore differences before forcing alignment: Spend time understanding what each side is protecting before chasing a compromise.
- Ask the systemic question: When friction occurs, ask: What hidden risk or vulnerability is this resistance trying to alert us to?
Inspiration
Inspired by "The Unexpected Benefits of Fear, Conflict, Failure, and Resistance" by Russ Gaskin.
#SystemsThinking #Leadership #Organizational_Change #Management #Culture
Comments