View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research Personas |  Team Design Team API |  Team Design Spotify Model Mapping |
|---|---|---|---|
Purposedifferent | When target groups stay too vague and teams talk about the same people differently, personas create a shared, solid picture of usage. Condensed profiles make needs, contexts, and differences tangible enough for decisions. | When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document. | 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 |
Timedifferent | 1-3 Tage | Half day initial, dann laufend | 90-180 min |
Participantsdifferent | Internes Team | Ein Team plus Stakeholder | 5-15 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | Team API Document | Spotify Model Map, Action List |
Tagsno overlap | ResearchCustomerSynthesis | TeamAlignmentCommunicationService | TeamOrganizationAlignmentDiagnosis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
