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 |  Architecture C4 Model |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-4 Wochen | 2-6 h | 1-4 h | 60-120 min |
Participantsdifferent | 5-20 | 2-8 | 1-5 | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Event Model, UI Flow, Commands, Read Models | Context Diagram, Container Diagram, Component Diagram | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | UX researchTrackingBehavior | EventsBlueprintDomain-Driven DesignBehavior | ArchitectureCommunicationVisualization | ArchitectureCommunicationStakeholdersCanvas |