methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
A paper-based illustration representing WSJF with its core stages and visible working result.
Agile
WSJF
Value Stream Mapping workspace showing the question, observations, and next decision.
Delivery
Value Stream Mapping
Paper illustration of DIBB with its method-specific working model.
Product Strategy
DIBB
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Purposedifferent
When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together.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.DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report.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
HighMediumLowLow
Timedifferent
45-90 min1-3 h1-2 h45-90 min
Participantsdifferent
3-104-102-83-12
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Ranked Backlog, Cost-of-Delay AssumptionsCurrent-state map, Future-state map, Bottleneck listDIBB document, Belief list, Bet list, Learning reportForce Field Map, Change Levers, Risk Notes
Tagsno overlap
LeanEconomicsSequencePrioritization
LeanFlowWasteDelivery
StrategyDecisionAssumptionsHypothesis
ChangeDecisionStrategy
Add more methods