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 Lotus Blossom |  Innovation Reverse 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. | 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. | For persistent errors or blockages, the method shifts the view to the opposite of the desired effect. It exposes the mechanics of failure and makes hidden causes easier to grasp. This makes improvement more concrete and the problem clearer. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 90-180 min | 45-90 min | 45-90 min | 30-60 min |
Participantsdifferent | 5-15 | 3-12 | 3-10 | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Spotify Model Map, Action List | Expectation Map, Alignment Notes, Agreements | Lotus Diagram, Idea Themes, Shortlist | Reverse Ideas, Risk Themes, Solution Ideas |
Tagsno overlap | TeamOrganizationAlignmentDiagnosis | AlignmentStakeholdersTeam | BrainstormingIdeationCreativityDivergenceWorkshop | BrainstormingIdeationCreativityRisk |