View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Jobs to Be DoneScatter DiagramFailure Mode and Effects AnalysisATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Product Discovery Jobs to Be Done |  Operations Scatter Diagram |  Operations Failure Mode and Effects Analysis |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | When switching motives and progress are unclear, it reconstructs the situation from real customer circumstances. It shows why a switch happens and what kind of progress is being sought. | When the question is whether two measures are related, the method makes patterns in the data picture visible. It separates felt correlations from relationships that actually show up in the data. | 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 | Low | High | High |
Timedifferent | 1-3 Wochen | 30-90 min | 2-6 h | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 5-12 Interviews | 1-4 | 3-10 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Job Stories, Outcome Statements, Opportunity List | Scatter Plot, Korrelationsnotiz, Hypothesenliste | 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 | CustomerOutcomesNeeds | Root causeQualityVisualization | RiskQualityOperationsRoot cause | ArchitectureQualityRiskTradeoffsStakeholders |