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 |  Team Design Team Topologies Interaction Modes |  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 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. | 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 | 1-2 h | Half day | 90-180 min |
Participantsdifferent | 2-8 | Team-Leads plus Architecture | 5-15 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Interaction Heat Map, Agreements per Pair | Spotify Model Map, Action List |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | TeamAlignmentCollaborationOrganization | TeamOrganizationAlignmentDiagnosis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
