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
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Purposedifferent
arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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.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
LowMediumMediumLow
Timedifferent
1-2 Tage15-60 min je Zyklus1-3 h45-90 min
Participantsdifferent
1-41-81-83-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewSituation Assessment, Decision Loop, Action UpdatesArgument Map, Evidence Gaps, Decision RationaleForce Field Map, Change Levers, Risk Notes
Tagsno overlap
ArchitectureDocumentationCommunication
DecisionChangeLearningStrategy
SensemakingDecisionRationale
ChangeDecisionStrategy
Add more methods