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 |  Operations ALPEN Method |  Business Strategy GAP Analysis |
|---|---|---|---|---|
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. | With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time. | 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. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 0.5-2 Tage | 10-20 min daily | 1-3 h |
Participantsdifferent | Designers, developers as users, and facilitation | 4-12 | 1 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Scenario Set, Strategic Implications, Robust Options | Daily Plan, Time Estimates, Review Notes | Gap Matrix, Action Plan, Risk Notes |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | StrategyUncertaintyPlanning | PlanningTime managementProductivityOperations | StrategyAnalysisPlanning |