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 Sailboat Retrospective | ![]() Agile Start Stop Continue |
|---|---|---|---|
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 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 a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitysame | Low | Low | Low |
Timedifferent | 30–60 min per interview | 45-90 min | 30-60 min |
Participantsdifferent | 1 participant per interview | 4-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Interview Notes, Themes, Insight Summary | Sailboat Board, Risks, Improvement Actions | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | QualitativeResearchCustomerDiscovery | RetrospectiveTeamImprovement | RetrospectiveImprovementTeamReflection |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






