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
A paper-based illustration representing Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Paper illustration for Contextual Inquiry.
UX Research
Contextual Inquiry
Paper illustration for Domain Context Map
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 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.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
LowLowMediumMedium
Timedifferent
1-2 h30-120 min1-3 Wochen1-3 h
Participantsdifferent
2-82-64-12 Beobachtungen3-10
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeObservation Notes, Improvement IdeasField Notes, Workflow Insights, Pain PointsDomain Context Map, Boundary Notes, Ownership Map
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
LeanObservationProcessOperations
UX researchObservationContext
Domain-Driven DesignContextBoundaries
Add more methods