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 Theory of Constraints.
Operations
Theory of Constraints
Paper illustration for ALPEN Method
Operations
ALPEN Method
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 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 an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time.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
LowHighLowMedium
Timedifferent
1-2 h2-4 h Analyse, laufend10-20 min daily1-3 h
Participantsdifferent
2-83-1213-10
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeConstraint Map, Improvement Plan, Flow MetricsDaily Plan, Time Estimates, Review NotesProcess Map, Handoff List, Improvement Backlog
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
OperationsConstraintsFlowImprovement
PlanningTime managementProductivityOperations
ProcessOperationsImprovement
Add more methods