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 |  Delivery RAID Log |  Architecture Risk Storming |  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. | 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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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 | 30 min Setup, dann laufend | 60-90 min | 60-120 min |
Participantsdifferent | 5-12 | 1-3 maintaining, briefing for everyone | 4-12 | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | RAID Log, Status Report Source | Annotated Diagram, Prioritized Risk List, Action Backlog | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | ExecutionCadenceLearningGovernance | RiskTrackingStakeholdersGovernance | RiskArchitectureWorkshopValidation | ArchitectureCommunicationStakeholdersCanvas |