View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy VRIO Framework |  Team Design Spotify Model Mapping |  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. | When a team landscape has grown without clear grouping, it maps roles and relationships onto the Spotify model. It clarifies responsibility, interaction, and load between teams. The result is captured as a Spotify model map and action list. | 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 | Medium | High |
Timedifferent | 90-180 min | 90-180 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-6 | 5-15 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | VRIO Table, Strategic Actions | Spotify Model Map, Action List | 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 | TeamOrganizationAlignmentDiagnosis | ArchitectureQualityRiskTradeoffsStakeholders |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
