Slack's Stewart Butterfield: The Big Pivot
Executive Summary
Butterfield recounts two failed games that produced Flickr and Slack. The interview covers choosing a single direction, supporting employees when a project closes, preserving money for the next attempt and turning an internal communication tool into a product. Notes cover selected business passages from the complete public captions, reaching the closing credits, and checked against the official show transcript. April 28, 2023 is this YouTube upload date; the official show page dates the original episode November 15, 2017. Roles, valuation and company figures refer to that earlier conversation, not current Slack. Illness, personal distress and violent business metaphors are not summarized.
Key Takeaways
Make the hard choice
Game Neverending and Flickr could not both remain the focus. A divided team needed a decision and a realistic account of what the company could fund.
Build community deliberately
Flickr’s early users were greeted personally by Caterina Fake and George Oates. Butterfield credits the positive community culture with helping the product succeed.
More resources do not guarantee demand
Glitch had funding, experience and better technology, but most new users left quickly. A passionate minority did not make the product commercially viable.
Close before the last dollar
Stopping Glitch while money remained gave the team room to explore instead of making one final desperate bet. The internal chat system emerged as a usable next direction.
Look after people during closure
The team created a hiring page, coached resumes and wrote references. Customers could seek refunds or donate balances, preserving goodwill that helped when former employees later returned.
Solve your own aggravating problem
Slack’s searchable message archive grew from practical needs inside the game team. Years of real use produced a clearer product vision than hypothetical feature speculation.
Sell the group change
Adoption required entire teams to switch together, making early sales harder than expected. Once teams changed, that collective habit became a retention advantage.
The Conversation Breakdown
Make the hard choice
⏱ Untimed topicGame Neverending and Flickr could not both remain the focus. A divided team needed a decision and a realistic account of what the company could fund.
Build community deliberately
⏱ Untimed topicFlickr’s early users were greeted personally by Caterina Fake and George Oates. Butterfield credits the positive community culture with helping the product succeed.
More resources do not guarantee demand
⏱ Untimed topicGlitch had funding, experience and better technology, but most new users left quickly. A passionate minority did not make the product commercially viable.
Close before the last dollar
⏱ Untimed topicStopping Glitch while money remained gave the team room to explore instead of making one final desperate bet. The internal chat system emerged as a usable next direction.
Look after people during closure
⏱ Untimed topicThe team created a hiring page, coached resumes and wrote references. Customers could seek refunds or donate balances, preserving goodwill that helped when former employees later returned.
Solve your own aggravating problem
⏱ Untimed topicSlack’s searchable message archive grew from practical needs inside the game team. Years of real use produced a clearer product vision than hypothetical feature speculation.
Sell the group change
⏱ Untimed topicAdoption required entire teams to switch together, making early sales harder than expected. Once teams changed, that collective habit became a retention advantage.
Core Frameworks & Ideas
Pivot toward and away
A transition needs a clear new direction and an explicit plan for winding down the old product. The Flickr and Slack stories include decisions about the team, customers and remaining cash.
Preserve options with runway
Butterfield says stopping Glitch before the last dollar left room to investigate alternatives. This is his account of preserving choices, not a rule that every struggling product should close.
Team-level adoption
Slack needed whole groups to change their communication habits together. Butterfield describes that as a barrier to initial adoption and a source of retention after a team switched.
Actionable Next Steps
- ✓Before a pivot, list how staff and customers will be supported through the change.
- ✓Look for tools you already use internally that solve a repeated problem.
- ✓When adoption requires a whole team, test the change with a complete small group rather than one isolated user.
Notable Quotes
“It wasn't coming from a grand vision of what photos could be.”
“We made a website called Hire a Genius”
“The good thing about shutting it down early was that we had the ability to just not do anything for a couple months.”
The One Thing to Remember
A pivot needs both a clear new product and an honest, humane exit from the old one.