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 | ![]() Facilitation Team Charter | ![]() Team Design Spotify Model Mapping |
|---|---|---|---|
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 is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. | 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 | Low | Medium | Medium |
Timedifferent | 45-90 min | 2-4 h | 90-180 min |
Participantsdifferent | 3-12 | 3-12 | 5-15 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Working Agreements, Team Norms, Review Cadence | Team Charter, Working Norms, Role Notes | Spotify Model Map, Action List |
Tags1 shared | TeamCollaborationAgile | TeamAlignmentCollaboration | TeamOrganizationAlignmentDiagnosis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






