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 of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
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 group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.
Complexitydifferent
MediumMediumLow
Timedifferent
1-3 h1-3 h45-90 min
Participantsdifferent
2-85-302-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + async
Outputdifferent
Context Map, Integration Patterns, Boundary NotesConsensus Clusters, Theme Titles, Priority AreasAssumption List, Critical Assumptions, Learning Plan
Tagsno overlap
Domain-Driven DesignBoundariesStrategy
FacilitationConsensusWorkshopAlignment
AssumptionsRiskDecisionDiscovery
Add more methods

Often compared together

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

Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Paper illustration of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
Paper illustration of DIBB with its method-specific working model.
Product Strategy
DIBB
EventStorming on a long working surface: colored event cards form a business flow, friction points are marked, and a boundary separates different areas of responsibility.
Domain Modeling
EventStorming