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 for Opportunity Interview
Product Discovery
Opportunity Interview
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
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 for Problem Interview
Product Discovery
Problem Interview
Purposedifferent
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.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 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 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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
30-60 min je Interview2–4 h review as a planning range; preparation and evaluation additional2-8 h30-60 min je Interview
Participantsdifferent
5-12 InterviewsDesigners, developers as users, and facilitation5-125-12 Interviews
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Interview Notes, Opportunity Themes, Customer QuotesPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsEvent Timeline, Ubiquitous Language, Boundaries, Open QuestionsProblem Evidence, Risk Notes, Customer Segments
Tagsno overlap
DiscoveryInterviewsOpportunityCustomer
ArchitectureEngineeringFeedbackValidationTasks
Domain-Driven DesignEventsDiscoveryWorkshop
DiscoveryInterviewsValidation
Add more methods