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 |  Team Design Team API |  Agile Working Agreements |
|---|---|---|---|---|
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 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 collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 1-2 h | 2-4 h | Half day initial, dann laufend | 45-90 min |
Participantsdifferent | 2-8 | 3-12 | Ein Team plus Stakeholder | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Team Charter, Working Norms, Role Notes | Team API Document | Working Agreements, Team Norms, Review Cadence |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | TeamAlignmentCollaboration | TeamAlignmentCommunicationService | TeamCollaborationAgile |