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 |  Delivery RAID Log |  Product Discovery Assumption Mapping |
|---|---|---|---|
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 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-3 h | 30 min Setup, dann laufend | 45-60 min |
Participantsdifferent | 4-10 | 1-3 maintaining, briefing for everyone | 2-8 |
Formatdifferent | Workshop | Async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | RAID Log, Status Report Source | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | LeanFlowWasteDelivery | RiskTrackingStakeholdersGovernance | AssumptionsRiskExperimentsValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
