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 | ![]() Knowledge Modeling Domain Storytelling | ![]() Operations After-Action Review | ![]() Operations Gemba Walk |
|---|---|---|---|---|
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. | 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. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 Wochen | 1-2 h | 20-45 min | 30-120 min |
Participantsdifferent | 4-12 Beobachtungen | 2-8 | 3-12 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Domain Story, Glossary Notes, Process Narrative | Lessons learned, Action items, Event summary | Observation Notes, Improvement Ideas |
Tagsno overlap | UX researchObservationContext | KnowledgeDomain-Driven DesignProcess | LearningOperationsImprovement | LeanObservationProcessOperations |



