Based on Lenny's Podcast data
The PhilosophyProducts Are Conversations
With the World
"Every product is a theory about how the world works and how people want to exist in it. The best products are theories that turn out to be right."
- The product IS the communication — every feature is a statement about your beliefs
- Collaboration tools are about changing human behavior, not just software
- Slack's bet: work doesn't have to be email. That was a theory about human nature.
- The best products create a new category, then define it
FrameworkStewart's Product Thinking
$27.7BSalesforce acquisition price
10+ yrsfrom Flickr to Slack to today
10Mdaily active users at acquisition
- Start with the insight, not the feature: what do you believe is true about humans?
- Build for the behavior change you want, not the feature your users ask for
- The MVP test: does it change how someone spends their time? If not, it's not an MVP.
- Iteration is overrated; insight is underrated — one great insight > 100 features
The Flickr originSlack emerged from the wreckage of a failed game. The best products are often accidental side projects of something that didn't work.
What Slack Taught10 Years of Product Lessons
- On competition: Microsoft Teams won distribution. Slack won culture. Distribution beats culture short-term.
- On adoption: The team that loves a product creates a viral loop; the team that merely uses it doesn't
- On simplicity: Every feature Slack added slowed down new user activation — and they added too many
- On scale: The product that works for 10 users often breaks at 1000 — behavior changes at scale
The Microsoft lesson
Teams won by being free in Office 365. Slack won by being beloved. They're different victories.
The channel insight
Channels weren't new. The insight was: people self-organize around topics when the friction is low enough.
PlaybookBuild Products That Last
- Write down the theory your product is based on — if you can't articulate it, you can't defend it
- Test the behavior change, not the feature: do users actually do something different?
- Protect your core insight from feature creep — Slack's mistake was adding features that diluted the theory
- Build the community before the product reaches scale — it's your retention moat
Stewart's regretAdding Slack huddles, clips, and canvas diluted the channel-first thesis. "We should have stayed simpler longer."
ContrarianProduct Development Myths
✗Build what users ask forINSTEAD →✓ Build what users' behavior reveals they need. Users ask for faster horses.
✗A/B test everythingINSTEAD →✓ A/B test optimizations. Don't A/B test your core thesis — run the experiment with conviction.
✗Growth is the metricINSTEAD →✓ Engagement depth is the metric. High growth with low engagement is borrowed time.
✗Add features to winINSTEAD →✓ Remove features to win. Slack's best release was removing things that cluttered the core.