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 an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Affinity Diagramming
UX Research
Affinity Diagramming
Empathy Mapping
UX Research
Empathy Mapping
Purposedifferent
Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.When research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer.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.
Complexitysame
LowLowLow
Timedifferent
45-90 min45–90 min30–60 min
Participantsdifferent
2-83-104-8
Formatdifferent
Workshop + asyncWorkshopWorkshop
Outputdifferent
Assumption List, Critical Assumptions, Learning PlanTheme clusters, Insight statements, Opportunity areasEmpathy Map, Assumptions List, Research Gaps
Tagsno overlap
AssumptionsRiskDecisionDiscovery
SynthesisQualitativeRoot cause
SynthesisQualitativeWorkshop
Add more methods

Often compared together

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

Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Paper illustration of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
Paper illustration of DIBB with its method-specific working model.
Product Strategy
DIBB
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