How to Run a Product Discovery Sprint in 2 Weeks
A product discovery sprint is a short burst of research that answers one big question before you spend months building: are we solving a real problem, in a way people will pay for? In this guide, we share the two-week method we use with clients. As a result, you can run it yourself with a small team.
What you get from a product discovery sprint
By the end of the two weeks, you will have:
- A clear problem statement the whole team agrees on
- Evidence from real customer conversations
- Up to two personas based on what you heard
- A prioritised roadmap for the next two quarters
Before you start your product discovery sprint
A little preparation makes the sprint far more useful. First, pick one product or problem area, because a sprint that covers everything learns nothing. Next, name one decision-maker who will attend the final readout. Then book your interviews early. Finally, agree what success means, for example “we know which of three ideas to build first”.
Week 1 of the product discovery sprint: understand the problem
Day 1: Align
To start, run a 90-minute kickoff. Next, write down what the team believes about customers and their problems. Then mark each belief as a fact or an assumption. In the end, the assumptions become your research questions.
Days 2 to 5: Talk to customers
To begin with, hold five or six interviews of 30 to 45 minutes each. Also, ask about past behaviour, not opinions about the future. For example, these questions work well:
- “Tell me about the last time you dealt with this problem.”
- “What did you try, and what was frustrating about it?”
- “How much time or money does this cost you today?”
- “If you could change one thing, what would it be?”
However, avoid pitching your idea. Once you describe your solution, people tend to be polite instead of honest.
Alongside: a quick competitor scan
At the same time, review up to five competitors or alternatives. Include spreadsheets and doing nothing, since those are real options too. Then note what each does well, where users complain, and how they charge.
Week 2 of the product discovery sprint: decide what to build
Days 6 and 7: Synthesise
First, put every interview note on a shared board. After that, group similar comments and name each group in the customer’s own words. Above all, look for problems that are painful, frequent or expensive.
Day 8: Frame the problem
Next, write a one-sentence problem statement: “[Customer] struggles to [job] because [reason], which costs them [impact].” Then draft up to two personas from the patterns you found.
Day 9: Prioritise
List the opportunities you found and score each one. A simple table is enough:
| Opportunity | Value (1–5) | Effort (1–5) | Confidence (1–5) |
|---|---|---|---|
| Example: automate weekly reports | 5 | 2 | 4 |
| Example: mobile app | 3 | 5 | 2 |
In general, favour high value, high confidence and low effort. As a result, these become the first items on your roadmap.
Day 10: Readout
Finally, present the problem statement, the evidence, the personas and the roadmap to your decision-maker. Agree what you will build first, and also what you will not build.
Common product discovery sprint mistakes
- Interviewing friends or investors instead of real users
- Asking leading questions such as “Would you use this?”
- Skipping synthesis and jumping straight to features
- Ending the sprint without a clear decision
If you want to go deeper on interview methods, this overview of user research is a good place to start. Alternatively, see how we run a product discovery sprint for clients.
Want us to run it with you?
Our Product Discovery Sprint covers up to 6 interviews, a competitor review, a problem statement, personas and a 2-quarter roadmap, starting from $1,500.
