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 a JTBD interview notebook with a decision timeline, forces of change and a concise job hypothesis.
Product Discovery
Jobs to Be Done
A paper-based illustration representing Kano Model with its core stages and visible working result.
Product Discovery
Kano Model
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
Purposedifferent
When switching motives and progress are unclear, it reconstructs the situation from real customer circumstances. It shows why a switch happens and what kind of progress is being sought.When features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight.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 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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
1-3 Wochen1-2 Tage120 min initial, dann laufend90-180 min initial, dann laufend
Participantsdifferent
5-12 Interviews10-503-63-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Job Stories, Outcome Statements, Opportunity ListKano Matrix, Feature Classes, Priority ThemesHEART-GSM Table, DashboardKPI Tree, Owner List
Tagsno overlap
CustomerOutcomesNeeds
SatisfactionPrioritizationCustomer
MetricsUX researchMeasurementSatisfaction
MetricsStrategyAlignmentMeasurement
Add more methods