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 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
Paper illustration for RAPID
Decision Making
RAPID
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.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.In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels.
Complexitydifferent
LowLowLowMedium
Timedifferent
1-2 h15-45 min30-60 min45-90 min
Participantsdifferent
2-81-32-103-12
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeADR File, Decision Log, RationaleDACI Matrix, Decision Owner, Decision LogRAPID Role Map, Recommendation, Decision Log
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
ArchitectureRationaleDocumentationGovernance
DecisionRolesGovernanceAlignment
DecisionRolesGovernance
Add more methods