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 |  UX Research Contextual Inquiry |  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. | When work processes are known only from accounts and the real context stays hidden, Contextual Inquiry makes behavior at the workplace visible. Observation and follow-up questions together show how people actually work, get interrupted, and improvise. | 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 Wochen | 1-3 Wochen vom Draft bis zur Entscheidung | 30 min Setup, dann laufend |
Participantsdifferent | 5-20 | 4-12 Beobachtungen | 3-20 Reviewer | 1-3 maintaining, briefing for everyone |
Formatdifferent | Async | Workshop + async | Async | Async |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Field Notes, Workflow Insights, Pain Points | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | RAID Log, Status Report Source |
Tagsno overlap | UX researchTrackingBehavior | UX researchObservationContext | ArchitectureDecisionAsyncGovernance | RiskTrackingStakeholdersGovernance |