View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Event Modeling |  Delivery RAID Log |  UX Research Diary Study |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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 stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 2-6 h | 30 min Setup, dann laufend | 1-4 Wochen | 60-90 min |
Participantsdifferent | 2-8 | 1-3 maintaining, briefing for everyone | 5-20 | 3-6 |
Formatdifferent | Workshop + async | Async | Async | Workshop |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | RAID Log, Status Report Source | Diary Entries, Longitudinal Patterns, Experience Timeline | Salience Diagram, Strategy per Class |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | RiskTrackingStakeholdersGovernance | UX researchTrackingBehavior | StakeholdersFacilitationAlignmentGovernance |