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 |  UX Research HEART Framework |  Engineering Goal Question Metric |  UX Research Diary Study |
|---|---|---|---|---|
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. | Helps clarify observations, needs, and patterns in concrete terms. It groups observations into patterns, questions, and decisions. The result is captured as a HEART-GSM table and dashboard. | Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 2-6 h | 120 min initial, dann laufend | 90-180 min | 1-4 Wochen |
Participantsdifferent | 2-8 | 3-6 | 3-6 | 5-20 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Async |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | HEART-GSM Table, Dashboard | GQM Table, Metric Profiles | Diary Entries, Longitudinal Patterns, Experience Timeline |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | MetricsUX researchMeasurementSatisfaction | MetricsMeasurementEngineeringAlignment | UX researchTrackingBehavior |