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 for OODA Loop.
Decision Making
OODA Loop
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Purposedifferent
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.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer.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
MediumLowLowLow
Timedifferent
15-60 min je Zyklus1-2 h60-90 min45-90 min
Participantsdifferent
1-83-104-103-12
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Situation Assessment, Decision Loop, Action UpdatesArchitecture Canvas, Goals, Constraints, Quality AttributesProblem Cluster, Prioritized Challenge, ExperimentForce Field Map, Change Levers, Risk Notes
Tagsno overlap
DecisionChangeLearningStrategy
CanvasArchitectureAlignmentWorkshop
FacilitationDecisionProblem solvingWorkshop
ChangeDecisionStrategy
Add more methods