View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Concept Mapping |  UX Research Contextual Inquiry |  Product Discovery Context Canvas |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-2 h | 1-3 Wochen | 45-90 min | 20-40 min pro Story |
Participantsdifferent | 1-8 | 4-12 Beobachtungen | 3-10 | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Field Notes, Workflow Insights, Pain Points | Context canvas, Open questions, Shared context notes | Acceptance Criteria, Story Update |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | UX researchObservationContext | ContextFramingRequirementsCanvas | AgileRequirementsRefinementBehavior-Driven Development |