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 Three Amigos | ![]() Delivery RAID Log | ![]() Agile Example Mapping |
|---|---|---|---|---|
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 story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-4 Wochen | 15-30 min | 30 min Setup, dann laufend | 30-60 min |
Participantsdifferent | 5-20 | 3 | 1-3 maintaining, briefing for everyone | 3-7 |
Formatdifferent | Async | Workshop + async | Async | Workshop |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Clarified Story, Test Examples, Open Questions | RAID Log, Status Report Source | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | UX researchTrackingBehavior | CollaborationBehavior-Driven DevelopmentQualityRefinement | RiskTrackingStakeholdersGovernance | Behavior-Driven DevelopmentRequirementsExamplesRefinement |



