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 |  UX Research Diary Study |  Architecture C4 Model |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | 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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 2-6 h | 1-4 Wochen | 1-4 h | 15-45 min |
Participantsdifferent | 2-8 | 5-20 | 1-5 | 1-3 |
Formatdifferent | Workshop + async | Async | Workshop + async | Async |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | Diary Entries, Longitudinal Patterns, Experience Timeline | Context Diagram, Container Diagram, Component Diagram | ADR File, Decision Log, Rationale |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | UX researchTrackingBehavior | ArchitectureCommunicationVisualization | ArchitectureRationaleDocumentationGovernance |