View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Example Mapping |  UX Research User Interviews |  Agile Specification by Example |  UX Research Personas |
|---|---|---|---|---|
Purposedifferent | 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 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 business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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 | Medium | Medium |
Timedifferent | 30-60 min | 30–60 min per interview | 60-90 min pro Feature | 1-3 Tage |
Participantsdifferent | 3-7 | 1 participant per interview | 3-6 | Internes Team |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Interview Notes, Themes, Insight Summary | Example Table, Acceptance Tests | Persona Profiles, Needs Summary, Scenario Notes |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | QualitativeResearchCustomerDiscovery | AgileRequirementsExamplesBehavior-Driven Development | ResearchCustomerSynthesis |