View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research Contextual Inquiry |  Domain Modeling Bounded Context Canvas |  Knowledge Modeling IBIS |  Knowledge Modeling Domain Storytelling |
|---|---|---|---|---|
Purposedifferent | 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. | When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold. | IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus. | 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 | Medium | Medium | Low |
Timedifferent | 1-3 Wochen | 1-3 h | 1-3 h | 1-2 h |
Participantsdifferent | 4-12 Beobachtungen | 3-8 | 2-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Context Canvas, Glossary, Integration Notes | Issue Map, Positions, Argument Notes | Domain Story, Glossary Notes, Process Narrative |
Tagsno overlap | UX researchObservationContext | Domain-Driven DesignBoundariesModeling | RationaleKnowledgeDecision | KnowledgeDomain-Driven DesignProcess |