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
Paper illustration for Kaizen Event.
Operations
Kaizen Event
Paper illustration for Theory of Constraints.
Operations
Theory of Constraints
Process Mapping method illustration showing its working structure
Operations
Process Mapping
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.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 a system that does not get faster despite effort, the method directs attention to the bottleneck. It concentrates improvement on the point that actually limits throughput.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.
Complexitydifferent
LowMediumHighMedium
Timedifferent
1-2 h0.5-5 Tage2-4 h Analyse, laufend1-3 h
Participantsdifferent
2-84-103-123-10
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeKaizen Charter, Waste List, Improvement Experiments, Standard Work UpdateConstraint Map, Improvement Plan, Flow MetricsProcess Map, Handoff List, Improvement Backlog
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
LeanContinuous improvementOperations
OperationsConstraintsFlowImprovement
ProcessOperationsImprovement
Add more methods