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 Design Customer Journey Canvas |  Engineering Goal Question Metric |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|
Purposedifferent | When a journey needs to be understood across several phases, it arranges experience, touchpoints, and opportunities into one picture. It makes gaps and friction along the user path clear. | Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs. | 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-3 h | 90-180 min | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 3-10 | 3-6 | Designers, developers as users, and facilitation |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Customer Journey Canvas, Pain Points, Experience Opportunities | GQM Table, Metric Profiles | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | JourneyCustomerService designCanvas | MetricsMeasurementEngineeringAlignment | ArchitectureEngineeringFeedbackValidationTasks |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
