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 the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration for Change Analysis.
Operations
Change Analysis
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
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.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.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.
Complexitydifferent
LowMediumLow
Timedifferent
45-90 min45-120 min15-45 min
Participantsdifferent
3-122-61-3
Formatdifferent
WorkshopWorkshop + asyncAsync
Outputdifferent
Force Field Map, Change Levers, Risk NotesChange Matrix, Cause Hypotheses, Validation Questions, Action ListADR File, Decision Log, Rationale
Tagsno overlap
ChangeDecisionStrategy
ChangeRoot causeTroubleshootingComparison
ArchitectureRationaleDocumentationGovernance
Add more methods

Often compared together

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

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
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)