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 Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
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 a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie.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.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
1-2 h1-3 h1-3 h1-4 h
Participantsdifferent
2-82-81-83-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeCause Tree, Evidence Notes, CountermeasuresArgument Map, Evidence Gaps, Decision RationaleProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
Root causeTreeIncidentQuality
SensemakingDecisionRationale
Root causeProblem solvingQualityIncident
Add more methods