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 MoSCoW |  Decision Making Force Field Analysis |  Decision Making Assumption Surfacing |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | When a release carries too many demands and priorities are only ever negotiated, MoSCoW creates clear boundaries for the next cut. Must, Should, Could, and Won't make commitment, room for maneuver, and trade-off logic visible to everyone involved. | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 30-90 min | 45-90 min | 45-90 min | 45-60 min |
Participantsdifferent | 3-12 | 3-12 | 2-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Prioritized Backlog, Release Scope, Tradeoff Notes | Force Field Map, Change Levers, Risk Notes | Assumption List, Critical Assumptions, Learning Plan | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | PrioritizationScopeDecision | ChangeDecisionStrategy | AssumptionsRiskDecisionDiscovery | AssumptionsRiskExperimentsValidation |