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 LoopArchitecture Decision RecordSoftware Architecture CanvasArchitecture Communication Canvas
| Criterion | ![]() Business Strategy Strategy Execution Loop | ![]() Architecture Architecture Decision Record | ![]() Architecture Software Architecture Canvas | ![]() Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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. | 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 Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | High | Low | Low | Medium |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 15-45 min | 1-2 h | 60-120 min |
Participantsdifferent | 5-12 | 1-3 | 3-10 | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | ADR File, Decision Log, Rationale | Architecture Canvas, Goals, Constraints, Quality Attributes | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | ExecutionCadenceLearningGovernance | ArchitectureRationaleDocumentationGovernance | CanvasArchitectureAlignmentWorkshop | ArchitectureCommunicationStakeholdersCanvas |



