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:Usability TestingRisk StormingDesign ThinkingARID (Active Reviews for Intermediate Designs)
Criterion
Paper illustration of a participant using a prototype while an observer takes notes beside a highlighted usability issue.
UX Research
Usability Testing
Paper illustration for Risk Storming.
Architecture
Risk Storming
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
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Purposedifferent
When a product is built but people get stuck on tasks, usability testing shows the friction at concrete points. Observed use instead of self-report makes visible where orientation, understanding, or interaction breaks down.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.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.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
MediumLowHighMedium
Timedifferent
1-2 h je Session60-90 min1 Tag bis mehrere Wochen2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
Based on research question4-124-10Designers, developers as users, and facilitation
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Usability Issues, Severity List, RecommendationsAnnotated Diagram, Prioritized Risk List, Action BacklogProblem Statement, Prototype, Test LearningsPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
ValidationUXPrototype
RiskArchitectureWorkshopValidation
InnovationPrototypeResearch
ArchitectureEngineeringFeedbackValidationTasks
Add more methods