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 PDCA Cycle.
Operations
PDCA Cycle
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration of Counter Metrics with its method-specific working model.
Product Strategy
Counter Metrics
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 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.When a headline metric could mask side effects, it adds guardrail signals against unwanted outcomes. It connects customer value, product logic, and decision priorities. The result is captured as a counter-metric list and guardrail definitions.
Complexitydifferent
LowLowMediumLow
Timedifferent
1-2 h1 h bis mehrere Wochen1-3 h30-60 min
Participantsdifferent
2-81-82-82-6
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativePDCA Log, Experiment Plan, Learning Outcome, Standard ChangeContext Map, Integration Patterns, Boundary NotesCounter Metric List, Guardrail Definitions
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
Continuous improvementLeanExperiments
Domain-Driven DesignBoundariesStrategy
MetricsMeasurementStrategyExperiments
Add more methods