View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy GAP Analysis |  Product Strategy Impact Mapping |  Architecture ARID (Active Reviews for Intermediate Designs) |  Architecture Risk Storming |
|---|---|---|---|---|
Purposedifferent | 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. | When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures. | 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 h | 45-90 min | 2–4 h review as a planning range; preparation and evaluation additional | 60-90 min |
Participantsdifferent | 2-8 | 3-8 | Designers, developers as users, and facilitation | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Gap Matrix, Action Plan, Risk Notes | Impact Map, Outcome Hypotheses, Delivery Options | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | StrategyAnalysisPlanning | OutcomesStrategyBehaviorPlanning | ArchitectureEngineeringFeedbackValidationTasks | RiskArchitectureWorkshopValidation |