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 Diary Study |  Agile Example Mapping |  Agile Planning Poker |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | When experiences build up over days or weeks and a single session cannot capture them, Diary Study records the course of everyday life. Recurring triggers, moods, and habits become visible this way, beyond the sharpness of memory. | 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 estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. | 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-4 Wochen | 30-60 min | 2-5 min je Item | 60-90 min pro Feature |
Participantsdifferent | 5-20 | 3-7 | 3-9 | 3-6 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Example Map, Acceptance Criteria, Open Questions | Relative Estimates, Assumption Notes, Split Candidates | Example Table, Acceptance Tests |
Tagsno overlap | UX researchTrackingBehavior | Behavior-Driven DevelopmentRequirementsExamplesRefinement | EstimationAgileRelative sizingTeam | AgileRequirementsExamplesBehavior-Driven Development |