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
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
Paper illustration of a participant using a prototype while an observer takes notes beside a highlighted usability issue.
UX Research
Usability Testing
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Purposedifferent
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.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.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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
HighMediumLowMedium
Timedifferent
1 Tag bis mehrere Wochen1-2 h je Session1-2 Tage2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
4-10Based on research question1-4Designers, developers as users, and facilitation
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Problem Statement, Prototype, Test LearningsUsability Issues, Severity List, RecommendationsArchitecture Document, Context View, Runtime View, Deployment ViewPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
InnovationPrototypeResearch
ValidationUXPrototype
ArchitectureDocumentationCommunication
ArchitectureEngineeringFeedbackValidationTasks
Add more methods