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 Value Stream Mapping | ![]() Decision Making PERT Estimation | ![]() Engineering Kanban |
|---|---|---|---|---|
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 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. | On complex initiatives, a plain average tends to understate just how uncertain the outcome really is. It separates options, evaluation criteria, and open risks. The result is captured as a PERT Estimate, Expected Value, and Risk Notes. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-4 Wochen | 1-3 h | 15-45 min | Ongoing |
Participantsdifferent | 5-20 | 4-10 | 1-8 | 2-12 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Current-state map, Future-state map, Bottleneck list | PERT Estimate, Expected Value, Risk Notes | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | UX researchTrackingBehavior | LeanFlowWasteDelivery | EstimationUncertaintyRisk | FlowVisual managementDelivery |



