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
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
Empathy Mapping
UX Research
Empathy Mapping
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Purposedifferent
When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views.When a lot is assumed about a target group but little is seen jointly, empathy mapping makes knowledge and gaps directly comparable. The picture also shows which assumptions hold up and where evidence is missing.Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable.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
MediumLowMediumLow
Timedifferent
2-8 h30–60 min1-3 h45-90 min
Participantsdifferent
5-124-83-122-8
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsEmpathy Map, Assumptions List, Research GapsKnowledge Map, Critical Knowledge Areas, Transfer PlanAssumption List, Critical Assumptions, Learning Plan
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
SynthesisQualitativeWorkshop
KnowledgeMappingRisk
AssumptionsRiskDecisionDiscovery
Add more methods