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 RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List.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.
Complexitysame
LowLowLowLow
Timedifferent
1-2 h30 min Setup, dann laufend20-40 min initial, dann laufend30-60 min
Participantsdifferent
2-81-3 maintaining, briefing for everyone3-152-10
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeRAID Log, Status Report SourceROAM Board, Owner ListDACI Matrix, Decision Owner, Decision Log
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
RiskTrackingStakeholdersGovernance
RiskAgileTrackingAlignment
DecisionRolesGovernanceAlignment
Add more methods