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 of two user profile cards with a goal, behavior evidence, and an open research question.
UX Research
Personas
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration of Outcome-Driven Innovation with its method-specific working model.
Product Discovery
Outcome-Driven Innovation
Paper illustration of a JTBD interview notebook with a decision timeline, forces of change and a concise job hypothesis.
Product Discovery
Jobs to Be Done
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.Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs.When switching motives and progress are unclear, it reconstructs the situation from real customer circumstances. It shows why a switch happens and what kind of progress is being sought.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
1-3 Tage2–4 h review as a planning range; preparation and evaluation additionalMehrere Wochen1-3 Wochen
Participantsdifferent
Internes TeamDesigners, developers as users, and facilitation2-6 researchers plus sample5-12 Interviews
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Persona Profiles, Needs Summary, Scenario NotesPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsDesired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypothesesJob Stories, Outcome Statements, Opportunity List
Tagsno overlap
ResearchCustomerSynthesis
ArchitectureEngineeringFeedbackValidationTasks
OutcomesInnovationResearchQuantitative
CustomerOutcomesNeeds
Add more methods