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 5 Whys |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Innovation Brainstorming |
|---|---|---|---|
Purposedifferent | 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. | 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. | When a team faces an open question with many obvious directions, the method first creates breadth instead of premature commitment. It separates idea flow from evaluation and makes lines of thought visible, creating a pool for selection and further development. |
Complexitydifferent | Low | High | Low |
Timedifferent | 15-30 min | Several meetings plus preparation and analysis; total effort depends on scope | 30-60 min |
Participantsdifferent | 2-6 | Evaluation team, architects, and relevant stakeholders | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Root cause notes, Countermeasures | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Idea pool, Theme clusters, Shortlist |
Tagsno overlap | Root causeIncidentLeanProblem solving | ArchitectureQualityRiskTradeoffsStakeholders | BrainstormingIdeationCreativityWorkshopDivergence |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
