View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Design ThinkingOutcome-Driven InnovationATAM (Architecture Tradeoff Analysis Method)Failure Mode and Effects Analysis
| Criterion |  Innovation Design Thinking |  Product Discovery Outcome-Driven Innovation |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
Purposedifferent | For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service. | 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. | 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. |
Complexitysame | High | High | High | High |
Timedifferent | 1 Tag bis mehrere Wochen | Mehrere Wochen | Several meetings plus preparation and analysis; total effort depends on scope | 2-6 h |
Participantsdifferent | 4-10 | 2-6 researchers plus sample | Evaluation team, architects, and relevant stakeholders | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Problem Statement, Prototype, Test Learnings | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | 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 | InnovationPrototypeResearch | OutcomesInnovationResearchQuantitative | ArchitectureQualityRiskTradeoffsStakeholders | RiskQualityOperationsRoot cause |