View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Assumption Surfacing |  Operations A3 Problem Solving |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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. | 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 single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Low | Medium | High | Low |
Timedifferent | 45-90 min | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 15-30 min |
Participantsdifferent | 2-8 | 2-5 | Evaluation team, architects, and relevant stakeholders | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Assumption List, Critical Assumptions, Learning Plan | A3 Report, Action Plan, Root Cause Analysis | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Root cause notes, Countermeasures |
Tagsno overlap | AssumptionsRiskDecisionDiscovery | LeanProblem solvingCoachingOperations | ArchitectureQualityRiskTradeoffsStakeholders | Root causeIncidentLeanProblem solving |