View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Getting Things Done |  UX Research Customer Journey Mapping |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|
Purposedifferent | 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. | When a user journey falls apart across many touchpoints, customer journey mapping makes the experience visible as a coherent arc. Phases, emotions, and breaks become legible enough to prioritize critical moments deliberately. | 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 Setup, laufend | 2-4 h | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 1 | 4-10 | Designers, developers as users, and facilitation |
Formatdifferent | Async | Workshop | Workshop + async |
Outputdifferent | Action Lists, Project List, Review Routine | Journey Map, Pain-point List, Opportunity Backlog | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | ProductivityPlanningTasksExecution | JourneyServiceService design | ArchitectureEngineeringFeedbackValidationTasks |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
