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
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Paper illustration of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
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.For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch.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.
Complexitydifferent
LowMediumLow
Timedifferent
1-2 h30-90 min60-90 min
Participantsdifferent
2-81-64-10
Formatdifferent
WorkshopWorkshop + asyncWorkshop
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeDecision Tree, Option Map, Assumption ListProblem Cluster, Prioritized Challenge, Experiment
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
DecisionTreeOptions
FacilitationDecisionProblem solvingWorkshop
Add more methods

Often compared together

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

Paper matrix with six colored hat cards for information, feeling, value, caution, ideas and process control.
Facilitation
Six Thinking Hats
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
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