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 a Polarity Map with two poles and four quadrants
Systems Thinking
Polarity Mapping
Paper illustration of Spotify Model Mapping with its method-specific working model.
Team Design
Spotify Model Mapping
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of Team Topologies Interaction Modes with its method-specific working model.
Team Design
Team Topologies Interaction Modes
Purposedifferent
Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely.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.When several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
1-2 h90-180 minSeveral meetings plus preparation and analysis; total effort depends on scopeHalf day
Participantsdifferent
3-125-15Evaluation team, architects, and relevant stakeholdersTeam-Leads plus Architecture
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Polarity Map, Warning Signs, Balance ActionsSpotify Model Map, Action ListPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsInteraction Heat Map, Agreements per Pair
Tagsno overlap
Systems thinkingTradeoffsLeadership
TeamOrganizationAlignmentDiagnosis
ArchitectureQualityRiskTradeoffsStakeholders
TeamAlignmentCollaborationOrganization
Add more methods