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 | ![]() Knowledge Modeling Event Modeling | ![]() Decision Making Force Field Analysis | ![]() Product Strategy DIBB |
|---|---|---|---|---|
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. | Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-4 Wochen | 2-6 h | 45-90 min | 1-2 h |
Participantsdifferent | 5-20 | 2-8 | 3-12 | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Event Model, UI Flow, Commands, Read Models | Force Field Map, Change Levers, Risk Notes | DIBB document, Belief list, Bet list, Learning report |
Tagsno overlap | UX researchTrackingBehavior | EventsBlueprintDomain-Driven DesignBehavior | ChangeDecisionStrategy | StrategyDecisionAssumptionsHypothesis |



