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 Contextual Inquiry | ![]() UX Research Diary Study | ![]() Agile Example Mapping | ![]() Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | When work processes are known only from accounts and the real context stays hidden, Contextual Inquiry makes behavior at the workplace visible. Observation and follow-up questions together show how people actually work, get interrupted, and improvise. | 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 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 | Medium | Low | Medium |
Timedifferent | 1-3 Wochen | 1-4 Wochen | 30-60 min | 60-90 min pro Feature |
Participantsdifferent | 4-12 Beobachtungen | 5-20 | 3-7 | 3-6 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Diary Entries, Longitudinal Patterns, Experience Timeline | Example Map, Acceptance Criteria, Open Questions | Example Table, Acceptance Tests |
Tagsno overlap | UX researchObservationContext | UX researchTrackingBehavior | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsExamplesBehavior-Driven Development |



