methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration of HEART Framework with its method-specific working model.
UX Research
HEART Framework
Paper illustration of Counter Metrics with its method-specific working model.
Product Strategy
Counter Metrics
Paper illustration for Diary Study.
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.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.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.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
2-6 h120 min initial, dann laufend30-60 min1-4 Wochen
Participantsdifferent
2-83-62-65-20
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsHEART-GSM Table, DashboardCounter Metric List, Guardrail DefinitionsDiary Entries, Longitudinal Patterns, Experience Timeline
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
MetricsUX researchMeasurementSatisfaction
MetricsMeasurementStrategyExperiments
UX researchTrackingBehavior
Add more methods