View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Risk Storming |  UX Research Empathy Mapping |  UX Research Personas |  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 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. | When target groups stay too vague and teams talk about the same people differently, personas create a shared, solid picture of usage. Condensed profiles make needs, contexts, and differences tangible enough for decisions. | 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 | Low | Low | Medium | Medium |
Timedifferent | 60-90 min | 30–60 min | 1-3 Tage | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 4-12 | 4-8 | Internes Team | Designers, developers as users, and facilitation |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Empathy Map, Assumptions List, Research Gaps | Persona Profiles, Needs Summary, Scenario Notes | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | RiskArchitectureWorkshopValidation | SynthesisQualitativeWorkshop | ResearchCustomerSynthesis | ArchitectureEngineeringFeedbackValidationTasks |