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 ATAM (Architecture Tradeoff Analysis Method) |  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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | 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 | High | Medium |
Timedifferent | 20-45 min | Several meetings plus preparation and analysis; total effort depends on scope | 45-90 min |
Participantsdifferent | 3-12 | Evaluation team, architects, and relevant stakeholders | 2-5 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Lessons learned, Action items, Event summary | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | LearningOperationsImprovement | ArchitectureQualityRiskTradeoffsStakeholders | LeanProblem solvingCoachingOperations |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
