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 |  Operations Process Mapping |  Systems Thinking CATWOE Analysis |  Operations After-Action Review |
|---|---|---|---|---|
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. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 20-60 min | 1-3 h | 45-90 min | 20-45 min |
Participantsdifferent | 1-4 | 3-10 | 3-8 | 3-12 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Runbook, Checklist, Escalation Path | Process Map, Handoff List, Improvement Backlog | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Lessons learned, Action items, Event summary |
Tagsno overlap | OperationsReliabilityDocumentation | ProcessOperationsImprovement | Systems thinkingFramingStakeholders | LearningOperationsImprovement |