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 Contextual Inquiry | ![]() Knowledge Modeling Competency Questions | ![]() Agile Example Mapping | ![]() Product Discovery Context Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | Competency Questions translate a domain model into concrete questions that it must be able to answer. The method keeps the model's scope clean and prevents pretty but useless structures. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 Wochen | 2-4 h | 30-60 min | 45-90 min |
Participantsdifferent | 4-12 Beobachtungen | 2-8 | 3-7 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Example Map, Acceptance Criteria, Open Questions | Context canvas, Open questions, Shared context notes |
Tagsno overlap | UX researchObservationContext | OntologyKnowledge graphScopeRequirementsSemantic | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ContextFramingRequirementsCanvas |



