View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Team Design Spotify Model Mapping |  Growth Funnel Analysis |  Product Discovery Assumption Mapping |
|---|---|---|---|
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 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 90-180 min | 1-3 h | 45-60 min |
Participantsdifferent | 5-15 | 1-5 | 2-8 |
Formatdifferent | Workshop | Async | Workshop + async |
Outputdifferent | Spotify Model Map, Action List | Funnel report, Drop-off analysis, Optimization hypotheses | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | TeamOrganizationAlignmentDiagnosis | AnalyticsConversionGrowth | AssumptionsRiskExperimentsValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
