All frameworks and cheat sheets

Reference table

Four customer discovery cadences for product teams

Table of four customer discovery cadences, pre-sprint, always-on, win/loss and feature validation, with what each is for and how many interviews.
Discovery works best as a steady stream, not a burst before each launch

Four ways to keep customer discovery running alongside product work: pre-sprint problem validation with 5 to 8 interviews, an always-on study triggered by events like cancellation, win/loss interviews aggregated across 20 to 30 responses, and pre-launch feature validation with 8 to 10 existing customers. Use it to plan a research rhythm that fits your sprint cycle.

Where this appears

What's in this reference table

CadenceWhat it is forSize
Pre-sprint discoveryConfirm a problem is real and how severe it is before committing to a feature5 to 8 interviews
Always-on discoveryA standing study triggered after NPS, onboarding or cancellationRuns continuously
Win/loss interviewsInvite customers after a deal closes or churns, then look for patterns20 to 30 responses
Feature validationCheck framing, naming and value proposition before you ship8 to 10 interviews

Use this image

Free to use in your docs, decks and posts under CC BY 4.0, as long as you credit Koji with a link to this page. To embed it, paste this into your page:

html
<a href="https://www.koji.so/visuals/customer-discovery-cadences-product-teams"><img src="https://www.koji.so/visuals/customer-discovery-cadences-product-teams/customer-discovery-cadences-product-teams.png" alt="Table of four customer discovery cadences, pre-sprint, always-on, win/loss and feature validation, with what each is for and how many interviews." width="1200" height="744" /></a>
<p>Source: <a href="https://www.koji.so/visuals/customer-discovery-cadences-product-teams">Four customer discovery cadences for product teams</a>, Koji</p>