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 |  Facilitation Team Charter |  Team Design Team API |
|---|---|---|---|
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 a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. | 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. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-3 Tage | 2-4 h | Half day initial, dann laufend |
Participantsdifferent | Internes Team | 3-12 | Ein Team plus Stakeholder |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | Team Charter, Working Norms, Role Notes | Team API Document |
Tagsno overlap | ResearchCustomerSynthesis | TeamAlignmentCollaboration | TeamAlignmentCommunicationService |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
