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 |  Engineering Kanban |  Delivery RAID Log |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
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. | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | Ongoing | 30 min Setup, dann laufend | 60-90 min |
Participantsdifferent | 4-10 | 2-12 | 1-3 maintaining, briefing for everyone | 3-6 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Kanban board, WIP policies, Flow metrics | RAID Log, Status Report Source | Salience Diagram, Strategy per Class |
Tagsno overlap | LeanFlowWasteDelivery | FlowVisual managementDelivery | RiskTrackingStakeholdersGovernance | StakeholdersFacilitationAlignmentGovernance |