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 for OODA Loop.
Decision Making
OODA Loop
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Paper illustration of the McKinsey 7S Framework with seven connected fields
Business Strategy
McKinsey 7S
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.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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.McKinsey 7S checks whether Strategy, Structure, Systems, Shared Values, Skills, Style, and Staff fit together. Organizational misalignments become visible across multiple levers as a result.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
Half day initial, dann laufend15-60 min je Zyklus1-2 h2-4 h
Participantsdifferent
Ein Team plus Stakeholder1-84-123-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Team API DocumentSituation Assessment, Decision Loop, Action UpdatesAlignment Map, Open Issues, Decision Questions7S Assessment, Alignment Gaps, Change Actions
Tagsno overlap
TeamAlignmentCommunicationService
DecisionChangeLearningStrategy
AlignmentStakeholdersStrategyFacilitation
OrganizationStrategyAlignmentChange
Add more methods