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 ARID (Active Reviews for Intermediate Designs) |  Business Strategy GAP Analysis |  Decision Making Constraint Analysis |  Product Strategy DIBB |
|---|---|---|---|---|
Purposedifferent | 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. | 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 an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 1-3 h | 30-90 min | 1-2 h |
Participantsdifferent | Designers, developers as users, and facilitation | 2-8 | 2-8 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Gap Matrix, Action Plan, Risk Notes | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | DIBB document, Belief list, Bet list, Learning report |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | StrategyAnalysisPlanning | ConstraintsDecisionPlanningOptions | StrategyDecisionAssumptionsHypothesis |