View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Innovation Reverse Brainstorming | ![]() Operations Root Cause Analysis | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) | ![]() Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | For persistent errors or blockages, the method shifts the view to the opposite of the desired effect. It exposes the mechanics of failure and makes hidden causes easier to grasp. This makes improvement more concrete and the problem clearer. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. | 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 | 30-60 min | 1-4 h | Several meetings plus preparation and analysis; total effort depends on scope | 15-30 min |
Participantsdifferent | 3-12 | 3-8 | Evaluation team, architects, and relevant stakeholders | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Reverse Ideas, Risk Themes, Solution Ideas | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | 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 | BrainstormingIdeationCreativityRisk | Root causeProblem solvingQualityIncident | ArchitectureQualityRiskTradeoffsStakeholders | Root causeIncidentLeanProblem solving |



