By Marty Cagan · svpg.com · LinkedIn
Marty Cagan introduces the discovery sprint, a one-week time-boxed effort to tackle a substantial problem or risk in a product's definition and validate a potential solution with real users. He explains that the approach fits Dual-Track Agile and can help teams get value from the MVP concept. He describes how the Google Ventures team helped startups run these sprints side by side, and recommends the book Sprint by Jake Knapp, John Zeratsky and Braden Kowitz as a structured, step-by-step guide. The piece matters because it gives teams new to discovery a concrete, repeatable starting point and suggests when to reach for it.
01Key takeaways
- Time-box discovery to one week and aim it at one substantial problem or risk.
- Always close the sprint by validating a potential solution with real users or customers.
- Use a sprint to learn discovery by doing it with structure, especially when the team lacks experience.
- Reach for a sprint when the work is critical or difficult, or when progress has stalled.
- Treat the sprint as a way to get value from the MVP concept, not just a design exercise.
02Key sections
- What a discovery sprint is
- A discovery sprint is a one-week time-box focused on a significant problem or risk, ending with validation against real customers. Cagan prefers the broader term over 'design sprint' because the work goes well beyond design.
- Origins with the Google Ventures team
- GV's team spent about a week with startups in their portfolio, working alongside them to show how product discovery is done in practice. Other discovery coaches use the same basic approach.
- Structure of the week
- The week moves from mapping the problem and choosing a target customer, to exploring multiple solution ideas, narrowing and refining them, building a realistic prototype, and testing it with users.
- The book Sprint
- Cagan found the book Sprint one of the best new product books in a long time, offering a proven step-by-step recipe with many examples. Its techniques will be familiar to readers of discovery literature.
- When to use a sprint
- Cagan recommends a sprint when a team is learning discovery, faces something big or difficult, or is moving too slowly.
03From the post
“A partnership dedicated to teaching best practices to product teams and product leaders”
04Frameworks mentioned
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.