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 | ![]() Operations Getting Things Done | ![]() 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. | 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. | 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 | Medium | Medium |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 1-2 h Setup, laufend | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 5-12 | 1 | Designers, developers as users, and facilitation |
Formatdifferent | Workshop + async | Async | Workshop + async |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Action Lists, Project List, Review Routine | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | ExecutionCadenceLearningGovernance | ProductivityPlanningTasksExecution | ArchitectureEngineeringFeedbackValidationTasks |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






