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 |  Operations Failure Mode and Effects Analysis |  Agile Example Mapping |  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. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. | 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 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 | High | Low | Medium |
Timedifferent | 1-4 Wochen | 2-6 h | 30-60 min | 60-90 min pro Feature |
Participantsdifferent | 5-20 | 3-10 | 3-7 | 3-6 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | FMEA Table, Risk Priority, Mitigation Actions | Example Map, Acceptance Criteria, Open Questions | Example Table, Acceptance Tests |
Tagsno overlap | UX researchTrackingBehavior | RiskQualityOperationsRoot cause | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsExamplesBehavior-Driven Development |