View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  Operations Runbook |  Delivery RAID Log |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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. | For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access. | 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 15-45 min | 20-60 min | 30 min Setup, dann laufend | 60-120 min |
Participantsdifferent | 1-3 | 1-4 | 1-3 maintaining, briefing for everyone | 2-8 |
Formatdifferent | Async | Async | Async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Runbook, Checklist, Escalation Path | RAID Log, Status Report Source | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | OperationsReliabilityDocumentation | RiskTrackingStakeholdersGovernance | ArchitectureCommunicationStakeholdersCanvas |