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 RAPID
Decision Making
RAPID
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
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 complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels.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.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
LowMediumLowMedium
Timedifferent
Half day initial, dann laufend45-90 min45-90 min2-4 h
Participantsdifferent
Ein Team plus Stakeholder3-123-123-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Team API DocumentRAPID Role Map, Recommendation, Decision LogForce Field Map, Change Levers, Risk Notes7S Assessment, Alignment Gaps, Change Actions
Tagsno overlap
TeamAlignmentCommunicationService
DecisionRolesGovernance
ChangeDecisionStrategy
OrganizationStrategyAlignmentChange
Add more methods