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 After-Action Review |  Architecture arc42 |  Operations Kepner-Tregoe |  Operations A3 Problem Solving |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | 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 | Low | High | Medium |
Timedifferent | 20-45 min | 1-2 Tage | 2-8 h | 45-90 min |
Participantsdifferent | 3-12 | 1-4 | 2-8 | 2-5 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Lessons learned, Action items, Event summary | Architecture Document, Context View, Runtime View, Deployment View | Problem Analysis, Decision Analysis, Risk Plan | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | LearningOperationsImprovement | ArchitectureDocumentationCommunication | Problem solvingRoot causeDecisionOperations | LeanProblem solvingCoachingOperations |