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 Constraint Analysis.
Decision Making
Constraint Analysis
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.When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped.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, laufend30-90 min1-3 h
Participantsdifferent
2-83-122-83-10
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeConstraint Map, Improvement Plan, Flow MetricsConstraint List, Hard/Soft Classification, Option Impact Notes, Decision BoundariesProcess Map, Handoff List, Improvement Backlog
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
OperationsConstraintsFlowImprovement
ConstraintsDecisionPlanningOptions
ProcessOperationsImprovement
Add more methods