View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Domain Storytelling |  Facilitation Team Charter |  Facilitation Expectation Mapping |  Team Design Spotify Model Mapping |
|---|---|---|---|---|
Purposedifferent | Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected. | 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 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. | 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 | Low | Medium |
Timedifferent | 1-2 h | 2-4 h | 45-90 min | 90-180 min |
Participantsdifferent | 2-8 | 3-12 | 3-12 | 5-15 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Team Charter, Working Norms, Role Notes | Expectation Map, Alignment Notes, Agreements | Spotify Model Map, Action List |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | TeamAlignmentCollaboration | AlignmentStakeholdersTeam | TeamOrganizationAlignmentDiagnosis |