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 4Ls Retrospective |  Agile Starfish Retrospective |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
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 a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. | 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 60-90 min | 45–75 min | 45-90 min | 45-60 min |
Participantsdifferent | 4-12 | Team members involved | 4-12 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | 4Ls Board, Learning Themes, Improvement Actions | Starfish Board, Practice Changes, Experiments | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | RiskArchitectureWorkshopValidation | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementExperimentsTeam | AssumptionsRiskExperimentsValidation |