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 Event Modeling |  Agile Example Mapping |  UX Research Diary Study |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | 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 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 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. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 2-6 h | 30-60 min | 1-4 Wochen | 60-90 min pro Feature |
Participantsdifferent | 2-8 | 3-7 | 5-20 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | Example Map, Acceptance Criteria, Open Questions | Diary Entries, Longitudinal Patterns, Experience Timeline | Example Table, Acceptance Tests |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | Behavior-Driven DevelopmentRequirementsExamplesRefinement | UX researchTrackingBehavior | AgileRequirementsExamplesBehavior-Driven Development |