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 |  Agile Start Stop Continue |  Agile Sailboat Retrospective |  Product Discovery Opportunity Solution Tree |
|---|---|---|---|---|
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 a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. | When discovery keeps swinging between goals, ideas, and learning loops, it creates clear steering logic. It connects the desired outcome, opportunities, and experiments into a legible structure. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 30-60 min je Interview | 30-60 min | 45-90 min | 1-2 h Setup, laufend |
Participantsdifferent | 5-12 Interviews | 3-12 | 4-12 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Start Stop Continue Board, Improvement Actions | Sailboat Board, Risks, Improvement Actions | Opportunity Solution Tree, Experiment Backlog, Learning Log |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | RetrospectiveImprovementTeamReflection | RetrospectiveTeamImprovement | DiscoveryOutcomesExperimentsOpportunity |