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 Strategy Execution Loop |  Architecture Risk Storming |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|
Purposedifferent | The Strategy Execution Loop helps avoid treating strategy as a one-off document. It makes visible how strategic decisions are turned into objectives, initiatives, operational work, measurement, and learning. | 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. |
Complexitydifferent | High | Low | Medium |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 60-90 min | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 5-12 | 4-12 | Designers, developers as users, and facilitation |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Annotated Diagram, Prioritized Risk List, Action Backlog | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | ExecutionCadenceLearningGovernance | RiskArchitectureWorkshopValidation | ArchitectureEngineeringFeedbackValidationTasks |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
