Reference table
A research rhythm for product sprints

A simple research cadence product managers can fit around a sprint cycle: a handful of interviews before each sprint to check direction, a round with new users two weeks after a launch, and a larger study every quarter to reset assumptions. Use it to make customer contact a habit rather than a one-off project. With Koji, each round runs as AI-moderated interviews that people complete in their own time, so setup and reading the report are the only PM time it takes.
Where this appears
What's in this reference table
| When | Interviews | What it's for |
|---|---|---|
| Before a sprint | 5 to 8 | Check the direction before the team commits to building |
| 2 weeks after launch | 10 to 15 | See whether new users understand the feature and use it as designed |
| Every quarter | 20 to 30 | Reset your core assumptions about pains, behaviours and alternatives |
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/product-manager-research-cadence-by-sprint"><img src="https://www.koji.so/visuals/product-manager-research-cadence-by-sprint/product-manager-research-cadence-by-sprint.png" alt="Table of a research cadence for product teams: 5 to 8 interviews before a sprint, 10 to 15 two weeks after launch, 20 to 30 every quarter." width="1200" height="630" /></a>
<p>Source: <a href="https://www.koji.so/visuals/product-manager-research-cadence-by-sprint">A research rhythm for product sprints</a>, Koji</p>




