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 |  Engineering Goal Question Metric |  Innovation Design Sprint |
|---|---|---|---|
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. | Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs. | When the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess. |
Complexitydifferent | Medium | Medium | High |
Timedifferent | 30-60 min je Interview | 90-180 min | 4-5 Tage |
Participantsdifferent | 5-10 Interviews | 3-6 | 5-8 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Solution Feedback, Objection List, Validation Notes | GQM Table, Metric Profiles | Prototype, Test Findings, Decision Rationale |
Tagsno overlap | ValidationInterviewsPrototype | MetricsMeasurementEngineeringAlignment | Design sprintPrototypeValidationInnovation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
