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
Paper illustration of HEART Framework with its method-specific working model.
UX Research
HEART Framework
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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
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.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 several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
120 min initial, dann laufend2-6 h30-60 min1-3 h
Participantsdifferent
3-62-82-62-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
HEART-GSM Table, DashboardEvent Model, UI Flow, Commands, Read ModelsCounter Metric List, Guardrail DefinitionsContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
MetricsUX researchMeasurementSatisfaction
EventsBlueprintDomain-Driven DesignBehavior
MetricsMeasurementStrategyExperiments
Domain-Driven DesignBoundariesStrategy
Add more methods