View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() UX Research Usability Testing | ![]() Operations Getting Things Done | ![]() 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. | With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-2 h je Session | 1-2 h Setup, laufend | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | Based on research question | 1 | Designers, developers as users, and facilitation |
Formatdifferent | Workshop + async | Async | Workshop + async |
Outputdifferent | Usability Issues, Severity List, Recommendations | Action Lists, Project List, Review Routine | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | ValidationUXPrototype | ProductivityPlanningTasksExecution | ArchitectureEngineeringFeedbackValidationTasks |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






