View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Working BackwardsFailure Mode and Effects AnalysisATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Product Discovery Working Backwards |  Operations Failure Mode and Effects Analysis |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|
Purposedifferent | When the target state and benefit need to be clear first, it thinks backward from the desired outcome into the product logic. It sharpens vision, objections, and value proposition before elaboration. | 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 | Medium | High | High |
Timedifferent | 4-8 h, mehrere Iterationen | 2-6 h | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 2-6 | 3-10 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Future Press Release, FAQ, Vision Statement | 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 | VisionNarrativeAlignment | RiskQualityOperationsRoot cause | ArchitectureQualityRiskTradeoffsStakeholders |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
