Discovery Sprint Framework

A structured approach to rapid product discovery and validation

Understanding Discovery Sprints

Discovery sprints are focused periods of intense product discovery work, typically lasting one week, where teams rapidly explore and validate product opportunities or solutions. Based on the Google Ventures Sprint methodology but adapted for product discovery.

Sprint Structure

Day 1: Map & Target

  • Morning - Define sprint goal and success metrics
  • Afternoon - Map the problem space
  • Deliverables: Sprint goal, journey map, key questions

Day 2: Sketch & Ideate

  • Morning - Research and inspiration
  • Afternoon - Individual sketching and ideation
  • Deliverables: Solution sketches, alternative approaches

Day 3: Decide & Storyboard

  • Morning - Solution review and decision
  • Afternoon - Detailed storyboard creation
  • Deliverables: Selected solution, detailed storyboard

Day 4: Prototype

  • Morning - Start prototype creation
  • Afternoon - Finish prototype and test plan
  • Deliverables: Working prototype, test script

Day 5: Test & Learn

  • Morning - Customer interviews and testing
  • Afternoon - Synthesize findings and plan next steps
  • Deliverables: Test results, insights, recommendations

Sprint Team Roles

  • Facilitator - Manages the process and keeps team on track
  • Decider - Makes final decisions when team can't align
  • Product Lead - Provides product context and vision
  • Designer - Creates prototypes and visual assets
  • Tech Lead - Provides technical feasibility input
  • Customer Expert - Provides customer context and insights

Sprint Preparation

  1. Pre-Sprint Planning
    • Define sprint challenge
    • Select team members
    • Gather existing research
    • Book customer interviews
  2. Logistics
    • Book dedicated space
    • Prepare materials
    • Set up tools
    • Brief participants

Discovery Sprint Brief Template

Sprint Overview
--------------
Sprint Goal:
Key Questions:
Success Metrics:
Sprint Dates:

Team
----
Facilitator:
Decider:
Core Team:
Extended Team:

Challenge
---------
Problem Statement:
Target Users:
Current State:
Desired Outcome:

Resources
---------
Research Materials:
Tools Needed:
Space Requirements:

Schedule
--------
Pre-Sprint Tasks:
Daily Agenda:
Post-Sprint Follow-up:

Success Criteria
---------------
Must Learn:
Nice to Learn:
Out of Scope:

Sprint Success Factors

  • Clear Focus - Well-defined sprint goal and questions
  • Right Team - Dedicated, cross-functional participants
  • Good Facilitation - Keeping energy and progress high
  • Real Customers - Access to target users for testing
  • Decision Making - Clear process for making choices

Common Pitfalls

  • Trying to solve too many problems
  • Not having decision maker involvement
  • Skipping prototype testing
  • Poor time management
  • Lack of follow-through on insights