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
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
Paper illustration for Kaizen Event.
Operations
Kaizen Event
Paper illustration for PDCA Cycle.
Operations
PDCA Cycle
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Purposedifferent
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 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.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.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.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
1-3 h0.5-5 Tage1 h bis mehrere Wochen1-3 h
Participantsdifferent
3-104-101-82-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Domain Context Map, Boundary Notes, Ownership MapKaizen Charter, Waste List, Improvement Experiments, Standard Work UpdatePDCA Log, Experiment Plan, Learning Outcome, Standard ChangeContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
Domain-Driven DesignContextBoundaries
LeanContinuous improvementOperations
Continuous improvementLeanExperiments
Domain-Driven DesignBoundariesStrategy
Add more methods