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 Solution Interview |  Architecture Architecture Decision Record |  Product Discovery Outcome-Driven Innovation |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | When a solution idea is already on the table, it checks how it is understood and evaluated. It looks for resonance, objections, and missing fit early in the conversation. | 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. | Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs. | 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 | Medium | Low | High | Low |
Timedifferent | 30-60 min je Interview | 15-45 min | Mehrere Wochen | 1-2 Tage |
Participantsdifferent | 5-10 Interviews | 1-3 | 2-6 researchers plus sample | 1-4 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Solution Feedback, Objection List, Validation Notes | ADR File, Decision Log, Rationale | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ValidationInterviewsPrototype | ArchitectureRationaleDocumentationGovernance | OutcomesInnovationResearchQuantitative | ArchitectureDocumentationCommunication |