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
ChatOps workspace showing the question, observations, and next decision.
DevOps
ChatOps
A paper-based illustration representing Wardley Mapping with its core stages and visible working result.
Systems Thinking
Wardley Mapping
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Purposedifferent
For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together.Wardley Mapping makes visible where an offering stands today and where it can evolve. The method connects user need, value chain, and evolution stages into a strategic basis for platform, build, or buy decisions.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.
Complexitysame
MediumMediumMedium
Timedifferent
Ongoing1-3 h15-60 min je Zyklus
Participantsdifferent
2-202-101-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Chat Transcript, Action Log, AutomationsWardley Map, Strategic Options, Evolution NotesSituation Assessment, Decision Loop, Action Updates
Tagsno overlap
CollaborationEngineeringIncident
StrategySystems thinkingDynamics
DecisionChangeLearningStrategy
Add more methods

Often compared together

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

Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
Paper illustration for Behavior Over Time Graph.
Systems Thinking
Behavior Over Time Graph
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem