View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Failure Mode and Effects AnalysisOutcome-Driven InnovationSurveysATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Operations Failure Mode and Effects Analysis |  Product Discovery Outcome-Driven Innovation |  UX Research Surveys |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | 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. | Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs. | When a topic needs to be validated broadly and many people can answer the same question, surveys gather structured feedback in a scalable form. Answers become comparable and segmentable instead of remaining merely anecdotal. | 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 | High | High | Medium | High |
Timedifferent | 2-6 h | Mehrere Wochen | 3-14 Tage | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-10 | 2-6 researchers plus sample | 50+ | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | FMEA Table, Risk Priority, Mitigation Actions | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Survey Results, Charts, Segment Insights | 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 | RiskQualityOperationsRoot cause | OutcomesInnovationResearchQuantitative | QuantitativeResearchValidation | ArchitectureQualityRiskTradeoffsStakeholders |