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 | ![]() Systems Thinking Iceberg Model | ![]() Systems Thinking Current Reality Tree | ![]() Systems Thinking Theory of Constraints Thinking Process |
|---|---|---|---|---|
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. | The Iceberg Model separates visible events from patterns, structures, and mental models. This turns a single observation into a deeper understanding of why a problem keeps recurring. | A Current Reality Tree condenses many symptoms into a few causal chains. The method makes visible which core problems drive several negative effects at once. | The Theory of Constraints Thinking Process exposes a system's bottleneck and the logic behind it. It suits situations where many symptoms trace back to the same limiting relationship. |
Complexitydifferent | Low | Low | High | High |
Timedifferent | 30-90 min | 30-60 min | 2-6 h | 0.5-3 Tage |
Participantsdifferent | 3-12 | 2-10 | 3-8 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Prioritized Backlog, Release Scope, Tradeoff Notes | Iceberg Worksheet, Pattern Notes, Intervention Ideas | Current Reality Tree, Core Problems, Intervention Ideas | Current Reality Logic, Conflict Cloud, Future Reality Tree, Implementation Obstacles |
Tagsno overlap | PrioritizationScopeDecision | Systems thinkingRoot causePatterns | Systems thinkingRoot causeConstraintsCausality | Theory of ConstraintsConstraintsSystems thinkingCausality |



