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 Views and Beyond |  Operations 5 Whys |  Operations A3 Problem Solving |
|---|---|---|---|---|
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. | 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. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | 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. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 20-60 min | 1-3 Tage | 15-30 min | 45-90 min |
Participantsdifferent | 1-4 | 1-4 | 2-6 | 2-5 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Runbook, Checklist, Escalation Path | Architecture Views, Cross-view Notes, Rationale | Root cause notes, Countermeasures | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | OperationsReliabilityDocumentation | DocumentationStakeholdersArchitecture | Root causeIncidentLeanProblem solving | LeanProblem solvingCoachingOperations |