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 |  Engineering Kanban |  Agile NoEstimates |  Delivery Value Stream 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 work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. | 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 delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-4 Wochen | Ongoing | laufend | 1-3 h |
Participantsdifferent | 5-20 | 2-12 | 2-12 | 4-10 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Kanban board, WIP policies, Flow metrics | Throughput Data, Flow Forecast, Slicing Rules | Current-state map, Future-state map, Bottleneck list |
Tagsno overlap | UX researchTrackingBehavior | FlowVisual managementDelivery | EstimationForecastingFlow | LeanFlowWasteDelivery |