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 Request for Comments |  Product Discovery Assumption Mapping |  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. | 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. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | 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 vom Draft bis zur Entscheidung | 45-60 min | 30 min Setup, dann laufend |
Participantsdifferent | 5-20 | 3-20 Reviewer | 2-8 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Async | Async | Workshop + async | Async |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Assumption map, Test backlog, Risk ranking | RAID Log, Status Report Source |
Tagsno overlap | UX researchTrackingBehavior | ArchitectureDecisionAsyncGovernance | AssumptionsRiskExperimentsValidation | RiskTrackingStakeholdersGovernance |