Slack founder: Mental models for building products people love ft. Stewart Butterfield

Nov 20, 2025 1h 30m 23 insights Episode Page ↗
Stuart Butterfield, founder of Flickr and Slack, shares product and leadership wisdom, discussing utility curves, the owner's delusion, hyper-realistic work-like activities, the importance of not making users think, and the cold rationality required for successful pivots. He emphasizes creating customer value and generosity.
Actionable Insights

1. Prioritize Customer Value Creation

Measure success by the actual value created for customers, not just by demonstrating effort, as there’s no substitute for real value creation and it’s an ethical way to run a business.

2. Embrace “Perpetual Desire to Improve”

Cultivate a mindset of perpetual dissatisfaction and a desire to improve, viewing your current product as a “piece of shit” to drive continuous enhancement and innovation.

3. Minimize User Cognitive Load

Shift focus from merely reducing friction or clicks to preventing users from having to think and making decisions, as this reduces metabolic cost and avoids making users feel stupid.

4. Apply “Don’t Make Me Think”

Adopt “Don’t Make Me Think” as a core design mantra to minimize cognitive load, prevent decision fatigue, and ensure users can intuitively understand and use your software.

5. Leverage Empathy for Product Advantage

Create a critical advantage by being considerate, courteous, and empathetic to users’ experiences, as others’ failure to do so presents an opportunity for your product to delight.

6. Market the Outcome, Not Features

Don’t just build a great product; also create the market by communicating the problem it solves and the outcomes it achieves for customers, rather than just listing features, especially for novel solutions.

7. Make Rational Pivot Decisions

When considering a pivot, ensure you’ve exhausted all non-ridiculous possibilities and make a coldly rational, intellectual decision, separating it from the emotional pain and humiliation of admitting a prior idea didn’t work.

8. Invest Past Utility Threshold

Understand utility curves to determine if a feature has received enough investment to cross the “magic threshold” where it provides enormous value, or if it’s stuck in the low-value phase, to optimize resource allocation.

9. Anticipate Rising User Standards

Recognize that user standards continuously increase as they become familiar with software and as competitors improve, requiring ongoing investment and improvement to maintain quality and delight.

10. Avoid The Owner’s Delusion

Be conscious of “The Owner’s Delusion,” where product creators overestimate user intent and familiarity, leading to designs that are unclear or frustrating for new users with minimal motivation and many distractions.

11. Test as a “Regular Person”

When evaluating your product, consciously adopt the mindset of a “regular human being” with distractions and low intent, to identify areas of confusion or difficulty and ensure clarity.

12. Eliminate Hyper-Realistic Work

Actively identify and eliminate “hyper-realistic work-like activities” – tasks that superficially resemble productive work (e.g., endless meetings about presentations) but add no real value.

13. Provide Clear, Valuable Work

Leaders must ensure a sufficient supply of “known valuable work” for their teams by creating clarity, alignment, and explicit priorities, rather than blaming employees for engaging in non-valuable activities.

14. Counteract Parkinson’s Law in Hiring

Be aware that work expands to fill the time available, and most employees will seek to hire more people to report to them, which can lead to organizational bloat if not actively managed.

15. Demonstrate Generosity for Cooperation

Practice generosity with employees and customers as a strategic way to signal cooperation in an iterated game, fostering mutual benefit and attracting ethical talent and customers.

For mobile apps, ask users for their email, then send a magic link that automatically opens the app and authenticates them, to avoid the terrible experience of typing complex passwords on a phone.

17. Guide Notification Defaults

For new users, set a default that aligns with initial expectations (e.g., all notifications), then proactively offer to switch to recommended, less noisy settings after a certain usage threshold to prevent overwhelm.

18. Add Friction to Prevent Misuse

Implement friction (e.g., a warning pop-up) for features that can be easily abused or cause annoyance, to shape user behavior and educate them on the impact of their actions.

19. Design Menus for Trivial Choices

For menus, present only the 2-3 most common actions upfront, grouping others behind an “other” option, prioritizing trivially easy choices over fewer clicks that require difficult comparisons.

20. Implement Staged Feature Rollout

For critical features with potential for conflict (like Do Not Disturb), pre-announce to administrators, set sensible organizational defaults, and allow both administrators and end-users to override settings.

21. Offer Proactive Customer Credits

Proactively offer generous, automatic credits for service disruptions or issues, even without customer input, to demonstrate commitment to customer value, though be mindful of scaling impacts for public companies.

22. Value Direct Improvement Feedback

Actively seek direct criticism and feedback, viewing every mistake or area for improvement as a valuable “gem” that can be collected and used to make your product or skills better.

23. Acknowledge Systemic Complexity

Understand that getting anything done is inherently difficult, requiring not just resources but also navigating complex social, political, and organizational dynamics, rather than blaming individual “bad actors.”