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 of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
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.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 dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia.When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.
Complexitydifferent
LowLowMediumMedium
Timedifferent
45-90 min15-45 min15-60 min je Zyklus1-3 h
Participantsdifferent
3-121-31-81-8
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Force Field Map, Change Levers, Risk NotesADR File, Decision Log, RationaleSituation Assessment, Decision Loop, Action UpdatesArgument Map, Evidence Gaps, Decision Rationale
Tagsno overlap
ChangeDecisionStrategy
ArchitectureRationaleDocumentationGovernance
DecisionChangeLearningStrategy
SensemakingDecisionRationale
Add more methods