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 | ![]() Delivery Communication Plan | ![]() Product Strategy Impact 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 many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. | When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-4 Wochen | Ongoing | 45-90 min | 45-90 min |
Participantsdifferent | 5-20 | 2-12 | 2-6 | 3-8 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Kanban board, WIP policies, Flow metrics | Communication Plan, Channel Matrix, Message Cadence | Impact Map, Outcome Hypotheses, Delivery Options |
Tagsno overlap | UX researchTrackingBehavior | FlowVisual managementDelivery | CommunicationStakeholdersDeliveryPlanning | OutcomesStrategyBehaviorPlanning |



