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 Experiment Canvas |  Product Discovery Hypothesis Prioritization Canvas |
|---|---|---|---|---|
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. | 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. | When many hypotheses compete for attention, it brings order to their learning sequence and importance. It separates problem, assumption, solution, and evidence. The result is captured as a prioritization canvas and a hypothesis backlog. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 60-90 min | 45-90 min | 30-60 min | 60-90 min |
Participantsdifferent | 4-12 | 4-12 | 1-5 | 3-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Starfish Board, Practice Changes, Experiments | Completed Experiment Canvas, Success Metric | Prioritization Canvas, Hypothesis Backlog |
Tagsno overlap | RiskArchitectureWorkshopValidation | RetrospectiveImprovementExperimentsTeam | ExperimentsValidationDiscoveryHypothesis | ExperimentsPrioritizationDiscoveryHypothesis |