Friction vs. Comprehension Matrix
by Stewart Butterfield • Co-founder & Former CEO at Slack / Flickr
Stewart Butterfield is a serial entrepreneur and product legend who founded Flickr and Slack, leading the latter to a massive acquisition by Salesforce. Known for his design-centric approach and philosophy on organizational behavior.
🎙️ Episode Context
Stewart Butterfield shares deep product wisdom, challenging conventional wisdom on friction and efficiency. He discusses the importance of utility curves, why "work-like activities" kill productivity, and how to apply empathy and taste to build software that doesn't make users feel stupid.
Problem It Solves
Teams often blindly optimize for 'zero friction' (fewer clicks), resulting in confusing products that users don't understand how to use.
Framework Overview
Instead of viewing friction as the enemy, view 'thinking' as the enemy. Sometimes adding steps (friction) increases comprehension, which is more valuable than speed. If a user has low intent and low comprehension, you must guide them, even if it takes more clicks.
🧠 Framework Structure
Minimize cognitive load (ATP/Glucose ...
Prioritize 'Comprehension' over 'Spee...
Avoid making the user feel stupid by ...
When to Use
Designing onboarding flows, complex settings (like Do Not Disturb), or introducing new mental models.
Common Mistakes
Removing necessary explanatory steps to hit a 'number of clicks' KPI.
Real World Example
Slack's 'Do Not Disturb' rollout: Instead of a simple toggle, they created a complex hierarchy of defaults and overrides to ensure admins and users understood the impact, preventing organizational conflict.
If your software stops me and asks me to make a decision and I don't really understand it, you make me feel stupid.
— Stewart Butterfield