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 for Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration of Team API with its method-specific working model.
Team Design
Team API
A paper-based illustration representing North Star Metric with its core stages and visible working result.
Growth
North Star Metric
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
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.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 product teams track many metrics, the view of the actual customer outcome easily gets lost. A North Star Metric bundles growth, usage, and value contribution into one signal that makes the system's direction visible.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.
Complexitydifferent
LowLowMediumMedium
Timedifferent
45-90 minHalf day initial, dann laufend1-2 h1-2 h
Participantsdifferent
3-12Ein Team plus Stakeholder3-84-12
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Expectation Map, Alignment Notes, AgreementsTeam API DocumentNorth Star metric, Input metric tree, Measurement cadenceAlignment Map, Open Issues, Decision Questions
Tags1 shared
AlignmentStakeholdersTeam
TeamAlignmentCommunicationService
GrowthMetricsAlignmentRetention
AlignmentStakeholdersStrategyFacilitation
Add more methods