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 Kanban |  Growth Hooked Model |  Operations Waste Analysis |
|---|---|---|---|
Purposedifferent | 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. | The Hooked Model helps clarify engagement loops, user behavior, and experiments. It makes repeat behavior measurable and captures the result as a hooked loop, trigger map, and reward design. | 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 | Low |
Timedifferent | Ongoing | Multiple workshops over several weeks | 45-120 min |
Participantsdifferent | 2-12 | 2-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Hooked loop, Trigger map, Reward design, Ethics check | Waste Map, Prioritized Waste, Improvement Backlog |
Tagsno overlap | FlowVisual managementDelivery | GrowthBehaviorRetention | WasteLeanProcess improvement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
