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 a participant using a prototype while an observer takes notes beside a highlighted usability issue.
UX Research
Usability Testing
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
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
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.An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.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
MediumMediumLowMedium
Timedifferent
1-2 h je Session1-3 Wochen vom Draft bis zur Entscheidung1-2 Tage2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
Based on research question3-20 Reviewer1-4Designers, developers as users, and facilitation
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Usability Issues, Severity List, RecommendationsRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsArchitecture 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
ValidationUXPrototype
ArchitectureDecisionAsyncGovernance
ArchitectureDocumentationCommunication
ArchitectureEngineeringFeedbackValidationTasks
Add more methods