View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Risk Storming |  Agile Starfish Retrospective |  Product Discovery Learning Card |  Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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. | The Learning Card connects traceable test results to a reasoned next action while keeping the limits of the insight visible. | 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 | Low | Low | Low | Medium |
Timedifferent | 60-90 min | 45-90 min | 25-40 min | 1-5 Tage |
Participantsdifferent | 4-12 | 4-12 | 1-5 | Nutzertraffic |
Formatdifferent | Workshop | Workshop | Workshop + async | Async |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Starfish Board, Practice Changes, Experiments | Learning Card with evidence and next action | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | RiskArchitectureWorkshopValidation | RetrospectiveImprovementExperimentsTeam | ExperimentsValidationDiscoveryLearning | ValidationExperimentsDemandDiscovery |