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 Brainstorming |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|
Purposedifferent | 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. | 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 process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. |
Complexitydifferent | Low | High | High |
Timedifferent | 30-60 min | Several meetings plus preparation and analysis; total effort depends on scope | 2-6 h |
Participantsdifferent | 4-12 | Evaluation team, architects, and relevant stakeholders | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Idea pool, Theme clusters, Shortlist | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | BrainstormingIdeationCreativityWorkshopDivergence | ArchitectureQualityRiskTradeoffsStakeholders | RiskQualityOperationsRoot cause |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
