If you’ve ever sponsored a transformation program, you’ve probably felt it: that moment when a process that should be working instead buckles under noise, confusion, or inertia. It’s tempting to reach for a new dashboard, more training, or yet another change champion. But most of the time, the issue isn’t strategy. It’s friction. Or more specifically: the wrong kind of friction, in the wrong places.
Let’s cut through the fluff: systems fail not because people don’t care, but because the wrong thing is too easy and the right thing is too hard. The real work of transformation isn’t just in the plan. It’s in how we design ease and resistance into the everyday experience of work.
The Illusion of Neutral Design
Most organizations unintentionally create exactly the wrong default. We make it effortless to do the wrong thing (submit vague requirements, bypass governance, prioritize pet projects), while making it maddeningly hard to do what actually drives value.
This isn’t neutral. It’s negligence disguised as good intentions.
You can’t afford to assume people will do the right thing just because they “should.” People follow the path of least resistance. Your job is to build that path, on purpose.
Five Levers to Bend Behavior
Every process, every tool, every interaction lives on a friction spectrum. If you’re serious about enabling real change, these are your five levers:
- Cognitive Load – Do people instinctively know what to do next? If not, they’ll stall or improvise. Reduce the decision fatigue.
- Time Cost – Is the process instant or painful? Speed up what you want more of. Slow down what needs reflection.
- Physical Effort – Is the task one-click or multi-form hell? Design for ease where it matters, and intentional drag where it protects.
- Emotional Friction – Does this action feel empowering or embarrassing? Normalize what should be common. Make poor decisions feel… awkward.
- Financial Friction – Are teams rewarded for compliance or for results? Budget isn’t just a constraint. It’s a lever.
These aren’t accidental variables. They’re your control panel.
What Happens When You Don’t Use the Panel
Let’s get real: I’ve seen system integrators launch $20M projects by asking 200 stakeholders on Day 1, “What do you want?” Sounds inclusive, right?
What they got:
– A dumping ground of chaos
– A bloated scope
– Months of expensive cleanup
– And a sponsor one step away from getting fired
Why? Because they made the wrong thing too easy, and the right thing (disciplined prioritization, focused iteration) too hard.
When we flipped it (launched a working prototype on Day 1, then made change requests go through a higher-friction, justified process), everything changed:
- 80% reduction in cost and timeline
- 90% success rate instead of 10%
- A sponsor who still had a job
This Isn’t Manipulation. It’s Responsibility.
Some companies use friction to confuse, delay, and deflect. (Looking at you, insurance claim forms.) That’s a misuse of power. But designing friction with transparency and integrity? That’s leadership.
If you wouldn’t explain your design logic to your own mother, don’t use it.
So, My Free Advice Is This:
Before your next initiative rolls out, stop asking if it’s “simple” or “scalable.” Ask instead:
- What do I want people to do instinctively?
- What’s way too easy right now, and hurting us?
- Where should we slow people down just enough to make them think?
- Are we protecting users, or protecting ourselves?
Because friction isn’t the enemy.
Unintentional friction is.
Make it easy to do what’s right