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 |  Facilitation Expectation Mapping |  Team Design Team Topologies Interaction Modes |  Team Design Spotify Model 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 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 several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 4-8 h, mehrere Iterationen | 45-90 min | Half day | 90-180 min |
Participantsdifferent | 2-6 | 3-12 | Team-Leads plus Architecture | 5-15 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Future Press Release, FAQ, Vision Statement | Expectation Map, Alignment Notes, Agreements | Interaction Heat Map, Agreements per Pair | Spotify Model Map, Action List |
Tags1 shared | VisionNarrativeAlignment | AlignmentStakeholdersTeam | TeamAlignmentCollaborationOrganization | TeamOrganizationAlignmentDiagnosis |