The Friction Project
How Smart Leaders Make the Right Things Easier and the Wrong Things Harder
by Robert I. Sutton & Huggy Rao
The 60-Second Take
In The Friction Project, Stanford professors Robert Sutton and Huggy Rao argue that friction is not inherently bad. The leader's job is to remove the wrong kind — pointless meetings, unnecessary approvals, bureaucratic red tape — while preserving the right kind: the resistance that forces deliberation before consequential decisions. A practical operating framework for any leader tired of watching good work get strangled by organizational overhead.
The Friction Project: The Science of Making the Right Things Easier
Most organizational improvement efforts start from the same assumption: friction is bad and should be reduced. Fewer meetings. Faster approvals. Simpler processes. Less red tape. The instinct is understandable. Bad friction — the unnecessary, pointless, demoralizing kind — is genuinely costly. It wastes time, frustrates good people, and slows down work that needs to happen.
But Robert Sutton and Huggy Rao, both professors at Stanford's d.school who previously wrote Scaling Up Excellence, push back on the assumption that all friction is equal. Their argument is precise: some friction is essential, and eliminating it is as damaging as piling it on. The leader's job is not to minimize friction. It is to fix its direction.
What You'll Learn
The distinction between "good friction" and "bad friction" and how to tell them apart
The specific costs of organizational friction and how to measure them
Why some friction should be deliberately added to slow down consequential decisions
Practical tools for running a "friction audit" in your organization
The organizational design features that reduce bad friction without eliminating the useful kind
Bad Friction: What It Costs
Sutton and Rao open by building the case against bad friction before complicating the picture. The evidence is specific. Studies of healthcare organizations have found that nurses and doctors spend up to half their working time on administrative tasks unrelated to patient care. Research on software engineers has found that unnecessary meetings and approval chains reduce coding output by 20 to 30 percent. Employee surveys across industries consistently identify pointless process as a top driver of disengagement.
The costs of bad friction are not evenly distributed. Junior employees, who lack the organizational capital to route around bureaucracy, bear a disproportionate share. The work that suffers most is the creative, collaborative, high-judgment work that is hardest to measure and easiest to displace with administrative activity.
The cumulative effect is what the authors call "addition sickness" — the tendency of organizations to respond to any problem by adding a new process, policy, or approval step. Each addition is individually defensible. The aggregate is suffocating.
Good Friction: Why You Need Some
The counterintuitive core of the book is the case for good friction. Some decisions benefit from resistance. The person who wants to launch a major product change, hire a controversial candidate, or approve a large acquisition should face enough friction to pause and think before proceeding. The friction is the control.
Sutton and Rao document several forms of good friction:
Deliberation requirements. Forcing a waiting period or a second review before major commitments. Simple to implement, demonstrably effective at catching errors.
Devil's advocate processes. Designating someone to argue against the proposed decision before it is finalized. The friction of structured disagreement produces better outcomes.
Documentation requirements. For high-stakes decisions, requiring a written rationale that others can read and critique. The friction of writing forces clarity that verbal discussion often skips.
Cooling-off periods. Slowing down decisions made in emotionally charged moments. A simple process rule that captures a large fraction of preventable mistakes.
The key distinction is between friction that stops bad decisions and friction that stops all decisions. The former is an asset. The latter is a management failure.
How to Run a Friction Audit
The book's most practical contribution is the friction audit framework. The steps are specific enough to run in an afternoon.
Identify your friction points. Survey your team on where they spend time that does not directly contribute to outcomes. Which meetings, approvals, reports, and processes feel most pointless?
Classify each friction point. Is this friction preventing bad outcomes (good friction) or just slowing things down without benefit (bad friction)?
Estimate the cost. For bad friction, calculate the time spent per week and multiply by average loaded cost per hour. The numbers are usually surprising.
Kill, simplify, or keep. Bad friction that is clearly pointless should be eliminated. Bad friction that has some benefit should be simplified. Good friction should be preserved and examined to ensure it is doing its intended job.
Track the results. Measure what happened to the outcomes you were trying to protect after removing bad friction. Did the quality hold? Most of the time, it does.
The authors are careful that friction audits should not be one-time events. Friction accumulates. Organizations need ongoing processes to surface and reduce bad friction before it calcifies into "the way we do things."
The Leader as Friction Fixer
Sutton and Rao introduce a useful identity: the leader as "friction fixer." Their research on companies with unusually low bad-friction environments consistently finds a senior leader who is personally identified with removing organizational obstacles. This person is visible, responsive, and takes the removal of bad friction personally.
The behaviors of effective friction fixers include:
Making themselves available to hear about specific friction points without defensive reactions.
Following up on complaints about friction with visible action, not just acknowledgment.
Modeling the willingness to kill their own pet processes when they are not producing value.
Celebrating teams that simplify their own operations.
The opposite is also true. Organizations with high bad friction almost always have senior leaders who are adding rather than removing — who respond to every problem with a new meeting, a new report, or a new approval chain.
Quick Start Guide
Three moves to start this week.
Run a meeting audit. List every recurring meeting your team attends. For each, write one sentence describing what decision it enables or what outcome it produces. Any meeting without a clear answer is a candidate for cancellation.
Map your approval chains. Find the five decisions that take the longest in your organization. For each, draw the approval path. The steps that never change anything are bad friction.
Add one piece of good friction. Pick a high-stakes decision your team makes regularly. Design a 30-minute pause with a structured second review before the decision is finalized.
Final Reflections
The Friction Project is unusually practical for a management book from academic authors. The research is solid, the examples are specific, and the tools are operational rather than aspirational. The core insight — that friction is not the enemy, bad friction is — sounds simple but has real operational implications that most organizations have not followed through on. For leaders who feel like their organizations are working against them, the book provides a precise diagnosis and a concrete set of tools to fix it.
Business Floss is reader-supported. When you use our links we may earn an affiliate commission that helps us keep the site running. Thank you for your support!
