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 Flywheel.
Growth
Flywheel
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
A paper-based illustration representing North Star Metric with its core stages and visible working result.
Growth
North Star Metric
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.Growth often breaks down where a reinforcing mechanism builds up too much friction. A Flywheel shows the cycle of value, repetition, and reinforcement meant to sustain growth.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.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.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
Half day initial, dann laufend60-120 min1-2 h1-2 h
Participantsdifferent
Ein Team plus Stakeholder3-84-123-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Team API DocumentFlywheel Map, Friction Points, Growth Levers, Experiment BacklogAlignment Map, Open Issues, Decision QuestionsNorth Star metric, Input metric tree, Measurement cadence
Tagsno overlap
TeamAlignmentCommunicationService
GrowthRetentionConversion
AlignmentStakeholdersStrategyFacilitation
GrowthMetricsAlignmentRetention
Add more methods