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 Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration of a two-by-two Ansoff Matrix with four growth directions
Business Strategy
Ansoff Matrix
Paper illustration of KPI Tree with its method-specific working model.
Product Strategy
KPI Tree
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.When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.The Ansoff Matrix organizes growth options by market and product relation. It helps weigh expansion, diversification, and adaptation cleanly against each other.When metrics across the organization drift apart, it arranges drivers and effects under one shared logic. It connects customer value, product logic, and decision priorities. The result is captured as a KPI tree and owner list.
Complexitydifferent
LowLowLowMedium
Timedifferent
Half day initial, dann laufend45-90 min45-90 min90-180 min initial, dann laufend
Participantsdifferent
Ein Team plus Stakeholder3-122-83-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Team API DocumentExpectation Map, Alignment Notes, AgreementsAnsoff Matrix, Growth Options, Risk NotesKPI Tree, Owner List
Tagsno overlap
TeamAlignmentCommunicationService
AlignmentStakeholdersTeam
GrowthStrategyMarketPortfolio
MetricsStrategyAlignmentMeasurement
Add more methods