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 RecordC4 ModelStrategy Execution LoopStrategic, Tactical and Operational Planning
| Criterion | ![]() Architecture Architecture Decision Record | ![]() Architecture C4 Model | ![]() Business Strategy Strategy Execution Loop | ![]() Business Strategy Strategic, Tactical and Operational Planning |
|---|---|---|---|---|
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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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. | 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. |
Complexitydifferent | Low | Low | High | Medium |
Timedifferent | 15-45 min | 1-4 h | Initial 3-6 h, then monthly or quarterly reviews | 90-180 min |
Participantsdifferent | 1-3 | 1-5 | 5-12 | 4-12 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Context Diagram, Container Diagram, Component Diagram | Execution Loop, Review Cadence, Strategic Learning Log | Planning Levels Map, Cadence Model, Planning Artifact Inventory |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationVisualization | ExecutionCadenceLearningGovernance | CadenceGovernanceExecution |



