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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
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
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
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 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 people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.
Complexitysame
MediumMediumMediumMedium
Timedifferent
1-3 h1-3 h90-180 min initial, dann laufend1-2 h
Participantsdifferent
2-83-103-84-12
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Context Map, Integration Patterns, Boundary NotesDomain Context Map, Boundary Notes, Ownership MapKPI Tree, Owner ListAlignment Map, Open Issues, Decision Questions
Tagsno overlap
Domain-Driven DesignBoundariesStrategy
Domain-Driven DesignContextBoundaries
MetricsStrategyAlignmentMeasurement
AlignmentStakeholdersStrategyFacilitation
Add more methods