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 Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
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.In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement.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.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
LowMediumMediumLow
Timedifferent
1-2 h90-180 min1-3 h15-45 min
Participantsdifferent
2-84-121-81-3
Formatdifferent
WorkshopWorkshopWorkshop + asyncAsync
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeDecision Rights Matrix, AgreementArgument Map, Evidence Gaps, Decision RationaleADR File, Decision Log, Rationale
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
DecisionGovernanceAlignmentResponsibility
SensemakingDecisionRationale
ArchitectureRationaleDocumentationGovernance
Add more methods