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 | ![]() Product Discovery Context Canvas | ![]() Knowledge Modeling Knowledge 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. | When an environment of users, systems, and constraints is hard to grasp, it puts the context compactly on the table. It creates a clear reading of influence, boundary, and dependency. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | 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 | 45-90 min | 1-3 h | 30 min Setup, dann laufend |
Participantsdifferent | 5-20 | 3-10 | 3-12 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Async | Workshop | Workshop | Async |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Context canvas, Open questions, Shared context notes | Knowledge Map, Critical Knowledge Areas, Transfer Plan | RAID Log, Status Report Source |
Tagsno overlap | UX researchTrackingBehavior | ContextFramingRequirementsCanvas | KnowledgeMappingRisk | RiskTrackingStakeholdersGovernance |



