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 Problem Interview |  Agile Start Stop Continue |  Agile Starfish Retrospective |  Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | 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 team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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 demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 30-60 min je Interview | 30-60 min | 45-90 min | 1-5 Tage |
Participantsdifferent | 5-12 Interviews | 3-12 | 4-12 | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop | Workshop | Async |
Outputdifferent | Problem Evidence, Risk Notes, Customer Segments | Start Stop Continue Board, Improvement Actions | Starfish Board, Practice Changes, Experiments | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | DiscoveryInterviewsValidation | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementExperimentsTeam | ValidationExperimentsDemandDiscovery |