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
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
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
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration of DIBB with its method-specific working model.
Product Strategy
DIBB
Purposedifferent
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.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.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.DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report.
Complexitydifferent
MediumMediumLowLow
Timedifferent
1-3 h2-8 h45-90 min1-2 h
Participantsdifferent
3-125-122-82-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Knowledge Map, Critical Knowledge Areas, Transfer PlanEvent Timeline, Ubiquitous Language, Boundaries, Open QuestionsAssumption List, Critical Assumptions, Learning PlanDIBB document, Belief list, Bet list, Learning report
Tagsno overlap
KnowledgeMappingRisk
Domain-Driven DesignEventsDiscoveryWorkshop
AssumptionsRiskDecisionDiscovery
StrategyDecisionAssumptionsHypothesis
Add more methods