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 User Interviews |  Agile Example Mapping |  Agile Acceptance Criteria Workshop |  UX Research Personas |
|---|---|---|---|---|
Purposedifferent | When teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 30–60 min per interview | 30-60 min | 20-40 min pro Story | 1-3 Tage |
Participantsdifferent | 1 participant per interview | 3-7 | 3-6 | Internes Team |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Interview Notes, Themes, Insight Summary | Example Map, Acceptance Criteria, Open Questions | Acceptance Criteria, Story Update | Persona Profiles, Needs Summary, Scenario Notes |
Tagsno overlap | QualitativeResearchCustomerDiscovery | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsRefinementBehavior-Driven Development | ResearchCustomerSynthesis |