View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery Value Stream Mapping |  UX Research HEART Framework |  Operations Bottleneck Analysis |  Engineering Kanban |
|---|---|---|---|---|
Purposedifferent | 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. | Helps clarify observations, needs, and patterns in concrete terms. It groups observations into patterns, questions, and decisions. The result is captured as a HEART-GSM table and dashboard. | For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | 120 min initial, dann laufend | 1-3 h | Ongoing |
Participantsdifferent | 4-10 | 3-6 | 3-8 | 2-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | HEART-GSM Table, Dashboard | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | LeanFlowWasteDelivery | MetricsUX researchMeasurementSatisfaction | FlowMeasurementConstraints | FlowVisual managementDelivery |