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 API |  Facilitation Team Charter |
|---|---|---|---|
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 expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document. | 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. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 1-2 h | Half day initial, dann laufend | 2-4 h |
Participantsdifferent | 2-8 | Ein Team plus Stakeholder | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Team API Document | Team Charter, Working Norms, Role Notes |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | TeamAlignmentCommunicationService | TeamAlignmentCollaboration |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
