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 Views and Beyond | ![]() Architecture Architecture Decision Record | ![]() Operations Runbook | ![]() Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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. | 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 | Medium | Low | Low | Medium |
Timedifferent | 1-3 Tage | 15-45 min | 20-60 min | 60-120 min |
Participantsdifferent | 1-4 | 1-3 | 1-4 | 2-8 |
Formatdifferent | Workshop + async | Async | Async | Workshop + async |
Outputdifferent | Architecture Views, Cross-view Notes, Rationale | ADR File, Decision Log, Rationale | Runbook, Checklist, Escalation Path | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | DocumentationStakeholdersArchitecture | ArchitectureRationaleDocumentationGovernance | OperationsReliabilityDocumentation | ArchitectureCommunicationStakeholdersCanvas |



