Margaret Heffernan argues that friction creates better solutions. In customer contact operations, this is not just true — it's essential.
Silence is expensive
Contact centers are full of people who know exactly what's broken. Agents know which IVR prompts confuse customers. Team leads know which processes create unnecessary rework. QA analysts know which knowledge gaps drive repeat contacts.
The question is whether anyone is asking — and whether it's safe to answer honestly.
In environments where disagreement is discouraged, problems stay hidden. Agents develop workarounds. Customers keep calling about the same issues. Management sees stable metrics while the underlying system degrades.
Friction as a signal
When someone in operations pushes back on a decision or questions a metric, that's not resistance to change — it's operational intelligence trying to surface.
- "This new process will increase handle time." — Listen. They know something the process designer doesn't.
- "Customers don't understand this communication." — Listen. They hear it every day.
- "The routing change created more transfers." — Listen. They see the system behavior that reports don't capture.
Building teams that disagree well
The goal isn't conflict for its own sake. It's creating conditions where:
- Frontline insight flows upward without being filtered.
- Technical teams and operational teams debate priorities based on evidence, not hierarchy.
- Bad news travels faster than good news — because bad news is actionable.
In customer contact, the cost of silence is measured in avoidable contacts, agent turnover, and missed opportunities to fix root causes. The teams that build the most reliable systems are usually the ones where people feel safe saying "this isn't working."