View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordStrategic, Tactical and Operational PlanningStrategy Execution LoopViews and Beyond
| Criterion | ![]() Architecture Architecture Decision Record | ![]() Business Strategy Strategic, Tactical and Operational Planning | ![]() Business Strategy Strategy Execution Loop | ![]() Architecture Views and Beyond |
|---|---|---|---|---|
Purposedifferent | 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. | It places decisions and artifacts at the right level. Strategic planning clarifies direction, tactical planning translates it into programs, and operational planning steers concrete processes. | 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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. |
Complexitydifferent | Low | Medium | High | Medium |
Timedifferent | 15-45 min | 90-180 min | Initial 3-6 h, then monthly or quarterly reviews | 1-3 Tage |
Participantsdifferent | 1-3 | 4-12 | 5-12 | 1-4 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Planning Levels Map, Cadence Model, Planning Artifact Inventory | Execution Loop, Review Cadence, Strategic Learning Log | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | CadenceGovernanceExecution | ExecutionCadenceLearningGovernance | DocumentationStakeholdersArchitecture |



