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
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
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 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 demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all.
Complexitydifferent
MediumLowHighLow
Timedifferent
90-180 min45-90 min1-4 Wochen1-5 Tage
Participantsdifferent
5-153-121-6Nutzertraffic
Formatdifferent
WorkshopWorkshopAsyncAsync
Outputdifferent
Spotify Model Map, Action ListExpectation Map, Alignment Notes, AgreementsExperiment results, Decision log, Learning summaryInterest Metrics, Conversion Signal, Learning Note
Tagsno overlap
TeamOrganizationAlignmentDiagnosis
AlignmentStakeholdersTeam
ExperimentsGrowthAnalyticsValidation
ValidationExperimentsDemandGrowth
Add more methods