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 RAID Log |  Delivery Value Stream Mapping |  Facilitation Stakeholder Salience Model |
|---|---|---|---|
Purposedifferent | 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 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 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 | Low | Medium | Medium |
Timedifferent | 30 min Setup, dann laufend | 1-3 h | 60-90 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 4-10 | 3-6 |
Formatdifferent | Async | Workshop | Workshop |
Outputdifferent | RAID Log, Status Report Source | Current-state map, Future-state map, Bottleneck list | Salience Diagram, Strategy per Class |
Tagsno overlap | RiskTrackingStakeholdersGovernance | LeanFlowWasteDelivery | StakeholdersFacilitationAlignmentGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
