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 FrameworkExpectation MappingATAM (Architecture Tradeoff Analysis Method)Spotify Model Mapping
| Criterion | ![]() Business Strategy VRIO Framework | ![]() Facilitation Expectation Mapping | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) | ![]() Team Design Spotify Model Mapping |
|---|---|---|---|---|
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 roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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 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. |
Complexitydifferent | Medium | Low | High | Medium |
Timedifferent | 90-180 min | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 90-180 min |
Participantsdifferent | 3-6 | 3-12 | Evaluation team, architects, and relevant stakeholders | 5-15 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | VRIO Table, Strategic Actions | Expectation Map, Alignment Notes, Agreements | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Spotify Model Map, Action List |
Tagsno overlap | StrategyDiagnosisBusiness modelCapability | AlignmentStakeholdersTeam | ArchitectureQualityRiskTradeoffsStakeholders | TeamOrganizationAlignmentDiagnosis |



