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 | ![]() Engineering Kanban | ![]() Product Strategy Counter Metrics |
|---|---|---|---|---|
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. | 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 a headline metric could mask side effects, it adds guardrail signals against unwanted outcomes. It connects customer value, product logic, and decision priorities. The result is captured as a counter-metric list and guardrail definitions. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 h | 120 min initial, dann laufend | Ongoing | 30-60 min |
Participantsdifferent | 4-10 | 3-6 | 2-12 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | HEART-GSM Table, Dashboard | Kanban board, WIP policies, Flow metrics | Counter Metric List, Guardrail Definitions |
Tagsno overlap | LeanFlowWasteDelivery | MetricsUX researchMeasurementSatisfaction | FlowVisual managementDelivery | MetricsMeasurementStrategyExperiments |



