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
Paper illustration for DACI
Decision Making
DACI
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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.In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.
Complexitydifferent
LowMediumLowLow
Timedifferent
1-2 h1-3 h30-60 min15-45 min
Participantsdifferent
2-81-82-101-3
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeArgument Map, Evidence Gaps, Decision RationaleDACI Matrix, Decision Owner, Decision LogADR File, Decision Log, Rationale
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
SensemakingDecisionRationale
DecisionRolesGovernanceAlignment
ArchitectureRationaleDocumentationGovernance
Add more methods