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
Empathy Mapping
UX Research
Empathy Mapping
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration for Problem Interview
Product Discovery
Problem Interview
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
Purposedifferent
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.ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.When the picture of the problem still needs to become solid, it asks about real situations and consequences. It separates genuine suffering from mere interest in a solution.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.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
30–60 min2–4 h review as a planning range; preparation and evaluation additional30-60 min je Interview2-8 h
Participantsdifferent
4-8Designers, developers as users, and facilitation5-12 Interviews5-12
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Empathy Map, Assumptions List, Research GapsPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsProblem Evidence, Risk Notes, Customer SegmentsEvent Timeline, Ubiquitous Language, Boundaries, Open Questions
Tagsno overlap
SynthesisQualitativeWorkshop
ArchitectureEngineeringFeedbackValidationTasks
DiscoveryInterviewsValidation
Domain-Driven DesignEventsDiscoveryWorkshop
Add more methods