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 Risk Storming.
Architecture
Risk Storming
Paper illustration of two people facing each other, speech bubbles and an open interview notebook.
UX Research
User Interviews
Affinity Diagramming
UX Research
Affinity Diagramming
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Purposedifferent
Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.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 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.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
LowLowLowMedium
Timedifferent
60-90 min30–60 min per interview45–90 min2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
4-121 participant per interview3-10Designers, developers as users, and facilitation
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Annotated Diagram, Prioritized Risk List, Action BacklogInterview Notes, Themes, Insight SummaryTheme clusters, Insight statements, Opportunity areasPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
RiskArchitectureWorkshopValidation
QualitativeResearchCustomerDiscovery
SynthesisQualitativeRoot cause
ArchitectureEngineeringFeedbackValidationTasks
Add more methods