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 board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
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 work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an 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.
Complexitydifferent
MediumLowMedium
Timedifferent
1-3 h20-40 min initial, dann laufend1-2 h
Participantsdifferent
2-83-154-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Context Map, Integration Patterns, Boundary NotesROAM Board, Owner ListAlignment Map, Open Issues, Decision Questions
Tagsno overlap
Domain-Driven DesignBoundariesStrategy
RiskAgileTrackingAlignment
AlignmentStakeholdersStrategyFacilitation
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of Power-Interest Grid with a method-specific labelled workspace.
Facilitation
Power Interest Grid
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Paper illustration of Stakeholder Salience Model with its method-specific working model.
Facilitation
Stakeholder Salience Model