View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Working Agreements |  Team Design Spotify Model Mapping |  Facilitation Dot Estimation |  Team Design Team Topologies Interaction Modes |
|---|---|---|---|---|
Purposedifferent | When collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths. | 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 size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets. | 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 | Low | Medium | Low | Medium |
Timedifferent | 45-90 min | 90-180 min | 5-20 min | Half day |
Participantsdifferent | 3-12 | 5-15 | 3-20 | Team-Leads plus Architecture |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Working Agreements, Team Norms, Review Cadence | Spotify Model Map, Action List | Effort Heatmap, Risk Signals, Discussion Targets | Interaction Heat Map, Agreements per Pair |
Tagsno overlap | TeamCollaborationAgile | TeamOrganizationAlignmentDiagnosis | EstimationEffortRisk | TeamAlignmentCollaborationOrganization |