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 Team API with its method-specific working model.
Team Design
Team API
Paper illustration of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
Paper illustration for DACI
Decision Making
DACI
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Purposedifferent
When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document.Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy.In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated.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.
Complexitydifferent
LowHighLowMedium
Timedifferent
Half day initial, dann laufendHalf day30-60 min15-60 min je Zyklus
Participantsdifferent
Ein Team plus Stakeholder3-122-101-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Team API DocumentLeverage Map, Action StrategyDACI Matrix, Decision Owner, Decision LogSituation Assessment, Decision Loop, Action Updates
Tagsno overlap
TeamAlignmentCommunicationService
Systems thinkingChangeStrategy
DecisionRolesGovernanceAlignment
DecisionChangeLearningStrategy
Add more methods