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 Scenario Planning |  Product Strategy Impact Mapping |
|---|---|---|---|
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. | Scenario Planning opens the view to several plausible futures instead of a single forecast. The method protects strategies from depending on too narrow an expected path. | 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. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 0.5-2 Tage | 45-90 min |
Participantsdifferent | Designers, developers as users, and facilitation | 4-12 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Scenario Set, Strategic Implications, Robust Options | Impact Map, Outcome Hypotheses, Delivery Options |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | StrategyUncertaintyPlanning | OutcomesStrategyBehaviorPlanning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
