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 Spotify Model Mapping with its method-specific working model.
Team Design
Spotify Model Mapping
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Funnel Analysis workspace showing the question, observations, and next decision.
Growth
Funnel Analysis
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
When a team landscape has grown without clear grouping, it maps roles and relationships onto the Spotify model. It clarifies responsibility, interaction, and load between teams. The result is captured as a Spotify model map and action list.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 many visitors or users drop off along the way, the reason behind the number often stays hidden. Funnel Analysis exposes these transitions and makes visible exactly where the path collapses.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.
Complexitydifferent
MediumLowMediumHigh
Timedifferent
90-180 min45-90 min1-3 h1-4 Wochen
Participantsdifferent
5-153-121-51-6
Formatdifferent
WorkshopWorkshopAsyncAsync
Outputdifferent
Spotify Model Map, Action ListExpectation Map, Alignment Notes, AgreementsFunnel report, Drop-off analysis, Optimization hypothesesExperiment results, Decision log, Learning summary
Tagsno overlap
TeamOrganizationAlignmentDiagnosis
AlignmentStakeholdersTeam
AnalyticsConversionGrowth
ExperimentsGrowthAnalyticsValidation
Add more methods