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 illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
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.In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving.
Complexitydifferent
LowMediumLow
Timedifferent
15-45 min90-180 min45-90 min
Participantsdifferent
1-34-123-12
Formatdifferent
AsyncWorkshopWorkshop
Outputdifferent
ADR File, Decision Log, RationaleDecision Rights Matrix, AgreementForce Field Map, Change Levers, Risk Notes
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
DecisionGovernanceAlignmentResponsibility
ChangeDecisionStrategy
Add more methods

Often compared together

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

Paper illustration of the McKinsey 7S Framework with seven connected fields
Business Strategy
McKinsey 7S
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments