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