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 |  Architecture Architecture Decision Record |  Operations RACI Matrix |
|---|---|---|---|---|
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. | 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. | With unclear responsibilities across several roles or areas, the method creates unambiguous accountability logic. It reduces friction because decision, execution, contribution, and information become separately visible. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 20-60 min | 1-4 h | 15-45 min | 45-90 min |
Participantsdifferent | 1-4 | 1-5 | 1-3 | 2-8 |
Formatdifferent | Async | Workshop + async | Async | Workshop + async |
Outputdifferent | Runbook, Checklist, Escalation Path | Context Diagram, Container Diagram, Component Diagram | ADR File, Decision Log, Rationale | RACI Matrix, Responsibility Map, Decision Notes |
Tagsno overlap | OperationsReliabilityDocumentation | ArchitectureCommunicationVisualization | ArchitectureRationaleDocumentationGovernance | RolesResponsibilityGovernanceOperations |