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

Stewart Butterfield's starting point is deliberately uncomfortable: when Slack launched in 2014, he told MIT Technology Review that the product was terrible and that the team should be embarrassed to offer it. He treats that judgment not as self-flagellation, but as a product discipline. A team should be able to see nearly limitless opportunities to improve, while the long-run measure of success remains the value actually created for customers rather than the effort spent demonstrating it.

His utility-curve framework turns product investment into a question of thresholds. Effort or cost sits on one axis and value or convenience on the other: early investment may produce almost no value, then a threshold can create a steep gain, followed by diminishing returns. A hammer handle that breaks is useless until it reaches a basic quality threshold; an app with a database but no useful experience has created no customer value. The framework prevents teams from treating a feature as simply present or absent and asks whether it needs more investment or has already passed its useful point.

Butterfield challenges the common product maxim that every form of friction should be removed. The harder problem is comprehension. When software forces a user to make a decision without explaining what it means, the user may feel stupid and associate that emotional cost with the product. Reducing clicks can make an interface worse if it exposes every option at once; a simpler product may require more taps while making each decision obvious.

The framework is a way to allocate product resources: first help people understand what a feature or product is for, then help it become indispensable. Until users reach the equivalent of 'I get it' and 'I can't live without it,' additional features do not solve the central problem. The conversation treats this as a lens for both a single Slack capability and Slack's overall onboarding.

Butterfield's advice on pivoting is less about a formula than about the emotional conditions for judgment. A founder must ask whether the available possibilities have really been exhausted, then create enough distance to make an intellectual decision rather than an emotional one. He emphasizes cold rationality because abandoning a direction can feel humiliating, and humiliation is a poor basis for deciding what to build next.

The interview's opening places these ideas in the context of Butterfield's career at Flickr and Slack, but the claims remain principles rather than a universal pivot playbook. The useful common thread is a willingness to examine the product without protecting the founder's ego, identify where value actually appears on the curve, and invest only after users can understand and depend on the result.