View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() UX Research Personas | ![]() Architecture ARID (Active Reviews for Intermediate Designs) | ![]() Growth A/B Testing |
|---|---|---|---|
Purposedifferent | 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. | When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. |
Complexitydifferent | Medium | Medium | High |
Timedifferent | 1-3 Tage | 2–4 h review as a planning range; preparation and evaluation additional | 1-4 Wochen |
Participantsdifferent | Internes Team | Designers, developers as users, and facilitation | 1-6 |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Experiment results, Decision log, Learning summary |
Tagsno overlap | ResearchCustomerSynthesis | ArchitectureEngineeringFeedbackValidationTasks | ExperimentsGrowthAnalyticsValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






