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 |  Agile WSJF |  Engineering Kanban |
|---|---|---|---|
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 many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together. | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 1-2 Tage | 45-90 min | Ongoing |
Participantsdifferent | 10-50 | 3-10 | 2-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Ranked Backlog, Cost-of-Delay Assumptions | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | SatisfactionPrioritizationCustomer | LeanEconomicsSequencePrioritization | FlowVisual managementDelivery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
