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 Kano Model |  Delivery Value Stream Mapping |  Operations 5 Whys |
|---|---|---|---|
Purposedifferent | 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. | When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-2 Tage | 1-3 h | 15-30 min |
Participantsdifferent | 10-50 | 4-10 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Current-state map, Future-state map, Bottleneck list | Root cause notes, Countermeasures |
Tagsno overlap | SatisfactionPrioritizationCustomer | LeanFlowWasteDelivery | Root causeIncidentLeanProblem solving |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
