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 | ![]() Knowledge Modeling Knowledge Mapping | ![]() Agile Acceptance Criteria Workshop | ![]() Knowledge Modeling Concept Mapping |
|---|---|---|---|---|
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. | 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. | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-4 Wochen | 1-3 h | 20-40 min pro Story | 1-2 h |
Participantsdifferent | 5-20 | 3-12 | 3-6 | 1-8 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Acceptance Criteria, Story Update | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | UX researchTrackingBehavior | KnowledgeMappingRisk | AgileRequirementsRefinementBehavior-Driven Development | KnowledgeConceptsMappingSensemaking |



