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 Event Modeling |  Agile Specification by Example |
|---|---|---|---|
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. | Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-3 Wochen | 2-6 h | 60-90 min pro Feature |
Participantsdifferent | 4-12 Beobachtungen | 2-8 | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Event Model, UI Flow, Commands, Read Models | Example Table, Acceptance Tests |
Tagsno overlap | UX researchObservationContext | EventsBlueprintDomain-Driven DesignBehavior | AgileRequirementsExamplesBehavior-Driven Development |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
