Complaint Storms
by Noah Weiss • Chief Product Officer at Slack
Noah Weiss is the Chief Product Officer at Slack, overseeing the product strategy and development. Previously, he was the SVP of Product at Foursquare and a Product Manager at Google, bringing over 15 years of experience in building both consumer and B2B software.
🎙️ Episode Context
Noah Weiss discusses the evolution of Slack's product strategy, sharing frameworks for working with visionary founders and revitalizing stalled growth. He details unique internal rituals like 'Complaint Storms' and 'Customer Love Sprints' that maintain product quality, and explains how Slack defined a new 'Successful Teams' metric to drive self-service revenue.
Problem It Solves
Overcoming the 'Curse of Knowledge' where product teams are power users and lose empathy for the new user experience.
Framework Overview
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.
🧠 Framework Structure
Start with an adjacent/competitor pro...
One screen, many voices: Project the ...
Log everything: Capture every confusi...
When to Use
When a product area feels stale, or when user metrics are flattening despite 'optimizations'.
Common Mistakes
Skipping the competitor review first (makes the team defensive) or trying to solve the bugs during the session instead of just logging them.
Real World Example
Slack used this to revamp their self-service onboarding by realizing how confusing the 'Day 1' experience was for non-tech teams.
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?
— Noah Weiss