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 |  Agile Example Mapping |  Operations 5 Whys |  Agile Specification by Example |
|---|---|---|---|---|
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 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. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 Tage | 30-60 min | 15-30 min | 60-90 min pro Feature |
Participantsdifferent | Internes Team | 3-7 | 2-6 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | Example Map, Acceptance Criteria, Open Questions | Root cause notes, Countermeasures | Example Table, Acceptance Tests |
Tagsno overlap | ResearchCustomerSynthesis | Behavior-Driven DevelopmentRequirementsExamplesRefinement | Root causeIncidentLeanProblem solving | AgileRequirementsExamplesBehavior-Driven Development |