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.

Selected:ARID (Active Reviews for Intermediate Designs)PersonasSolution InterviewDesign Thinking
Criterion
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration of two user profile cards with a goal, behavior evidence, and an open research question.
UX Research
Personas
Paper illustration for Solution Interview
Product Discovery
Solution Interview
Design Thinking as a learning loop: an observation notebook, a focused problem statement, different idea sketches, a cardboard prototype and user-test notes. Feedback leads to new understanding.
Innovation
Design Thinking
Purposedifferent
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 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.When a solution idea is already on the table, it checks how it is understood and evaluated. It looks for resonance, objections, and missing fit early in the conversation.For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service.
Complexitydifferent
MediumMediumMediumHigh
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional1-3 Tage30-60 min je Interview1 Tag bis mehrere Wochen
Participantsdifferent
Designers, developers as users, and facilitationInternes Team5-10 Interviews4-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsPersona Profiles, Needs Summary, Scenario NotesSolution Feedback, Objection List, Validation NotesProblem Statement, Prototype, Test Learnings
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
ResearchCustomerSynthesis
ValidationInterviewsPrototype
InnovationPrototypeResearch
Add more methods