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 Domain Context Map
Domain Modeling
Domain Context Map
Paper illustration for PDCA Cycle.
Operations
PDCA Cycle
Paper illustration for Kaizen Event.
Operations
Kaizen Event
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 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.For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode.For a tightly scoped process segment with noticeable waste, the method bundles shared energy for change. It suits situations that call for fast learning loops and visible adjustments.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
1-3 h1-3 h1 h bis mehrere Wochen0.5-5 Tage
Participantsdifferent
2-83-101-84-10
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Context Map, Integration Patterns, Boundary NotesDomain Context Map, Boundary Notes, Ownership MapPDCA Log, Experiment Plan, Learning Outcome, Standard ChangeKaizen Charter, Waste List, Improvement Experiments, Standard Work Update
Tagsno overlap
Domain-Driven DesignBoundariesStrategy
Domain-Driven DesignContextBoundaries
Continuous improvementLeanExperiments
LeanContinuous improvementOperations
Add more methods