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 Flywheel.
Growth
Flywheel
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
A paper-based illustration representing North Star Metric with its core stages and visible working result.
Growth
North Star Metric
Purposedifferent
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 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 two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.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
MediumLowHighMedium
Timedifferent
60-120 min45-90 min1-4 Wochen1-2 h
Participantsdifferent
3-83-121-63-8
Formatdifferent
WorkshopWorkshopAsyncWorkshop + async
Outputdifferent
Flywheel Map, Friction Points, Growth Levers, Experiment BacklogExpectation Map, Alignment Notes, AgreementsExperiment results, Decision log, Learning summaryNorth Star metric, Input metric tree, Measurement cadence
Tagsno overlap
GrowthRetentionConversion
AlignmentStakeholdersTeam
ExperimentsGrowthAnalyticsValidation
GrowthMetricsAlignmentRetention
Add more methods