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 Views and Beyond |  Architecture Request for Comments |  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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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 | Medium | Medium | Low |
Timedifferent | 1-4 Wochen | 1-3 Tage | 1-3 Wochen vom Draft bis zur Entscheidung | 30 min Setup, dann laufend |
Participantsdifferent | 5-20 | 1-4 | 3-20 Reviewer | 1-3 maintaining, briefing for everyone |
Formatdifferent | Async | Workshop + async | Async | Async |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Architecture Views, Cross-view Notes, Rationale | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | RAID Log, Status Report Source |
Tagsno overlap | UX researchTrackingBehavior | DocumentationStakeholdersArchitecture | ArchitectureDecisionAsyncGovernance | RiskTrackingStakeholdersGovernance |