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 | ![]() Operations Root Cause Tree Analysis | ![]() Operations Barrier Analysis |
|---|---|---|---|---|
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. | For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie. | For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-4 Wochen | Ongoing | 1-3 h | 2-4 h |
Participantsdifferent | 5-20 | 2-12 | 2-8 | 2-6 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Kanban board, WIP policies, Flow metrics | Cause Tree, Evidence Notes, Countermeasures | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tagsno overlap | UX researchTrackingBehavior | FlowVisual managementDelivery | Root causeTreeIncidentQuality | Root causeSafetyIncident |



