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 HEART Framework | ![]() Domain Modeling EventStorming | ![]() UX Research Diary Study | ![]() Product Strategy Counter Metrics |
|---|---|---|---|---|
Purposedifferent | 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. | When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views. | 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 a headline metric could mask side effects, it adds guardrail signals against unwanted outcomes. It connects customer value, product logic, and decision priorities. The result is captured as a counter-metric list and guardrail definitions. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 120 min initial, dann laufend | 2-8 h | 1-4 Wochen | 30-60 min |
Participantsdifferent | 3-6 | 5-12 | 5-20 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | HEART-GSM Table, Dashboard | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Diary Entries, Longitudinal Patterns, Experience Timeline | Counter Metric List, Guardrail Definitions |
Tagsno overlap | MetricsUX researchMeasurementSatisfaction | Domain-Driven DesignEventsDiscoveryWorkshop | UX researchTrackingBehavior | MetricsMeasurementStrategyExperiments |



