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 Domain Context Map
Domain Modeling
Domain Context Map
Paper illustration of KPI Tree with its method-specific working model.
Product Strategy
KPI Tree
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
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.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.When metrics across the organization drift apart, it arranges drivers and effects under one shared logic. It connects customer value, product logic, and decision priorities. The result is captured as a KPI tree and owner list.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
LowMediumMediumMedium
Timedifferent
1-2 h1-3 h90-180 min initial, dann laufend1-3 h
Participantsdifferent
2-83-103-82-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeDomain Context Map, Boundary Notes, Ownership MapKPI Tree, Owner ListContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
Domain-Driven DesignContextBoundaries
MetricsStrategyAlignmentMeasurement
Domain-Driven DesignBoundariesStrategy
Add more methods