View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery RAID Log | ![]() Architecture arc42 | ![]() Business Strategy Strategic, Tactical and Operational Planning | ![]() Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 30 min Setup, dann laufend | 1-2 Tage | 90-180 min | 60-120 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1-4 | 4-12 | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Architecture Document, Context View, Runtime View, Deployment View | Planning Levels Map, Cadence Model, Planning Artifact Inventory | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | RiskTrackingStakeholdersGovernance | ArchitectureDocumentationCommunication | CadenceGovernanceExecution | ArchitectureCommunicationStakeholdersCanvas |



