Portfolio prioritization framework

Why this playbook matters

Research groups often face more ideas than they can resource. Good prioritization focuses scarce attention and budget on projects that deliver the greatest value, reduce key risks, and accelerate learning. This playbook gives a repeatable, adaptable scoring framework you can use to evaluate, compare, and stage projects across a portfolio.

When to use this framework

• Setting annual or quarterly research priorities.
• Deciding which proposals to fund from a larger candidate set.
• Rebalancing an active portfolio (identify pilots, scale-ups, or shutdowns).
• Creating a governance-friendly record of why decisions were made.

Core principles

• Keep the criteria simple and relevant to your organizational hungers.
• Score consistently: use the same scales and weights across projects.
• Treat scores as decision inputs, not absolute truths—combine them with qualitative judgment.
• Design stopping rules and review cadence up front to avoid resource drag.

Five recommended criteria

1. Impact — potential benefit if successful (scientific, clinical, commercial, strategic). 0–5.
2. Novelty / Differentiation — degree to which the project fills a gap or creates an advantage vs. alternatives. 0–5.
3. Feasibility / Technical Risk — likelihood of successful execution given current knowledge and capabilities. (Higher score = more feasible). 0–5.
4. Time-to-Insight — expected elapsed time until a useful result or decision. (Higher score = faster insights). 0–5.
5. Resource Intensity — estimated cost, personnel, or infrastructure burden. (Higher score = lower resource burden). 0–5.

Scoring method

For each criterion, assign a score from 0 (worst) to 5 (best). Apply weights to reflect your priorities (weights total 100%). Compute a weighted sum to produce a single priority score for each project.

Worked example

Three candidate projects (Alpha, Beta, Gamma) scored using the default weights:

Interpretation: Alpha (3.6) is top priority to fund at scale or pilot aggressively because of high impact and reasonable feasibility. Beta is a high-novelty, riskier bet—suitable for a focused pilot with clear go/no-go milestones. Gamma is operationally easy and fast but has lower impact—consider as a quick win or deprioritize in favor of higher-impact work.

From scores to staging decisions

Map weighted scores into staging categories. Adjust thresholds for your context:

• Fund & Scale — weighted score >= 3.5 and acceptable risk.
• Pilot / Validate — score 3.0–3.5 or high novelty with moderate risk; define 3–6 month milestones.
• Park / Defer — score 2.0–3.0 unless strategic reasons exist; revisit in next planning cycle.
• Stop — score < 2.0 or projects consuming resources without learning; apply stopping rules.

Governance and review cadence

• Use time-boxed pilots with specific metrics and decision milestones.
• Review pilots at predetermined gates; require evidence tied to the criteria (e.g., early signals of impact or technical feasibility).
• Assign clear owners and budget envelopes by stage (explore, pilot, scale).
• Track learning outcomes as part of the portfolio scorecard—learning itself can be a measurable outcome.

Customization and fairness

Tailor criteria and weights to your group: a translational lab may weigh time-to-insight and feasibility more heavily; an exploratory group may emphasize novelty. Document chosen weights and rationale so decisions remain transparent and reproducible.

Common pitfalls

• Invisible bias — ensure scoring panels include diverse perspectives (scientific, operational, stakeholder).
• Overly granular scores — prefer 0–5 to avoid false accuracy.
• No stopping rules — projects linger; set explicit end criteria for pilots.
• Ignoring dependencies — consider shared resources, regulatory timelines, and dependencies when comparing projects.

Next steps — practical checklist

1. Agree criteria and weights with stakeholders and publish them.
2. Score candidates independently, then reconcile differences in a short panel meeting.
3. Assign staging decisions with owners, budgets, and milestones.
4. Set review cadence and stopping rules for pilots.
5. Capture scores and decisions in a persistent record for future learning and audit.

Tools and extensions

This playbook lends itself to an interactive scoring sheet (save per-project submissions and history), dashboards that show portfolio composition by stage and risk, and templated pilot reports. See Capability notes for practical implementation ideas.

Adapt this framework to your context: the goal is reliable, transparent decision-making that maximizes impact and learning while avoiding spreading resources too thin.