Why this index exists
Prioritization is the most consequential decision a product or R&D leader makes each quarter, and the one with the least shared vocabulary. Teams pick frameworks (RICE, WSJF, MoSCoW), then quietly abandon them when the spreadsheet outgrows the meeting.
There is good public research on the downstream cost of that abandonment, but it is scattered across project-failure studies, developer-productivity indices, and portfolio-management surveys. This index consolidates the most defensible findings, then layers on a simple model for putting a dollar figure on what unstructured triage costs at portfolio scale.
01 · Synthesis
Key findings from public research
Five findings recur across the most cited public studies of project delivery, portfolio management, and engineering productivity. Each is sourced; see the citations list at the end of this piece for full references.
Roughly two of every three large IT projects miss schedule, scope, or budget.[1]
The Standish Group CHAOS reports have tracked project outcomes across more than 50,000 engagements since 1994. The "challenged" plus "failed" rate has hovered between 60 and 70 percent for two decades. Larger projects fare worse than smaller ones at a consistent rate.
Top-quartile engineering organizations ship four to five times more business value than bottom-quartile peers at the same headcount.[2]
McKinsey's Developer Velocity Index, built from a survey of 440 large enterprises, found a 4x to 5x revenue-growth gap between leaders and laggards. The differentiating practices are concentrated in tooling, product management, and developer experience.
Strategic Portfolio Management is a recognized category, not an emerging one.[3]
Gartner has published an annual Magic Quadrant for Strategic Portfolio Management since 2021. The category replaces what was previously called PPM and explicitly includes lean and product-centric portfolio practices, not just waterfall project portfolios.
The Stage-Gate / phase-gate approach remains the most widely adopted product-development governance model.[4]
Robert G. Cooper's decades of survey work for the Product Development and Management Association continues to find Stage-Gate or a close derivative in use at the majority of large product organizations, even those that describe themselves as agile.
Capacity-aware planning, not estimate accuracy, is the dominant predictor of on-time delivery.[5]
Mike Cohn's research on agile planning, drawing on the experience of more than 100 teams, points to consistent velocity and protected capacity as more reliable predictors of delivery than improvements to estimation technique. The implication for portfolio management is that scheduling is a capacity problem before it is an estimation problem.
02 · Original framework· original to Vantage
The Prioritization Debt model
Prioritization Debt is the recurring opportunity cost of running a portfolio without a consistent scoring practice. The model treats each quarter as a decision window: the portfolio either ranks the right work at the top of the queue, or it does not, and the gap between those two outcomes accrues as debt.
The formula below is intended to be computed from data most enterprise organizations already have. It is deliberately conservative: it ignores compounding effects and uses median rather than mean values, so the resulting figure is the floor, not the ceiling, of what prioritization debt likely costs.
PD = N × C × ( 1 − A ) × Q
- N
- Number of in-flight initiatives in the quarter
- C
- Median fully-loaded cost of one initiative-quarter (people, infra, opportunity)
- A
- Alignment ratio, 0–1, the fraction of in-flight initiatives that map to a top-quartile strategic objective
- Q
- Quarterly discount factor, 0–1, defaulting to 0.5 to reflect that misaligned work is rarely zero-value
A worked example
Consider a 250-person product organization running 40 in-flight initiatives in a given quarter. Fully-loaded cost per initiative-quarter, including people, cloud, and opportunity cost of headcount, lands around 180,000 USD. Of those 40 initiatives, leadership later confirms that 22 map cleanly to a top-quartile objective. The remaining 18 do not.
| Variable | Value |
|---|---|
| N — in-flight initiatives | 40 |
| C — median cost per initiative-quarter | $180,000 |
| A — alignment ratio (22 of 40) | 0.55 |
| Q — quarterly discount factor | 0.5 |
| PD — Quarterly Prioritization Debt | $1.62M |
| Annualized | ~$6.5M |
How Vantage uses the model in practice
Vantage instruments the alignment ratio (A) directly. Every initiative carries a strategic-objective link, and the platform computes A continuously from the portfolio. The cost variable (C) is sourced from finance, either as an organization-wide median or per-team blended rates. The result is a live PD figure that updates as the portfolio changes, instead of a one-off slide.
The same model is used inside Vantage to compute the upside of a re-prioritization scenario. Modeling a re-rank of the portfolio against a fresh set of strategic weights produces a delta on A, which translates directly into a recovered-debt figure leadership can act on.
Limitations and honest framing
The Prioritization Debt model is a planning lens, not an accounting one. It assumes that misaligned work has positive but reduced value (hence the 0.5 default discount), and it ignores second-order effects like organizational fatigue, customer trust erosion, and competitive timing. Treat the figure as directional.
The findings synthesized in this piece are taken from the most cited public sources available. Where this index makes a quantitative claim, it cites a study. Where the claim is original to Vantage, it is labeled as a model or framework, not a finding.
References
Sources
- [1]Standish Group International. CHAOS Reports, 1994 through 2020. https://www.standishgroup.com
- [2]Srivastava, Sahota, Wagle, and Hatami. "Developer Velocity: How software excellence fuels business performance." McKinsey & Company, April 2020. https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/developer-velocity-how-software-excellence-fuels-business-performance
- [3]Gartner. Magic Quadrant for Strategic Portfolio Management, annual editions since 2021.
- [4]Cooper, Robert G. Winning at New Products: Creating Value Through Innovation, 5th edition. Basic Books, 2017.
- [5]Cohn, Mike. Agile Estimating and Planning. Prentice Hall, 2005.
Machine readable
Datasets
Every dataset in this piece is also served as JSON for agents and downstream tools. Endpoints below.
Worked example inputs
Machine-readable copy of the worked-example table. Use as a starting set of inputs when computing PD against your own organization.
GET /api/research/2026-rd-prioritization-reference-index/datasets/worked-example
More research
- The Composite Portfolio Score: a methodology paper
How Vantage combines RICE, WSJF, and bounded AI judgment into a single composite score, including the formula, the failure modes the system tolerates, and the calibration approach.
