Before committing engineering resources — a 5-day discovery sprint can save months of building the wrong thing.
You are a senior {{role}} brought in to help {{target_user}} complete a Run a Product Discovery Sprint. # Context Original working context: - Step 1: I want to explore a new product idea or major feature. The opportunity I see: {{describe}}. My assumption about the customer problem: {{describe}}. What I don't know yet: {{list_3_key_unknowns}}. - Step 2: Design the discovery sprint: 5-day plan — Day 1: Define the challenge and map assumptions. Day 2: Customer interviews (who to talk to, 5 key questions to ask). Day 3: Analyze patterns and synthesize insights. Day 4: Sketch 3 solution concepts. Day 5: Build a lightweight prototype and test with 2 users. - Step 3: Write the customer interview guide: 8 open-ended questions that uncover the real problem without leading the witness. Include 2 warm-up questions, 4 core questions, and 2 closing questions. - Step 4: Design the prototype: What's the simplest version I can put in front of a user in Day 5? (Figma mockup, Notion page, printed wireframe, or Loom video of the concept.) What are the 3 things I'm testing? - Step 5: Create the synthesis template: How to capture insights from interviews, identify patterns, and make a go/no-go decision on the opportunity at the end of the sprint. # Goal Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use. # Constraints - Use the user's variables exactly where relevant. - Avoid generic filler and vague advice. - Be specific to the stated audience, platform, market, role, industry, or situation. - Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue. # Output Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.
{{double-curly}} with your real context.Before committing engineering resources — a 5-day discovery sprint can save months of building the wrong thing.
The discovery sprint is the most valuable week a product team can spend. It's the week you talk to customers instead of assuming you know them. Every sprint that surfaces 'we were wrong about X' is a sprint that saved 3 months of wrong-direction engineering.
Validate this business idea rigorously. Assess market size, competition, feasibility, and risk. Give an honest recommendation — do not flatter.
Conduct a structured competitor analysis. Map each competitor's strengths, weaknesses, positioning, pricing, and target customer. Identify the market gaps your business can own.
Write the complete narrative for a 10-slide pitch deck. For each slide, write the title, the key message (one sentence), and the talking points (3-5 bullets).
Recommend a pricing strategy with full rationale. Provide 3 pricing options (low/mid/premium tier) and explain what each achieves. Recommend one as optimal for the stated goal.