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 Red Teaming | ![]() Decision Making Assumption Surfacing | ![]() Decision Making Argument 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. | For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments. | 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 statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. |
Complexitydifferent | Low | High | Low | Medium |
Timedifferent | 30-90 min | 1-4 h | 45-90 min | 1-3 h |
Participantsdifferent | 3-12 | 3-8 | 2-8 | 1-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Prioritized Backlog, Release Scope, Tradeoff Notes | Challenge Findings, Risk Register, Mitigation Plan | Assumption List, Critical Assumptions, Learning Plan | Argument Map, Evidence Gaps, Decision Rationale |
Tags1 shared | PrioritizationScopeDecision | RiskDecisionSensemaking | AssumptionsRiskDecisionDiscovery | SensemakingDecisionRationale |



