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 Contextual Inquiry | ![]() UX Research Diary Study | ![]() Architecture Request for Comments |
|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-3 Wochen | 1-4 Wochen | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 4-12 Beobachtungen | 5-20 | 3-20 Reviewer |
Formatdifferent | Workshop + async | Async | Async |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Diary Entries, Longitudinal Patterns, Experience Timeline | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | UX researchObservationContext | UX researchTrackingBehavior | ArchitectureDecisionAsyncGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






