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 of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration of Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Purposedifferent
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 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 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.
Complexitydifferent
LowMediumLow
Timedifferent
15-45 min90-180 min20-40 min initial, dann laufend
Participantsdifferent
1-34-123-15
Formatdifferent
AsyncWorkshopWorkshop + async
Outputdifferent
ADR File, Decision Log, RationaleDecision Rights Matrix, AgreementROAM Board, Owner List
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
DecisionGovernanceAlignmentResponsibility
RiskAgileTrackingAlignment
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments