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 Starfish Retrospective | ![]() Agile Start Stop Continue | ![]() Product Discovery Experiment Canvas |
|---|---|---|---|---|
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 improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. | 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 experiments become unreadable after the fact, it arranges hypothesis, signal, and learning goal on a single canvas. It separates problem, assumption, solution, and evidence. The result is captured as a Completed Experiment Canvas and a Success Metric. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30–60 min per interview | 45-90 min | 30-60 min | 30-60 min |
Participantsdifferent | 1 participant per interview | 4-12 | 3-12 | 1-5 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Interview Notes, Themes, Insight Summary | Starfish Board, Practice Changes, Experiments | Start Stop Continue Board, Improvement Actions | Completed Experiment Canvas, Success Metric |
Tagsno overlap | QualitativeResearchCustomerDiscovery | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementTeamReflection | ExperimentsValidationDiscoveryHypothesis |



