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 Counter Metrics with its method-specific working model.
Product Strategy
Counter Metrics
Paper illustration for Diary Study.
UX Research
Diary Study
Paper illustration of KPI Tree with its method-specific working model.
Product Strategy
KPI Tree
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 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.When metrics across the organization drift apart, it arranges drivers and effects under one shared logic. It connects customer value, product logic, and decision priorities. The result is captured as a KPI tree and owner list.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
2-6 h30-60 min1-4 Wochen90-180 min initial, dann laufend
Participantsdifferent
2-82-65-203-8
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsCounter Metric List, Guardrail DefinitionsDiary Entries, Longitudinal Patterns, Experience TimelineKPI Tree, Owner List
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
MetricsMeasurementStrategyExperiments
UX researchTrackingBehavior
MetricsStrategyAlignmentMeasurement
Add more methods