View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Working Backwards |  UX Design Design Studio |  Team Design Spotify Model Mapping |  Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | When the target state and benefit need to be clear first, it thinks backward from the desired outcome into the product logic. It sharpens vision, objections, and value proposition before elaboration. | When several designs need to be quickly put in relation to each other, it makes ideas visible and comparable. It encourages early variants instead of long upfront debates. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 4-8 h, mehrere Iterationen | 1-3 h | 90-180 min | 45-90 min |
Participantsdifferent | 2-6 | 3-8 | 5-15 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Future Press Release, FAQ, Vision Statement | Sketches, Concept Directions, Design Decisions | Spotify Model Map, Action List | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | VisionNarrativeAlignment | SketchingCollaborationIdeation | TeamOrganizationAlignmentDiagnosis | AlignmentStakeholdersTeam |