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 |  Facilitation Expectation Mapping |  Innovation SCAMPER |  Innovation Brainstorming |
|---|---|---|---|---|
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. | For an existing solution under pressure to change, the method deliberately opens space for systematic variants. It directs attention to rebuilding, combining, and repurposing rather than only new basic ideas. This produces concrete evolution paths for products, offerings, or workflows. | When a team faces an open question with many obvious directions, the method first creates breadth instead of premature commitment. It separates idea flow from evaluation and makes lines of thought visible, creating a pool for selection and further development. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 90-180 min | 45-90 min | 30-60 min | 30-60 min |
Participantsdifferent | 5-15 | 3-12 | 2-10 | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Spotify Model Map, Action List | Expectation Map, Alignment Notes, Agreements | SCAMPER Idea List, Concept Shortlist, Variation Notes | Idea pool, Theme clusters, Shortlist |
Tagsno overlap | TeamOrganizationAlignmentDiagnosis | AlignmentStakeholdersTeam | BrainstormingIdeationCreativityReframingInnovation | BrainstormingIdeationCreativityWorkshopDivergence |