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 |  Engineering Kanban |  Delivery Value Stream Mapping |  Operations Waste Analysis |
|---|---|---|---|---|
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 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. | 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 process that keeps people busy but creates little value, the method exposes waste. It directs attention to unnecessary movement, waiting times, rework, and overdelivery. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-2 Tage | Ongoing | 1-3 h | 45-120 min |
Participantsdifferent | 10-50 | 2-12 | 4-10 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Kanban board, WIP policies, Flow metrics | Current-state map, Future-state map, Bottleneck list | Waste Map, Prioritized Waste, Improvement Backlog |
Tagsno overlap | SatisfactionPrioritizationCustomer | FlowVisual managementDelivery | LeanFlowWasteDelivery | WasteLeanProcess improvement |