View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Operations Getting Things Done | ![]() Knowledge Modeling Domain Storytelling | ![]() Domain Modeling EventStorming |
|---|---|---|---|
Purposedifferent | With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory. | 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 domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-2 h Setup, laufend | 1-2 h | 2-8 h |
Participantsdifferent | 1 | 2-8 | 5-12 |
Formatdifferent | Async | Workshop | Workshop |
Outputdifferent | Action Lists, Project List, Review Routine | Domain Story, Glossary Notes, Process Narrative | Event Timeline, Ubiquitous Language, Boundaries, Open Questions |
Tagsno overlap | ProductivityPlanningTasksExecution | KnowledgeDomain-Driven DesignProcess | Domain-Driven DesignEventsDiscoveryWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






