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 SCAMPER |  Operations Failure Mode and Effects Analysis |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|
Purposedifferent | For an existing solution under pressure to change, the method deliberately opens space for systematic variants. It directs attention to rebuilding, combining, and repurposing rather than only new basic ideas. This produces concrete evolution paths for products, offerings, or workflows. | 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. | 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. |
Complexitydifferent | Low | High | High |
Timedifferent | 30-60 min | 2-6 h | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 2-10 | 3-10 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | SCAMPER Idea List, Concept Shortlist, Variation Notes | FMEA Table, Risk Priority, Mitigation Actions | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | BrainstormingIdeationCreativityReframingInnovation | RiskQualityOperationsRoot cause | ArchitectureQualityRiskTradeoffsStakeholders |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
