View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research User Interviews |  Agile Start Stop Continue |  Agile Sailboat Retrospective |  Product Discovery Opportunity Interview |
|---|---|---|---|---|
Purposedifferent | When teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible. | 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 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 30–60 min per interview | 30-60 min | 45-90 min | 30-60 min je Interview |
Participantsdifferent | 1 participant per interview | 3-12 | 4-12 | 5-12 Interviews |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Interview Notes, Themes, Insight Summary | Start Stop Continue Board, Improvement Actions | Sailboat Board, Risks, Improvement Actions | Interview Notes, Opportunity Themes, Customer Quotes |
Tagsno overlap | QualitativeResearchCustomerDiscovery | RetrospectiveImprovementTeamReflection | RetrospectiveTeamImprovement | DiscoveryInterviewsOpportunityCustomer |