View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:VRIO FrameworkFailure Mode and Effects AnalysisATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Business Strategy VRIO Framework |  Operations Failure Mode and Effects Analysis |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|
Purposedifferent | The VRIO Framework rates resources and capabilities on whether they are Valuable, Rare, Inimitable, and Organized. It compares strengths, risks, market logic, and courses of action. The result is captured as a VRIO table and strategic actions. | 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 | 90-180 min | 2-6 h | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-6 | 3-10 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | VRIO Table, Strategic Actions | 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 | StrategyDiagnosisBusiness modelCapability | RiskQualityOperationsRoot cause | ArchitectureQualityRiskTradeoffsStakeholders |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
