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
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
Paper illustration for Contextual Inquiry.
UX Research
Contextual Inquiry
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.Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins.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.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.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
30-120 min1-3 h1-3 h1-3 Wochen
Participantsdifferent
2-63-123-104-12 Beobachtungen
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Observation Notes, Improvement IdeasSystem Map, Dependencies, Leverage PointsDomain Context Map, Boundary Notes, Ownership MapField Notes, Workflow Insights, Pain Points
Tagsno overlap
LeanObservationProcessOperations
Systems thinkingMappingBoundariesChange
Domain-Driven DesignContextBoundaries
UX researchObservationContext
Add more methods