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 LoopRAID LogArchitecture Communication CanvasArchitecture Decision Record
| Criterion | ![]() Business Strategy Strategy Execution Loop | ![]() Delivery RAID Log | ![]() Architecture Architecture Communication Canvas | ![]() 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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 | Low | Medium | Low |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 30 min Setup, dann laufend | 60-120 min | 15-45 min |
Participantsdifferent | 5-12 | 1-3 maintaining, briefing for everyone | 2-8 | 1-3 |
Formatdifferent | Workshop + async | Async | Workshop + async | Async |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | RAID Log, Status Report Source | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | ADR File, Decision Log, Rationale |
Tagsno overlap | ExecutionCadenceLearningGovernance | RiskTrackingStakeholdersGovernance | ArchitectureCommunicationStakeholdersCanvas | ArchitectureRationaleDocumentationGovernance |



