View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Hypothesis-Driven Troubleshooting |  Product Discovery Opportunity Scoring |  Product Discovery Kano Model |  UX Design Lean UX Canvas |
|---|---|---|---|---|
Purposedifferent | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | When opportunities need ranking by their effect, it makes importance and satisfaction directly comparable. It separates problem, assumption, solution, and evidence. The result is captured as an opportunity-score table and top outcomes. | When features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight. | The Lean UX Canvas helps clarify user behavior, touchpoints, and concept decisions. It makes assumptions and desired outcomes visible and captures the result as a completed canvas, hypothesis list, and first experiment. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 30-240 min | 60-120 min | 1-2 Tage | 2-3 h |
Participantsdifferent | 1-6 | 3-6 | 10-50 | 3-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Opportunity Score Table, Top Outcomes | Kano Matrix, Feature Classes, Priority Themes | Completed Lean UX Canvas, Hypothesis list, First experiment |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | PrioritizationDiscoveryOutcomesNeeds | SatisfactionPrioritizationCustomer | CanvasHypothesisOutcomesDiscovery |