Portfolio Prioritisation Frameworks

The Prioritisation Problem

Every portfolio faces the same challenge: more demand than capacity. Stakeholders compete for limited resources. Every initiative has a compelling business case. Without a structured framework, prioritisation defaults to:

• Whoever shouts loudest (political prioritisation)
• Whatever the CEO mentioned last (recency bias)
• Whatever's already started (sunk cost fallacy)
• Equal distribution across all initiatives (peanut butter spreading)

None of these maximise value. Structured prioritisation frameworks replace politics with data-driven decision-making.

Framework 1: Weighted Shortest Job First (WSJF)

Best for: SAFe environments, continuous flow portfolios, when you need to sequence work for maximum economic benefit.

Formula: WSJF = Cost of Delay ÷ Job Size

Cost of Delay is the sum of three factors (each scored 1-10 relative to other items):

• Business Value: Revenue impact, cost saving, strategic importance
• Time Criticality: Does value decrease if delayed? Regulatory deadlines? Market windows?
• Risk Reduction / Opportunity Enablement: Does this reduce risk or enable future opportunities?

Job Size: Relative effort to deliver (1-10, where 1 is smallest)

Example:

| Initiative | Business Value | Time Criticality | Risk Reduction | CoD | Job Size | WSJF | |---|---|---|---|---|---|---| | Payment migration | 8 | 9 | 7 | 24 | 5 | 4.8 | | Mobile app | 7 | 3 | 4 | 14 | 8 | 1.75 | | Security upgrade | 5 | 8 | 9 | 22 | 3 | 7.3 |

Priority order: Security upgrade (7.3) → Payment migration (4.8) → Mobile app (1.75)

Strengths: Accounts for time sensitivity. Favours small, high-value items. Widely understood in SAFe. Weaknesses: Relative scoring can be gamed. Requires calibration across scorers. Doesn't account for dependencies.

Framework 2: Weighted Scoring Model

Best for: Portfolio boards making investment decisions, comparing diverse initiatives, when multiple criteria matter.

Process: 1. Define 4-6 scoring criteria (aligned with strategy) 2. Assign weights to each criterion (must sum to 100%) 3. Score each initiative against each criterion (1-10) 4. Calculate weighted score: Σ(score × weight) 5. Rank by total weighted score

Example criteria and weights:

• Strategic alignment (25%): How well does this support our strategic objectives?
• Financial impact (25%): Expected ROI, cost saving, or revenue
• Risk (20%): Delivery risk, technical risk, market risk (lower risk = higher score)
• Customer impact (15%): Number of customers affected, satisfaction improvement
• Urgency (15%): Regulatory deadline, competitive pressure, dependency on timing

Strengths: Transparent and defensible. Criteria can be customised to organisational strategy. Easy to explain to stakeholders. Weaknesses: Criteria selection is subjective. Scores can be manipulated. Doesn't account for dependencies or sequencing.

Framework 3: MoSCoW at Portfolio Level

Best for: Fixed-budget portfolios, annual planning cycles, when you need to make binary in/out decisions.

• Must Have: Initiatives that are non-negotiable (regulatory, contractual, existential risk)
• Should Have: High-value initiatives that the portfolio should include if possible
• Could Have: Valuable but deferrable — include only if capacity allows
• Won't Have (this period): Explicitly deferred to a future planning cycle

The rule: Must Haves should consume no more than 60% of portfolio capacity. This leaves room for Should Haves (20%) and Could Haves (20%). If Must Haves exceed 60%, either the bar for "Must" is too low or the portfolio is under-resourced.

Strengths: Simple, fast, easy to communicate. Forces explicit trade-offs. Clear "in/out" decisions. Weaknesses: Doesn't differentiate within categories. Everything becomes "Must Have" without discipline. No sequencing guidance.

Framework 4: RICE Scoring

Best for: Product portfolios, feature prioritisation, when reach and confidence matter.

Formula: RICE = (Reach × Impact × Confidence) ÷ Effort

• Reach: How many customers/users will this affect in a given period?
• Impact: How much will it affect each person? (3 = massive, 2 = high, 1 = medium, 0.5 = low, 0.25 = minimal)
• Confidence: How confident are we in our estimates? (100% = high, 80% = medium, 50% = low)
• Effort: Person-months of work required

Strengths: Accounts for uncertainty (confidence factor). Penalises large, uncertain initiatives. Good for product-led organisations. Weaknesses: "Reach" is hard to estimate for internal/infrastructure initiatives. Confidence scoring is subjective.

Choosing the Right Framework

| Context | Recommended Framework | |---|---| | SAFe environment, continuous flow | WSJF | | Annual portfolio planning, diverse initiatives | Weighted Scoring | | Fixed budget, binary decisions needed | MoSCoW | | Product-led, customer-facing features | RICE | | Mixed portfolio with both products and projects | Weighted Scoring + MoSCoW |

Running a Prioritisation Session

Preparation

• Gather initiative proposals with consistent information (business case summary, estimated effort, expected benefits, risks)
• Pre-score initiatives individually (each portfolio board member scores independently before the session)
• Identify dependencies between initiatives (some can't be done without others)

The Session (2-3 hours for quarterly planning)

1. Calibration (15 min): Review scoring criteria and definitions. Ensure everyone interprets them consistently. 2. Individual scoring review (30 min): Share pre-scores. Discuss where scores diverge significantly (>3 points difference). 3. Consensus scoring (60 min): For each initiative, agree a consensus score through discussion. Don't average — discuss and agree. 4. Capacity check (30 min): Rank initiatives by score. Draw the capacity line. Everything above the line is funded; everything below is deferred. 5. Dependency check (15 min): Verify that funded initiatives don't depend on unfunded ones. Adjust if needed. 6. Communication plan (15 min): Agree how decisions will be communicated to initiative sponsors.

After the Session

• Document decisions with rationale (not just the scores — why)
• Communicate to all initiative sponsors (funded and deferred)
• For deferred initiatives: "Not now" with clear criteria for re-evaluation
• Schedule quarterly re-prioritisation (priorities change as context changes)

Anti-Patterns

Prioritisation without data: Scoring based on gut feel rather than evidence. Fix: require each initiative to provide quantified benefits, estimated effort, and risk assessment before scoring.

The permanent backlog: Deferred initiatives sit in the backlog forever without re-evaluation. Fix: review deferred items quarterly. If they've been deferred 3 times, either fund them or explicitly cancel them.

Gaming the scores: Sponsors inflate their initiative's scores to win funding. Fix: independent scoring by the portfolio board (not self-assessment by sponsors). Challenge outlier scores.

Ignoring dependencies: Prioritising initiatives independently without considering that some enable others. Fix: map dependencies before scoring. Fund enablers even if their standalone score is lower.

Annual-only prioritisation: Setting priorities once a year and never adjusting. Fix: quarterly re-prioritisation with the ability to stop low-performing initiatives and redirect resources.

---

Download the [Investment Prioritisation Scorecard template](/templates) for a ready-to-use weighted scoring model with 6 criteria.