View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Runbook |  Architecture C4 Model |  Delivery Communication Plan |  Architecture Views and Beyond |
|---|---|---|---|---|
Purposedifferent | 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 C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. | 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 20-60 min | 1-4 h | 45-90 min | 1-3 Tage |
Participantsdifferent | 1-4 | 1-5 | 2-6 | 1-4 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Runbook, Checklist, Escalation Path | Context Diagram, Container Diagram, Component Diagram | Communication Plan, Channel Matrix, Message Cadence | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | OperationsReliabilityDocumentation | ArchitectureCommunicationVisualization | CommunicationStakeholdersDeliveryPlanning | DocumentationStakeholdersArchitecture |