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 NoEstimates |  Facilitation Dot Estimation |
|---|---|---|---|---|
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 estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules. | When size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-4 Wochen | 30 min Setup, dann laufend | laufend | 5-20 min |
Participantsdifferent | 5-20 | 1-3 maintaining, briefing for everyone | 2-12 | 3-20 |
Formatdifferent | Async | Async | Workshop + async | Workshop |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | RAID Log, Status Report Source | Throughput Data, Flow Forecast, Slicing Rules | Effort Heatmap, Risk Signals, Discussion Targets |
Tagsno overlap | UX researchTrackingBehavior | RiskTrackingStakeholdersGovernance | EstimationForecastingFlow | EstimationEffortRisk |