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 |  Growth Flywheel |  Knowledge Modeling Event Modeling |
|---|---|---|---|
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. | Growth often breaks down where a reinforcing mechanism builds up too much friction. A Flywheel shows the cycle of value, repetition, and reinforcement meant to sustain growth. | Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 1-2 h | 60-120 min | 2-6 h |
Participantsdifferent | 2-8 | 3-8 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | Event Model, UI Flow, Commands, Read Models |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | GrowthRetentionConversion | EventsBlueprintDomain-Driven DesignBehavior |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
