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 |  Business Strategy GAP Analysis |  Product Strategy DIBB |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|---|
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. | GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing. | DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 60-90 min | 1-3 h | 1-2 h | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 4-12 | 2-8 | 2-8 | Designers, developers as users, and facilitation |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Gap Matrix, Action Plan, Risk Notes | DIBB document, Belief list, Bet list, Learning report | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | RiskArchitectureWorkshopValidation | StrategyAnalysisPlanning | StrategyDecisionAssumptionsHypothesis | ArchitectureEngineeringFeedbackValidationTasks |