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 |  Business Strategy SWOT Analysis |  Operations Getting Things Done |
|---|---|---|---|---|
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. | SWOT Analysis arranges strengths, weaknesses, opportunities, and threats into a compact picture of the situation. It keeps internal capabilities and external influences separate before strategic options emerge from them. | With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 1-3 h | 30-60 min | 1-2 h Setup, laufend |
Participantsdifferent | Designers, developers as users, and facilitation | 2-8 | 3-12 | 1 |
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 | Gap Matrix, Action Plan, Risk Notes | SWOT matrix, Strategic options, Action list | Action Lists, Project List, Review Routine |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | StrategyAnalysisPlanning | StrategyAnalysisMarketPositioning | ProductivityPlanningTasksExecution |