View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Facilitation Expectation Mapping | ![]() Team Design Spotify Model Mapping | ![]() Innovation Brainstorming | ![]() Innovation Lotus Blossom |
|---|---|---|---|---|
Purposedifferent | 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 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 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. | When a central question feels too large, the method breaks it into neighboring topic fields with their own depth of ideation. It holds structure and openness at the same time, so adjacent perspectives don't get lost. This grows an idea space out of a core problem. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45-90 min | 90-180 min | 30-60 min | 45-90 min |
Participantsdifferent | 3-12 | 5-15 | 4-12 | 3-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Spotify Model Map, Action List | Idea pool, Theme clusters, Shortlist | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | AlignmentStakeholdersTeam | TeamOrganizationAlignmentDiagnosis | BrainstormingIdeationCreativityWorkshopDivergence | BrainstormingIdeationCreativityDivergenceWorkshop |



