View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  UX Research User Interviews |  Product Discovery Concierge MVP |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | When teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible. | 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. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 15-45 min | 30–60 min per interview | 1-4 Wochen | 1-2 Tage |
Participantsdifferent | 1-3 | 1 participant per interview | 3-10 Kunden | 1-4 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Interview Notes, Themes, Insight Summary | Concierge Learnings, Service Blueprint, MVP Risks | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | QualitativeResearchCustomerDiscovery | MVPValidationServiceDiscovery | ArchitectureDocumentationCommunication |