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 |  Delivery RAID Log |  Agile Ideal Days |  Agile Planning Poker |
|---|---|---|---|---|
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. | 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 effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats. | When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-4 Wochen | 30 min Setup, dann laufend | 15-60 min | 2-5 min je Item |
Participantsdifferent | 5-20 | 1-3 maintaining, briefing for everyone | 2-9 | 3-9 |
Formatdifferent | Async | Async | Workshop + async | Workshop + async |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | RAID Log, Status Report Source | Ideal Day Estimates, Assumption Notes, Capacity Caveats | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | UX researchTrackingBehavior | RiskTrackingStakeholdersGovernance | EstimationEffortAgile | EstimationAgileRelative sizingTeam |