Customer Love Sprints
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
Balancing roadmap pressure for 'big features' with the need to polish the product and fix minor annoyances that degrade trust.
Framework Overview
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.
🧠 Framework Structure
Quarterly Cadence: Schedule these reg...
Cross-functional: Engineers, PMs, and...
Burn-down List: Work from a backlog o...
Total Release: The goal is to ship ev...
When to Use
When the product feels 'heavy' or buggy, or when customer sentiment is dipping due to lack of polish.
Common Mistakes
Using this time to start new big features or treating it as a throwaway hackathon where code doesn't ship.
Real World Example
Slack uses these sprints to fix minor animation glitches, text inconsistencies, or small interaction delays that don't justify a full PRD.
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.
— Noah Weiss