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 |  Architecture arc42 |  Operations Fishbone Diagram |  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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | 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 | Low | Low |
Timedifferent | 1-3 h | 1-2 Tage | 30-60 min | 20-45 min |
Participantsdifferent | 3-10 | 1-4 | 2-8 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | Architecture Document, Context View, Runtime View, Deployment View | Fishbone Diagram, Cause Categories, Investigation Backlog | Lessons learned, Action items, Event summary |
Tagsno overlap | ProcessOperationsImprovement | ArchitectureDocumentationCommunication | Root causeQualityOperations | LearningOperationsImprovement |