Every meaningful project I’ve worked on created friction. Every single one.

A new quoting process meant reps couldn’t discount freely anymore. A CRM redesign meant managers had to learn new pipeline stages. A portal launch meant the inside sales team lost the phone calls that made them feel essential. A structured handoff process meant sales reps had to spend 20 minutes documenting context they used to carry in their heads and never share.

In each case, the change was objectively good. Faster quotes. Better data. Happier customers. More scalable operations. And in each case, people pushed back. Not because they disagreed with the goal. Because the change disrupted something that was working for them personally, even if it wasn’t working for the organization.

Change and friction aren’t opposites. They’re inseparable. If you’re introducing change without encountering friction, the change probably isn’t meaningful enough to matter.

Friction is information, not failure

The instinct when friction shows up is to treat it as a problem. Resistance from the sales team? They don’t understand the vision. Pushback from a manager? They’re protecting their territory.

Sometimes that’s true. But more often, friction is telling you something useful. It’s information about what people value, what they’re afraid of losing, and where the real dependencies are.

A sales rep who resists discount governance isn’t necessarily being difficult. They might be telling you that their entire compensation is built around closing deals fast, and the approval process adds two hours to a workflow they’ve optimized over years. The friction isn’t about the principle. It’s about the practical impact on their daily work.

A customer success manager who pushes back on a structured handoff isn’t opposed to better information. They might be telling you that they’re already overloaded, and adding a mandatory review meeting to every new account feels like one more thing on a list that’s already impossible.

When you listen to friction instead of dismissing it, you learn where the change needs to be adjusted. Not abandoned. Adjusted. The goal stays the same. The path to get there accounts for the reality of how people work.

Every change has a cost to someone

This is the part that gets overlooked in business cases and project plans. Organizational change always redistributes effort, authority, or comfort. Something that makes the business better overall can make an individual’s job harder, less autonomous, or less central.

Pricing governance takes away discretion. Before CPQ, a senior rep had full control over pricing. That authority was part of their identity. Introducing floor prices and approval thresholds doesn’t just change a process. It changes the rep’s role. The company gains margin visibility. The rep loses autonomy. Both things are true at the same time.

Process documentation exposes informal power. In every organization, there are people whose influence comes from knowing things others don’t. The person who knows the pricing. The person who knows the product compatibility rules. When you systematize that knowledge into a CRM or a guided selling flow, you’re making the organization less dependent on those individuals. That’s good for the business. It can feel threatening to the person whose value was tied to being the one who knows.

Visibility creates accountability. When nobody can see the pipeline, nobody can question it. When nobody can see the discount patterns, nobody can challenge them. Building dashboards that make operations visible is one of the highest-value things you can do. It’s also politically sensitive. Visibility means people’s work is now measurable. That’s uncomfortable for anyone whose performance was previously judged by narrative rather than data.

Automation changes who matters. A portal that lets customers check order status eliminates the need for the support team to answer those calls. The business case says “redirect that capacity to higher-value work.” The support team hears “40% of what we do is about to disappear.” Even if nobody loses their job, the shift in what they do and how they’re valued is real.

None of these reactions are irrational. They’re human responses to real changes. Ignoring them doesn’t make them go away. It makes them go underground, where they show up as passive resistance, slow adoption, or quiet sabotage of the new process.

The size of the friction tells you the size of the change

Small changes create small friction. Renaming a field in the CRM. Adjusting a report layout. Nobody cares much. Nobody’s world changes.

Large changes create large friction. Redesigning the quoting process. Introducing discount governance. Building a portal that replaces phone-based ordering. These affect how people spend their time, how they’re measured, and what role they play. The friction is proportional to the disruption.

This is useful information. If you’re implementing a CPQ system and nobody is pushing back, one of two things is happening. Either you’ve done extraordinary change management. Or the implementation isn’t actually changing anything meaningful. The tool is new. The way people work is the same.

The absence of friction should make you nervous, not comfortable.

You can’t eliminate friction. You can make it productive.

Name it. The worst thing you can do with friction is pretend it doesn’t exist. When you acknowledge that a change is going to be hard for specific people in specific ways, you earn trust. “I know this approval process adds a step to your workflow. Here’s why it’s there and here’s how we’ve designed it to be as fast as possible.” That’s a different conversation than “here’s your new approval process, please comply.”

Involve the people affected before the decision is made. Not as a courtesy. Because they know things you don’t. The rep who’s been quoting for ten years knows where the real bottlenecks are. The support team knows which questions customers actually ask. The operations manager knows which data is reliable and which is garbage. If you design the change without their input, you’ll design it wrong.

Separate the goal from the method. Most friction isn’t about what you’re trying to achieve. It’s about how. People rarely argue against “we need faster quoting” or “we need better renewal rates.” They argue against the specific implementation. When you separate the two, you can hold firm on the goal while being flexible on the method.

Give it time. The shift from people-centric to process-centric operations takes 12 to 24 months. The system can be ready in weeks. The organizational adoption takes much longer. Planning for that gap is the difference between a project that succeeds and one that’s technically live but practically ignored.

Show results early. Nothing converts skeptics faster than seeing the new process work. The first rep who sends a quote in 30 minutes instead of three days becomes your best advocate. The first dealer who self-serves through the portal and closes a deal without calling anyone becomes proof that the change was worth the discomfort.

The projects that failed and the ones that didn’t

Looking back across ten years of this work, the projects that failed had one thing in common. They treated friction as an obstacle to overcome rather than a signal to listen to. The project team pushed through resistance, launched the system, declared victory, and moved on. Six months later, adoption was low, workarounds had emerged, and the old process was running in parallel with the new one.

The projects that succeeded also had friction. Often more of it, because they were attempting deeper change. But the friction was addressed, not avoided. People were involved in the design. Concerns were heard and incorporated where they were valid. The timeline accounted for the human side of the transition. And the results were shown early enough that skeptics could see the value before they were asked to fully commit.

The friction didn’t go away. It was converted from resistance into engagement. From “this is being done to us” into “this is something we’re building together.”

If nobody is uncomfortable, nothing is changing. And if everyone is uncomfortable and nobody understands why, the change won’t stick. The space between those two is where good consulting lives.