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 Problem Interview
Product Discovery
Problem Interview
Paper illustration of two people facing each other, speech bubbles and an open interview notebook.
UX Research
User Interviews
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Purposedifferent
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 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.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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.
Complexitydifferent
MediumLowLowMedium
Timedifferent
30-60 min je Interview30–60 min per interview1-2 Tage2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
5-12 Interviews1 participant per interview1-4Designers, developers as users, and facilitation
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Problem Evidence, Risk Notes, Customer SegmentsInterview Notes, Themes, Insight SummaryArchitecture Document, Context View, Runtime View, Deployment ViewPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
DiscoveryInterviewsValidation
QualitativeResearchCustomerDiscovery
ArchitectureDocumentationCommunication
ArchitectureEngineeringFeedbackValidationTasks
Add more methods