methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
A paper-based illustration representing Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
Paper illustration for Contextual Inquiry.
UX Research
Contextual Inquiry
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Purposedifferent
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.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.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.
Complexitydifferent
LowLowMediumMedium
Timedifferent
30-120 min1-2 h1-3 Wochen1-3 h
Participantsdifferent
2-62-84-12 Beobachtungen3-10
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Observation Notes, Improvement IdeasDomain Story, Glossary Notes, Process NarrativeField Notes, Workflow Insights, Pain PointsProcess Map, Handoff List, Improvement Backlog
Tagsno overlap
LeanObservationProcessOperations
KnowledgeDomain-Driven DesignProcess
UX researchObservationContext
ProcessOperationsImprovement
Add more methods