The Friction Project
Remove what wastes time; make the right thing easy.
Essence (why this landed for me)
This book gave me a clear role to play: friction fixer. It showed how subtraction, not addition, often moves work faster. I like the tools that make good actions effortless and bad ones harder. It feels useful in teams and in daily life.
Insights (mapped to mental models)
Takeaways grouped by mental models, with a short action you can use now.
Subtraction is a strategy, not an afterthought
Make the right thing the easy thing
Name the time thieves before you fight them
Flow improves when you shrink batch size
Checklists prevent known mistakes
Stop-doing lists free more time than to-do lists
Friction can be a feature for risky actions
Clear ownership removes coordination drag
Map the journey to see hidden friction
Meetings need gates or they multiply
Tripwires catch drift early
Defaults are powerful policy
Fewer handoffs, fewer headaches
Error-proof the step that fails most
Measure friction by outcomes, not feelings
Sometimes the fix is to add a buffer
Absorption Notes (short essay)
Work like a friction fixer. List the biggest time thieves and remove one each week. Map the path from request to delivery and cut steps, handoffs, and batch size. Add a one-page checklist where errors repeat. Set gates for meetings and approvals so they do not grow by habit. Use defaults and templates to make good actions easy. Add a speed bump only where risk is high. Track cycle time and rework, not vibes. Keep the changes small but steady.
Reflection Prompts (product × design × engineering)
Questions to apply the ideas across projects. Pick one or two and use them today.
Time thieves
What wastes the most time on this path
BottlenecksList three.
Subtraction
Which step can we remove with no downside
InversionKill one.
Batch size
How can we deliver in smaller chunks
Queuing TheoryHalve it.
Ownership
Who is the single owner for the next step
Role ClarityName one.
Defaults
What default would steer the right behavior
Choice ArchitectureSet it.
Poka-yoke
Where do we see the same error and how to prevent it
Error MinimizationDesign it out.
Meeting gate
Does this meeting have a purpose, agenda, and pre-read
Constraints → CreativityCancel if not.
Tripwire
What signal should force a pause or pivot
Threshold EffectsDefine one.
Handoffs
Which handoff can we remove or merge
Transaction CostsShorten chain.
Slack
Where will a small buffer prevent a big failure
Margin of SafetyAdd it.