View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Strategy RICE Scoring |  Engineering Kanban |  Operations ABC Analysis |  Delivery Monte Carlo Forecasting |
|---|---|---|---|---|
Purposedifferent | When many initiatives compete for the same resources, it brings reach, impact, confidence, and effort into one shared ranking. It makes prioritization economically connectable. | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as Forecast Percentiles, Throughput Dataset, and Risk Communication. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 60-90 min | Ongoing | 30-60 min | 30-90 min Setup, danach laufend |
Participantsdifferent | 2-10 | 2-12 | 1-5 | 1-8 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | RICE Scores, Ranked List, Assumption Log | Kanban board, WIP policies, Flow metrics | ABC Classification, Focus Rules, Control List | Forecast Percentiles, Throughput Dataset, Risk Communication |
Tagsno overlap | PrioritizationScoringRoadmapTradeoffs | FlowVisual managementDelivery | PrioritizationOperationsPortfolio | ForecastingFlowDelivery |