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 Process Mapping |  Systems Thinking Rich Picture |  DevOps Game Day |  Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | 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. | A Rich Picture brings an unclear situation onto a shared drawing. It captures actors, tensions, information flows, and blind spots before the team jumps to solutions too early. | In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic. | 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 | Medium | Low | High | Low |
Timedifferent | 1-3 h | 30-90 min | Halber Tag | 20-45 min |
Participantsdifferent | 3-10 | 2-10 | 5-20 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | Rich Picture, Problem Framing Notes | Simulation Notes, Gaps List, Updated Runbooks | Lessons learned, Action items, Event summary |
Tagsno overlap | ProcessOperationsImprovement | Systems thinkingSoft systemsFramingVisualization | ResilienceOperationsIncident | LearningOperationsImprovement |