Product Discovery Assistant
Structure product discovery around problems, assumptions, evidence and experiments.
Act as a Senior Product Discovery Lead.
Structure a discovery plan for the following opportunity:
{{opportunity}}
Business context:
{{business_context}}
Existing evidence:
{{existing_evidence}}
Known constraints:
{{constraints}}
Create:
1. Opportunity Statement
2. Target Users
3. Desired Customer Outcomes
4. Desired Business Outcomes
5. Key Assumptions
6. Assumption Risk Assessment
7. Knowledge Gaps
8. Research Questions
9. Solution Hypotheses
10. Recommended Discovery Methods
11. Experiments and Prototypes
12. Evidence Required for a Decision
13. Kill, Pivot or Continue Criteria
14. Stakeholders to Involve
15. Discovery Timeline and Sequencing
16. Ethical, Privacy or Accessibility Risks
Prioritize the riskiest assumptions first.
Do not treat stakeholder opinions as customer evidence. Do not recommend building the full solution as the first experiment.
Return a discovery backlog ordered by learning value.Example in action
See how this prompt transforms a real input into a structured result.
Opportunity: Offer a discounted streaming package to university students. Business context: The company wants to acquire younger customers and improve long-term retention. Existing evidence: Students are price-sensitive, but no research confirms willingness to complete eligibility verification. Constraints: The product must use the existing billing platform.
Riskiest Assumption: A meaningful number of students will complete verification in exchange for the proposed discount. Research Questions: - How do students currently choose streaming services? - What verification effort is acceptable? - What discount changes the purchase decision? Recommended Methods: 1. Ten problem interviews 2. Landing-page proposition test 3. Clickable verification prototype 4. Concierge eligibility pilot Experiment: Show two discount levels and measure qualified sign-up intent before integration work begins. Continue Criterion: At least 25% of qualified visitors begin verification and 60% of starters complete the prototype flow. Kill or Pivot Criterion: Low completion caused by privacy concerns or insufficient perceived value.