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
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
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Purposedifferent
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.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.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.
Complexitysame
LowLowLowLow
Timedifferent
30-60 min15-45 min20-40 min initial, dann laufend30 min Setup, dann laufend
Participantsdifferent
2-101-33-151-3 maintaining, briefing for everyone
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncAsync
Outputdifferent
DACI Matrix, Decision Owner, Decision LogADR File, Decision Log, RationaleROAM Board, Owner ListRAID Log, Status Report Source
Tagsno overlap
DecisionRolesGovernanceAlignment
ArchitectureRationaleDocumentationGovernance
RiskAgileTrackingAlignment
RiskTrackingStakeholdersGovernance
Add more methods