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 |  UX Research Contextual Inquiry |  Operations A3 Problem Solving |  Domain Modeling Domain Context Map |
|---|---|---|---|---|
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 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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 1-2 h | 1-3 Wochen | 45-90 min | 1-3 h |
Participantsdifferent | 2-8 | 4-12 Beobachtungen | 2-5 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Field Notes, Workflow Insights, Pain Points | A3 Report, Action Plan, Root Cause Analysis | Domain Context Map, Boundary Notes, Ownership Map |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | UX researchObservationContext | LeanProblem solvingCoachingOperations | Domain-Driven DesignContextBoundaries |