💡

InsightHunt

Hunt the Insights

N

Noah Weiss

Episode #230

Chief Product Officer

Slack

🔍User Research👥Team & Culture📈Growth & MetricsExecution

📝Full Transcript

17,498 words
Noah Weiss (00:00:00): We have this mental metaphor that we talk a lot about, getting to the next hill. The actual wording is "Take bigger boulder bets." I think teams can often get lost crawling up that hill, not realizing that there's a huge, incredibly beautiful range behind it where we've over time freighted new teams from scratch that incubated in a new area before the areas mature. Noah Weiss (00:00:19): We did that with a lot of these native audiovisual products like huddles and clips really in the pandemic because our customers were demanding it from us. I think in the AI space, we're trying to hear from customers, what do you wish Slack could do if it had these new superpowers? Let's incubate a couple teams or prototype, give them space to run and pilot and then get something to launch that's amazing. Blows people away. That's the formula that we've seen. Lenny (00:00:45): Welcome to Lenny's podcast where I interview world-class product leaders and growth experts to learn from their hard one experiences building and growing today's most successful products. Today my guest is Noah Weiss. Noah is chief product officer at Slack where he spent the last seven years. Prior to that he was head of product at Foursquare, which is near and dear to my heart as you'll hear at the top of this episode. Prior to that, he was a PM at Google and at Fog Creek Software. Lenny (00:01:10): In our conversation we cover the 10 traits of great product managers, how to work effectively with strongly opinionated and product-minded founders, what Noah has learned about working effectively with AI in your product over his last 15 years at Google and Foursquare and now Slack. We talk about a process called Complaint Storms that helps Slack build better product. Plus, what he is learned from Slack's self-service business plateauing back in 2019 and how they turned it around and what they took away from that experience. Lenny (00:01:38): Also, how he thinks about competition with Mic...

💡 Key Takeaways

  • 1Product intuition requires 'tasting the soup'—founders and leaders must use the product in code, not just look at static mocks.
  • 2Optimization for learning must sometimes precede optimization for impact when growth plateaus.
  • 3Writing is the only scalable way to have influence in a large product organization.
  • 4Fewer clicks are not always better; clarity and reduced stress ('Don't Make Me Think') trumps click-counting.
  • 5To reignite growth, Slack shifted focus from individual active users to 'Successful Teams' (5+ people communicating).
  • 6Great PMs act as 'shock absorbers' for the team, maintaining an aura of 'I got this' execution.

📚Methodologies (4)

Complaint Storms

by Noah Weiss

🔍 User Research

A synchronous session where the team walks through a specific user journey (often onboarding) to identify every friction point. Uniquely, they start by critiquing a competitor's product first to warm up the critical muscle.

Core Principles

  • 1.Start with an adjacent/competitor product: This removes defensiveness and sets a high bar for critique.
  • 2.One screen, many voices: Project the flow on one screen while everyone shouts out issues.
  • 3.Log everything: Capture every confusion, pain point, and friction moment—no matter how small.

"If you didn't care about the software, you don't work on it, what would actually confuse you? What would stop you in your tracks?"

#complaint#storms#research
View Deep Dive →
👥 Team & Culture

A framework for when to involve product-minded founders. High involvement at the start for strategy, low involvement during execution to allow creativity, and high involvement at the end for polish.

Core Principles

  • 1.Phase 1 (Start): Align on principles, strategy, goals, and anti-goals. Define the 'what' and 'why'.
  • 2.Phase 2 (Middle): Give the team space to run, explore, and prototype without constant oversight.
  • 3.Phase 3 (End): Bring the founder back to 'taste the soup' (review working code) for final polish and craft.

"Get the founder CEO really involved early on... then give space... and at the very end you want them to really be bought in... literally taste the soup."

#founder#engagement#u-curve
View Deep Dive →
📈 Growth & Metrics

Instead of focusing on generic DAU or individual sign-ups, Slack identified a specific threshold of team behavior that predicted long-term retention and upgrade potential.

Core Principles

  • 1.Shift from Individual to Team: For collaboration tools, individual metrics are noise. Team density matters.
  • 2.Find the Magic Threshold: Slack found that a team of 5+ people communicating weekly was the tipping point.
  • 3.Optimize for Learning first: When growth plateaus, pause 'optimization' work and spend a quarter strictly testing hypotheses to find new levers.

"If you could get five people using Slack the majority of the work week to just communicate at all... they were going to be 400% more likely to upgrade."

#'successful#teams'#activation
View Deep Dive →
Execution

A dedicated 2-week sprint where the team focuses exclusively on low-effort, high-delight improvements. These are small UI/UX fixes that customers love but never make it onto a strategic roadmap.

Core Principles

  • 1.Quarterly Cadence: Schedule these regularly (e.g., once a quarter) so debt doesn't accumulate.
  • 2.Cross-functional: Engineers, PMs, and Designers work together specifically on 'delight'.
  • 3.Burn-down List: Work from a backlog of known annoyances or 'paper cuts' derived from support tickets or Twitter.
  • +1 more...

"Make it this really fun total change of pace... to do all these small delightful things that customers are going to love at the end."

#customer#sprints#execution
View Deep Dive →