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 for Change Analysis.
Operations
Change Analysis
Paper illustration of a branching impact map with a Why goal at the root, actor circles, How behavior changes and What options.
Product Strategy
Impact Mapping
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.For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise.When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures.
Complexitydifferent
LowMediumMedium
Timedifferent
15-45 min45-120 min45-90 min
Participantsdifferent
1-32-63-8
Formatdifferent
AsyncWorkshop + asyncWorkshop
Outputdifferent
ADR File, Decision Log, RationaleChange Matrix, Cause Hypotheses, Validation Questions, Action ListImpact Map, Outcome Hypotheses, Delivery Options
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
ChangeRoot causeTroubleshootingComparison
OutcomesStrategyBehaviorPlanning
Add more methods

Often compared together

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

Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis