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 for Argument Mapping
Decision Making
Argument Mapping
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration of an IBIS map with issues, positions and arguments
Knowledge Modeling
IBIS
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.When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus.
Complexitydifferent
LowMediumLowMedium
Timedifferent
1-2 h1-3 h15-30 min1-3 h
Participantsdifferent
2-81-82-62-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeArgument Map, Evidence Gaps, Decision RationaleRoot cause notes, CountermeasuresIssue Map, Positions, Argument Notes
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
SensemakingDecisionRationale
Root causeIncidentLeanProblem solving
RationaleKnowledgeDecision
Add more methods