methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of Spotify Model Mapping with its method-specific working model.
Team Design
Spotify Model Mapping
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
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.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.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.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
MediumLowMediumHigh
Timedifferent
90-180 min45-90 min1-3 hSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
5-153-123-12Evaluation team, architects, and relevant stakeholders
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Spotify Model Map, Action ListExpectation Map, Alignment Notes, AgreementsKnowledge Map, Critical Knowledge Areas, Transfer PlanPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
TeamOrganizationAlignmentDiagnosis
AlignmentStakeholdersTeam
KnowledgeMappingRisk
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods