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 for Diary Study.
UX Research
Diary Study
Paper illustration of Goal Question Metric with its method-specific working model.
Engineering
Goal Question Metric
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 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.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.
Complexitysame
MediumMediumMedium
Timedifferent
2-6 h1-4 Wochen90-180 min
Participantsdifferent
2-85-203-6
Formatdifferent
Workshop + asyncAsyncWorkshop
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsDiary Entries, Longitudinal Patterns, Experience TimelineGQM Table, Metric Profiles
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
UX researchTrackingBehavior
MetricsMeasurementEngineeringAlignment
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of HEART Framework with its method-specific working model.
UX Research
HEART Framework
Paper illustration of KPI Tree with its method-specific working model.
Product Strategy
KPI Tree
Paper illustration of Counter Metrics with its method-specific working model.
Product Strategy
Counter Metrics
EventStorming on a long working surface: colored event cards form a business flow, friction points are marked, and a boundary separates different areas of responsibility.
Domain Modeling
EventStorming