View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Opportunity Interview |  Product Discovery Problem Interview |  Agile 4Ls Retrospective |  Agile Start Stop Continue |
|---|---|---|---|---|
Purposedifferent | When opportunities are still hidden behind signals of need, it structures conversations around needs and obstacles. It looks for patterns that lead to new product opportunities. | When the picture of the problem still needs to become solid, it asks about real situations and consequences. It separates genuine suffering from mere interest in a solution. | When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. | When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 30-60 min je Interview | 30-60 min je Interview | 45–75 min | 30-60 min |
Participantsdifferent | 5-12 Interviews | 5-12 Interviews | Team members involved | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Problem Evidence, Risk Notes, Customer Segments | 4Ls Board, Learning Themes, Improvement Actions | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | DiscoveryInterviewsValidation | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementTeamReflection |