View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Business Model Stress TestFailure Mode and Effects AnalysisATAM (Architecture Tradeoff Analysis Method)Fishbone Diagram
| Criterion |  Business Strategy Business Model Stress Test |  Operations Failure Mode and Effects Analysis |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations Fishbone Diagram |
|---|---|---|---|---|
Purposedifferent | A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario. | 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. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. |
Complexitydifferent | High | High | High | Low |
Timedifferent | Half day | 2-6 h | Several meetings plus preparation and analysis; total effort depends on scope | 30-60 min |
Participantsdifferent | 3-8 | 3-10 | Evaluation team, architects, and relevant stakeholders | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Stress Test Report, Action Plan per Scenario | 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 | Fishbone Diagram, Cause Categories, Investigation Backlog |
Tagsno overlap | StrategyBusiness modelRiskDiagnosis | RiskQualityOperationsRoot cause | ArchitectureQualityRiskTradeoffsStakeholders | Root causeQualityOperations |