Move from many initiatives to transparent order, scope, and explicit trade-offs.
A prioritized list with scoring, scope decisions, and documented assumptions.
You can decide which initiatives to pursue first and which are intentionally delayed or not implemented.
Translate priorities into roadmap, backlog slicing, and stakeholder communication.
Which important user outcomes are currently underserved in the target segment?
Opportunity Scoring ranks opportunities by value, urgency, and evidence before effort discussions dominate.
The stronger opportunities are then further evaluated with Reach, Impact, Confidence, and Effort.
Which initiative promises the greatest expected contribution to our goal relative to effort?
RICE makes value, reach, certainty, and effort transparent and comparable.
Scores are then compared with time criticality and delay cost.
What value is lost per week of delay, what is the loss profile, and which assumptions support the estimate?
Cost of Delay shows which initiatives lose the most value when delayed.
Value, urgency, and effort then feed into concrete release scope.
Which requirements must be in this release, which are negotiable, and what is deliberately left for later?
MoSCoW cuts scope into must, should, could, and explicitly excluded elements.
The scope is adopted in roadmap, backlog, and expectation management.
Artifacts stay collapsed until you actually need them.
Markdown matrix for comparing options across competing criteria and accepted trade-offs.
# Trade-off Matrix: Decision
| Criterion | Weight | Option A | Option B | Option C |
|---|---:|---|---|---|
| Benefit | 30 | | | |
| Cost | 20 | | | |
| Risk | 20 | | | |
| Time-to-Learn | 15 | | | |
| Reversibility | 15 | | | |
## Accepted trade-offs
- Option A accepts:
- Option B accepts:
- Option C accepts:
## Recommendation
Which option is recommended and why?
## Sensitivity
Which small change in weighting or assumption would flip the recommendation?