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 | ![]() Product Discovery Assumption Mapping | ![]() Decision Making Force Field Analysis |
|---|---|---|---|
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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-3 h | 45-60 min | 45-90 min |
Participantsdifferent | 4-10 | 2-8 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Assumption map, Test backlog, Risk ranking | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | LeanFlowWasteDelivery | AssumptionsRiskExperimentsValidation | ChangeDecisionStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






