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 a two-by-two Ansoff Matrix with four growth directions
Business Strategy
Ansoff Matrix
Stakeholder Mapping
Facilitation
Stakeholder Mapping
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.The Ansoff Matrix organizes growth options by market and product relation. It helps weigh expansion, diversification, and adaptation cleanly against each other.When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first.
Complexitysame
LowLowLow
Timedifferent
Half day initial, dann laufend45-90 min60–90 min
Participantsdifferent
Ein Team plus Stakeholder2-82-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Team API DocumentAnsoff Matrix, Growth Options, Risk NotesStakeholder Map, Engagement Plan, Risk Notes
Tagsno overlap
TeamAlignmentCommunicationService
GrowthStrategyMarketPortfolio
StakeholdersAlignmentFacilitationChange
Add more methods

Often compared together

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

Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration of the McKinsey 7S Framework with seven connected fields
Business Strategy
McKinsey 7S
Paper illustration of Power-Interest Grid with a method-specific labelled workspace.
Facilitation
Power Interest Grid