View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Opportunity Interview |  UX Research Affinity Diagramming |  Architecture arc42 |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | When opportunities are still hidden behind signals of need, it structures conversations around needs and obstacles. It looks for patterns that lead to new product opportunities. | When research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 30-60 min je Interview | 45–90 min | 1-2 Tage | 15-45 min |
Participantsdifferent | 5-12 Interviews | 3-10 | 1-4 | 1-3 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Async |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Theme clusters, Insight statements, Opportunity areas | Architecture Document, Context View, Runtime View, Deployment View | ADR File, Decision Log, Rationale |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | SynthesisQualitativeRoot cause | ArchitectureDocumentationCommunication | ArchitectureRationaleDocumentationGovernance |