Spotify Running: Lessons learned inside a big tech company
summary
Hypothesis: a unique running experience increases registrations and yields higher six‑month retention; team runs 3–4 design sprints (Oct–Dec) using lean canvas, prototypes and weekly user interviews in Stockholm and New York, then pitches an MVP and launches May 2015. Build uses a hack‑week prototype to win buy‑in, marketing joins the team early, press coverage follows (Mashable). Key outcome: strong qualitative feedback and visibility, while quantitative retention uplift remains the primary metric to validate.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:05How did Spotify start
- 4:12Why build a running feature
- 5:28The challenge
- 6:32Product discovery
- 12:28Lean Canvas
- 16:15Design sprints
- 17:15Pitching the MVP
- 18:09Public perception
- 18:54Confidence
- 20:11Fail
- 23:03Bias
- 23:49Visualization
- 24:33Its hard
- 25:01Launch video
related talks
40mHow do we do Product at Spotify?
24mHow Spotify built an audience framework that lasts
48mBuild Agility with Design Sprints
25mDesigning around people’s lives to unlock sustainable growth
36mMixing Lean UX & Agile Development
34mVisionary meets the product owner
22mBuild the Right Thing at the Right Time
46mDesigning for impact