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 |  Architecture Risk Storming |  Architecture ARID (Active Reviews for Intermediate Designs) |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
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. | 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. | 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. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-3 h | 60-90 min | 2–4 h review as a planning range; preparation and evaluation additional | 45-60 min |
Participantsdifferent | 2-8 | 4-12 | Designers, developers as users, and facilitation | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Gap Matrix, Action Plan, Risk Notes | Annotated Diagram, Prioritized Risk List, Action Backlog | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | StrategyAnalysisPlanning | RiskArchitectureWorkshopValidation | ArchitectureEngineeringFeedbackValidationTasks | AssumptionsRiskExperimentsValidation |