View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Argument MappingTeam Topologies Interaction ModesArchitecture Decision RecordSpotify Model Mapping
| Criterion |  Decision Making Argument Mapping |  Team Design Team Topologies Interaction Modes |  Architecture Architecture Decision Record |  Team Design Spotify Model Mapping |
|---|---|---|---|---|
Purposedifferent | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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 | Medium | Low | Medium |
Timedifferent | 1-3 h | Half day | 15-45 min | 90-180 min |
Participantsdifferent | 1-8 | Team-Leads plus Architecture | 1-3 | 5-15 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | Argument Map, Evidence Gaps, Decision Rationale | Interaction Heat Map, Agreements per Pair | ADR File, Decision Log, Rationale | Spotify Model Map, Action List |
Tagsno overlap | SensemakingDecisionRationale | TeamAlignmentCollaborationOrganization | ArchitectureRationaleDocumentationGovernance | TeamOrganizationAlignmentDiagnosis |