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 arc42 | ![]() UX Research User Interviews | ![]() Product Discovery Test Card | ![]() Product Discovery Experiment Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | The Test Card turns a critical assumption into a testable claim and specifies in advance which result counts as success. | When experiments become unreadable after the fact, it arranges hypothesis, signal, and learning goal on a single canvas. It separates problem, assumption, solution, and evidence. The result is captured as a Completed Experiment Canvas and a Success Metric. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 1-2 Tage | 30–60 min per interview | 20-35 min | 30-60 min |
Participantsdifferent | 1-4 | 1 participant per interview | 1-5 | 1-5 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Interview Notes, Themes, Insight Summary | Test Card with a pre-set threshold | Completed Experiment Canvas, Success Metric |
Tagsno overlap | ArchitectureDocumentationCommunication | QualitativeResearchCustomerDiscovery | ExperimentsValidationDiscoveryHypothesis | ExperimentsValidationDiscoveryHypothesis |



