View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Knowledge MappingExpectation MappingSpotify Model MappingATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Knowledge Modeling Knowledge Mapping |  Facilitation Expectation Mapping |  Team Design Spotify Model Mapping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | 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. | 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 | Low | Medium | High |
Timedifferent | 1-3 h | 45-90 min | 90-180 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-12 | 3-12 | 5-15 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Expectation Map, Alignment Notes, Agreements | 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 | KnowledgeMappingRisk | AlignmentStakeholdersTeam | TeamOrganizationAlignmentDiagnosis | ArchitectureQualityRiskTradeoffsStakeholders |