View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Diary StudySpecification by ExampleFailure Mode and Effects AnalysisAcceptance Criteria Workshop
| Criterion |  UX Research Diary Study |  Agile Specification by Example |  Operations Failure Mode and Effects Analysis |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
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 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. | 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 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. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | 1-4 Wochen | 60-90 min pro Feature | 2-6 h | 20-40 min pro Story |
Participantsdifferent | 5-20 | 3-6 | 3-10 | 3-6 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Example Table, Acceptance Tests | FMEA Table, Risk Priority, Mitigation Actions | Acceptance Criteria, Story Update |
Tagsno overlap | UX researchTrackingBehavior | AgileRequirementsExamplesBehavior-Driven Development | RiskQualityOperationsRoot cause | AgileRequirementsRefinementBehavior-Driven Development |