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 |  Architecture Architecture Decision Record |  Delivery RAID Log |  UX Research Diary Study |
|---|---|---|---|---|
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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 2-6 h | 15-45 min | 30 min Setup, dann laufend | 1-4 Wochen |
Participantsdifferent | 2-8 | 1-3 | 1-3 maintaining, briefing for everyone | 5-20 |
Formatdifferent | Workshop + async | Async | Async | Async |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | ADR File, Decision Log, Rationale | RAID Log, Status Report Source | Diary Entries, Longitudinal Patterns, Experience Timeline |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | ArchitectureRationaleDocumentationGovernance | RiskTrackingStakeholdersGovernance | UX researchTrackingBehavior |