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 |  Product Discovery Outcome-Driven Innovation |  Architecture arc42 |  Innovation Design Thinking |
|---|---|---|---|---|
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. | 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. | For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service. |
Complexitydifferent | Medium | High | Low | High |
Timedifferent | 30-60 min je Interview | Mehrere Wochen | 1-2 Tage | 1 Tag bis mehrere Wochen |
Participantsdifferent | 5-10 Interviews | 2-6 researchers plus sample | 1-4 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Solution Feedback, Objection List, Validation Notes | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Architecture Document, Context View, Runtime View, Deployment View | Problem Statement, Prototype, Test Learnings |
Tagsno overlap | ValidationInterviewsPrototype | OutcomesInnovationResearchQuantitative | ArchitectureDocumentationCommunication | InnovationPrototypeResearch |