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 |  Architecture C4 Model |  Facilitation Stakeholder Salience Model |  Delivery RAID Log |
|---|---|---|---|---|
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. | 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. | 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. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-4 Wochen | 1-4 h | 60-90 min | 30 min Setup, dann laufend |
Participantsdifferent | 5-20 | 1-5 | 3-6 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Async | Workshop + async | Workshop | Async |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Context Diagram, Container Diagram, Component Diagram | Salience Diagram, Strategy per Class | RAID Log, Status Report Source |
Tagsno overlap | UX researchTrackingBehavior | ArchitectureCommunicationVisualization | StakeholdersFacilitationAlignmentGovernance | RiskTrackingStakeholdersGovernance |