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
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
Empathy Mapping
UX Research
Empathy Mapping
Paper illustration of Goal Question Metric with its method-specific working model.
Engineering
Goal Question Metric
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 a lot is assumed about a target group but little is seen jointly, empathy mapping makes knowledge and gaps directly comparable. The picture also shows which assumptions hold up and where evidence is missing.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.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
120 min initial, dann laufend2-8 h30–60 min90-180 min
Participantsdifferent
3-65-124-83-6
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
HEART-GSM Table, DashboardEvent Timeline, Ubiquitous Language, Boundaries, Open QuestionsEmpathy Map, Assumptions List, Research GapsGQM Table, Metric Profiles
Tagsno overlap
MetricsUX researchMeasurementSatisfaction
Domain-Driven DesignEventsDiscoveryWorkshop
SynthesisQualitativeWorkshop
MetricsMeasurementEngineeringAlignment
Add more methods