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 Event Modeling |  Operations Gemba Walk |  UX Research Contextual Inquiry |  Knowledge Modeling Domain Storytelling |
|---|---|---|---|---|
Purposedifferent | 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. | When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. | When work processes are known only from accounts and the real context stays hidden, Contextual Inquiry makes behavior at the workplace visible. Observation and follow-up questions together show how people actually work, get interrupted, and improvise. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 2-6 h | 30-120 min | 1-3 Wochen | 1-2 h |
Participantsdifferent | 2-8 | 2-6 | 4-12 Beobachtungen | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | Observation Notes, Improvement Ideas | Field Notes, Workflow Insights, Pain Points | Domain Story, Glossary Notes, Process Narrative |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | LeanObservationProcessOperations | UX researchObservationContext | KnowledgeDomain-Driven DesignProcess |