View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Customer Journey MappingATAM (Architecture Tradeoff Analysis Method)Concierge MVPARID (Active Reviews for Intermediate Designs)
| Criterion |  UX Research Customer Journey Mapping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Product Discovery Concierge MVP |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|---|
Purposedifferent | 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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | When an idea can first fail or grow through genuine hands-on support, it relies on manual work instead of automation. It shows whether user value holds up even under manual execution. | 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 | Medium | High | Medium | Medium |
Timedifferent | 2-4 h | Several meetings plus preparation and analysis; total effort depends on scope | 1-4 Wochen | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 4-10 | Evaluation team, architects, and relevant stakeholders | 3-10 Kunden | Designers, developers as users, and facilitation |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Journey Map, Pain-point List, Opportunity Backlog | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Concierge Learnings, Service Blueprint, MVP Risks | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | JourneyServiceService design | ArchitectureQualityRiskTradeoffsStakeholders | MVPValidationServiceDiscovery | ArchitectureEngineeringFeedbackValidationTasks |