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 two people facing each other, speech bubbles and an open interview notebook.
UX Research
User Interviews
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
Paper illustration for Opportunity Interview
Product Discovery
Opportunity Interview
Purposedifferent
When teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible.When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole.When opportunities are still hidden behind signals of need, it structures conversations around needs and obstacles. It looks for patterns that lead to new product opportunities.
Complexitydifferent
LowMediumMedium
Timedifferent
30–60 min per interview1-3 h30-60 min je Interview
Participantsdifferent
1 participant per interview3-105-12 Interviews
Formatdifferent
Workshop + asyncWorkshopWorkshop + async
Outputdifferent
Interview Notes, Themes, Insight SummaryDomain Context Map, Boundary Notes, Ownership MapInterview Notes, Opportunity Themes, Customer Quotes
Tagsno overlap
QualitativeResearchCustomerDiscovery
Domain-Driven DesignContextBoundaries
DiscoveryInterviewsOpportunityCustomer
Add more methods

Often compared together

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

A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
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
Paper illustration of a branching tree with an outcome at its root, customer opportunities, solution options and small experiment cards.
Product Discovery
Opportunity Solution Tree