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 |  Operations A3 Problem Solving |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | 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 | 20-60 min | 1-4 h | 45-90 min | 60-120 min |
Participantsdifferent | 1-4 | 1-5 | 2-5 | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Runbook, Checklist, Escalation Path | Context Diagram, Container Diagram, Component Diagram | A3 Report, Action Plan, Root Cause Analysis | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | OperationsReliabilityDocumentation | ArchitectureCommunicationVisualization | LeanProblem solvingCoachingOperations | ArchitectureCommunicationStakeholdersCanvas |