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
A paper-based illustration representing Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
Paper illustration of DIBB with its method-specific working model.
Product Strategy
DIBB
Paper illustration of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Purposedifferent
Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected.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.When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer.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.
Complexitydifferent
LowLowLowMedium
Timedifferent
1-2 h1-2 h60-90 min1-3 h
Participantsdifferent
2-82-84-102-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeDIBB document, Belief list, Bet list, Learning reportProblem Cluster, Prioritized Challenge, ExperimentContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
StrategyDecisionAssumptionsHypothesis
FacilitationDecisionProblem solvingWorkshop
Domain-Driven DesignBoundariesStrategy
Add more methods