Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Selected:Empathy Mapping Architecture Decision Record ARID (Active Reviews for Intermediate Designs)Risk Storming

Criterion	UX Research Empathy Mapping	Architecture Architecture Decision Record	Architecture ARID (Active Reviews for Intermediate Designs)	Architecture Risk Storming
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.	An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.	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.	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.
Complexitydifferent	Low	Low	Medium	Low
Timedifferent	30–60 min	15-45 min	2–4 h review as a planning range; preparation and evaluation additional	60-90 min
Participantsdifferent	4-8	1-3	Designers, developers as users, and facilitation	4-12
Formatdifferent	Workshop	Async	Workshop + async	Workshop
Outputdifferent	Empathy Map, Assumptions List, Research Gaps	ADR File, Decision Log, Rationale	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Annotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap	SynthesisQualitativeWorkshop	ArchitectureRationaleDocumentationGovernance	ArchitectureEngineeringFeedbackValidationTasks	RiskArchitectureWorkshopValidation

Add more methods