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 an IBIS map with issues, positions and arguments
Knowledge Modeling
IBIS
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for DACI
Decision Making
DACI
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.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.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.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
1-2 h1-3 h15-45 min30-60 min
Participantsdifferent
2-82-81-32-10
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeIssue Map, Positions, Argument NotesADR File, Decision Log, RationaleDACI Matrix, Decision Owner, Decision Log
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
RationaleKnowledgeDecision
ArchitectureRationaleDocumentationGovernance
DecisionRolesGovernanceAlignment
Add more methods