View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Strategy Execution LoopARID (Active Reviews for Intermediate Designs)Architecture Decision Record
| Criterion |  Business Strategy Strategy Execution Loop |  Architecture ARID (Active Reviews for Intermediate Designs) |  Architecture Architecture Decision Record |
|---|---|---|---|
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. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. |
Complexitydifferent | High | Medium | Low |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 2–4 h review as a planning range; preparation and evaluation additional | 15-45 min |
Participantsdifferent | 5-12 | Designers, developers as users, and facilitation | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | ADR File, Decision Log, Rationale |
Tagsno overlap | ExecutionCadenceLearningGovernance | ArchitectureEngineeringFeedbackValidationTasks | ArchitectureRationaleDocumentationGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
