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 Funnel Analysis |  Domain Modeling Context Map |  Growth A/B Testing |
|---|---|---|---|---|
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 many visitors or users drop off along the way, the reason behind the number often stays hidden. Funnel Analysis exposes these transitions and makes visible exactly where the path collapses. | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. |
Complexitydifferent | Low | Medium | Medium | High |
Timedifferent | 1-2 h | 1-3 h | 1-3 h | 1-4 Wochen |
Participantsdifferent | 2-8 | 1-5 | 2-8 | 1-6 |
Formatdifferent | Workshop | Async | Workshop + async | Async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Funnel report, Drop-off analysis, Optimization hypotheses | Context Map, Integration Patterns, Boundary Notes | Experiment results, Decision log, Learning summary |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | AnalyticsConversionGrowth | Domain-Driven DesignBoundariesStrategy | ExperimentsGrowthAnalyticsValidation |