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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration for Standard Work Analysis.
Operations
Standard Work Analysis
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
Purposedifferent
When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.When the same task is done differently depending on the person, the method exposes the reliable core. It creates comparability without unnecessarily choking off needed latitude.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 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
MediumMediumLowMedium
Timedifferent
1-3 h1-3 h30-120 min1-3 h
Participantsdifferent
2-82-62-63-10
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Context Map, Integration Patterns, Boundary NotesStandard Work Sheet, Deviation List, Improved Standard, Training NeedsObservation Notes, Improvement IdeasDomain Context Map, Boundary Notes, Ownership Map
Tagsno overlap
Domain-Driven DesignBoundariesStrategy
LeanProcessQuality
LeanObservationProcessOperations
Domain-Driven DesignContextBoundaries
Add more methods