How to run a product discovery sprint

How can a team run a short product discovery sprint before committing to build?

Spend one to three weeks testing the riskiest assumptions behind an idea before writing production code. Talk to a small number of real target users about their current workaround, test a rough prototype or a manual version of the service, and check whether people will commit time, data or money. End with a written decision: build a first release, change the idea or stop.

What this means in practice

Write down the assumptions that would kill the idea if wrong.
Interview a handful of real target users about how they solve the problem today.
Test a rough prototype or a manual version of the service.
Look for commitment, such as time, data or a paid pilot, not just praise.
End with a written decision and the scope of the first release.

How Lid Vizion approaches it

We start with the business decision and operating context, define ownership and measurable milestones, then use configuration, integrations, automation, or custom software only where each earns its place.

--- title: "How to run a product discovery sprint" description: "Spend one to three weeks testing the riskiest assumptions behind an idea before writing production code. Talk to a small number of real target users about their current workaround, test a rough prototype or a manual version of the service, and check whether people will commit time, data or money. End with a written decision: build a first release, change the idea or stop." url: https://lidvizion.ai/answers/how-to-run-a-product-discovery-sprint/ site: Lid Vizion index: https://lidvizion.ai/llms.txt --- [Direct answers](https://lidvizion.ai/answers/) # How can a team run a short product discovery sprint before committing to build? Spend one to three weeks testing the riskiest assumptions behind an idea before writing production code. Talk to a small number of real target users about their current workaround, test a rough prototype or a manual version of the service, and check whether people will commit time, data or money. End with a written decision: build a first release, change the idea or stop. ## What this means in practice - Write down the assumptions that would kill the idea if wrong. - Interview a handful of real target users about how they solve the problem today. - Test a rough prototype or a manual version of the service. - Look for commitment, such as time, data or a paid pilot, not just praise. - End with a written decision and the scope of the first release. ## How Lid Vizion approaches it We start with the business decision and operating context, define ownership and measurable milestones, then use configuration, integrations, automation, or custom software only where each earns its place. ## More on Product & milestone delivery - [How can a product team produce release notes from shipped work without extra effort?](https://lidvizion.ai/answers/how-to-write-release-notes-from-shipped-work/) - [Which product metrics should a small product team actually track?](https://lidvizion.ai/answers/which-product-metrics-should-you-track/) - [How can a company reduce customers leaving in their first few weeks?](https://lidvizion.ai/answers/how-to-reduce-early-customer-churn/) [Compare services](https://lidvizion.ai/services/) · [Use a planning tool](https://lidvizion.ai/tools/) · [Explore workflow use cases](https://lidvizion.ai/use-cases/) · [More direct answers](https://lidvizion.ai/answers/) Talk it through ## Have a version of this question inside your company? Bring the decision, the constraints, and what a good outcome looks like. [Talk through the decision](https://lidvizion.ai/contact/?need=milestone-delivery&from=%2Fanswers%2Fhow-to-run-a-product-discovery-sprint%2F#write) · [Book a call](https://calendar.app.google/bB26LdA9e2gmGFp69)

What this means in practice

How Lid Vizion approaches it

More on Product & milestone delivery

Have a version of thisquestion inside your company?

Have a version of this
question inside your company?