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 |  Product Discovery Assumption Mapping |  Agile Start Stop Continue |  Agile 4Ls Retrospective |
|---|---|---|---|---|
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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | 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 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 60-90 min | 45-60 min | 30-60 min | 45–75 min |
Participantsdifferent | 4-12 | 2-8 | 3-12 | Team members involved |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Assumption map, Test backlog, Risk ranking | Start Stop Continue Board, Improvement Actions | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | RiskArchitectureWorkshopValidation | AssumptionsRiskExperimentsValidation | RetrospectiveImprovementTeamReflection | RetrospectiveLearningReflectionTeam |