Home/Research/Specifications/Product Debt Index (PDI)
Canonical Research SpecificationLevel: Architect
Verified: August 2026

Product Debt Index (PDI)

30-Second Executive Definition

A diagnostic score ranging from 0 to 100 that quantifies the total technical debt of a software organization in explicit dollar terms. The Product Debt Index translates abstract engineering complexity into measurable carrying costs and valuation drag. It provides a standardized mechanism for product and finance teams to measure the economic penalty of unmanaged software feature accumulation. By establishing a direct link between code entropy and financial performance, the PDI forces accountability in architectural decision-making.

Technical debt is an engineering problem. Product debt is a balance sheet crisis.

Why It Matters:

Traditional technical debt metrics fail because they remain isolated within engineering departments as story points or refactoring tickets. The Product Debt Index bridges this gap by expressing debt as a financial liability on the balance sheet. When executives can see the explicit dollar cost of feature bloat, they allocate resources toward stabilization rather than blind expansion. This metric fundamentally alters how companies evaluate the true cost of their product roadmaps.

Who Should Care:
Chief Financial OfficersChief Product OfficersEngineering Directors
Infinite Relationship Navigator118-Node Sovereign Knowledge Graph

Multi-Hop Causal Traversal Engine

Explore how concepts dynamically feed into each other across 1-hop, 2-hop, and 3-hop transitive relationships. Click any node to navigate the causal highway.

Current Traversal Path (1 Hops Traveled):
Product EconomicsRichard Ewing Canon (Original Framework)Confidence: 95%
Open Full Specification ↗

Product Debt Index (PDI)

A diagnostic score ranging from 0 to 100 that quantifies the total technical debt of a software organization in explicit dollar terms. The Product Debt Index translates abstract engineering complexity into measurable carrying costs and valuation drag. It provides a standardized mechanism for product and finance teams to measure the economic penalty of unmanaged software feature accumulation. By establishing a direct link between code entropy and financial performance, the PDI forces accountability in architectural decision-making.

Connected Tool:PDI Calculator[Diagnostic Calculator]
Launch ↗
Relationship Filter:
Hop Level 1

Direct Relationships (10)

Hop Level 2

Transitive Neighbors (Connected via Hop 1)

Hop Level 3

Extended Causal Ripple Effects

★ Canonical Research Position

Richard Ewing’s Research Thesis

We must measure software complexity in the only language the board understands: dollars.

Genesis & Intellectual Positioning

Why This Specification Exists

1. The Problem

Engineering cannot get funding to fix technical debt because executives only see new features as valuable.

2. Existing Approaches

Complaining about code quality using story points or technical jargon.

3. The Structural Gap

No shared language between engineering realities and financial oversight.

4. This Specification

A financial index that quantifies technical debt in terms of enterprise carrying cost.

Operational Realignment

What Changes If You Believe This?

Engineering

Refactoring becomes a financially justified priority.

Finance & COGS

Can accurately measure the ROI of technical debt repayment.

Product Strategy

Must account for carrying costs before proposing new features.

Security & Audit

Improved baseline quality reduces systemic vulnerabilities.

Audience-Specific Executive Guidance

Recommended Action by Role

CTO

Use PDI to defend refactoring budgets to the CFO.

Recommended Next Step →
Executable Tool[Diagnostic Calculator]

PDI Calculator

Calculates the financial carrying cost of your existing feature portfolio.

Launch Tool ↗
Freshness & Research Updates

Latest Publications & Research Activity

CIO.comFebruary 2026

Hey, Senior PMs: Shipping Faster Won’t Get You Promoted

Read Work ↗
Mind the ProductFebruary 2026

The 3 Financial Metrics Every PM Needs on Their Scorecard

Read Work ↗
Answer Engine FAQ Matrix

Frequently Asked Questions

Q:Is the PDI just a re-brand of technical debt?

No. Technical debt measures code quality; the PDI measures the financial carrying cost and enterprise valuation drag of that debt.

Q:How do you calculate the score?

The calculation involves weighing the ratio of maintenance engineering hours against new feature development, multiplied by the blended hourly cost of the engineering organization, normalized on a 0-100 scale.

01 • Origin & GenesisProvenance Record

Canonical Specification Origin

Quantifying technical debt as explicit dollar carrying costs and valuation drag on the balance sheet.

First IntroducedAugust 2026
Primary VenueCIO.com & Mind the Product
02 • Internal Research Corpusrichardewing.io

Corpus Interconnections

Richard Ewing artifacts developed around this canonical framework, including publications, execution tools, and diagnostic models.

Articles3
Tools1
Specs2
Chapters1
03A • Verified Human External EvidenceAudit Status: Baseline

External Adoption & Peer Citations

Documented instances where independent researchers, engineering teams, and publications have cited, implemented, or referenced this concept outside Richard Ewing’s ecosystem.

External Evidence: No independently verified references recorded yet.

This concept is part of Richard Ewing’s original baseline canon. External citations and implementations are added only upon rigorous empirical verification.

04 • Research Evolution & Chronology

The History of the Idea

Chronological narrative tracing the concept from first observed friction through internal tooling to external ecosystem emergence.

August 2026ORIGIN

PDI Formulation & Financial Metric Specification

Formulated the Product Debt Index diagnostic model connecting code entropy with explicit carrying costs.

August 2026INTERNAL EXPANSION

Interactive Diagnostic Calculator Released

Deployed the PDI calculator allowing product leaders to compute debt drag on a 0-100 scale.

Inspectable Evidence Ledger

Classified evidence items supporting, extending, or refining this canonical research specification.

Evidence ItemPublisherEvidence TypeStrengthRoleAction
Hey, Senior PMs: Shipping Faster Won't Get You PromotedCIO.comTier-1 Article★★★★★OriginInspect ↗
The 3 Financial Metrics Every PM Needs on Their ScorecardMind the ProductIndustry Article★★★★ExtendsInspect ↗
The Negative-Carry Code CrisisBeehiivNewsletter★★★★ExtendsInspect ↗
05 • Downstream Operational RealizationActionable Pathways

Translating Product Debt Index (PDI) into Execution

Technical debt remains isolated in engineering as story points, preventing executive intervention while compounding balance sheet liabilities. Impact: Unmanaged feature accumulation drags enterprise valuation multiples by 20-40% during M&A and due diligence.

[EXECUTIVE ADVISORY]ADVISES ON
For: PE Operating Partners & CPOs

Commission a Technical Due Diligence & PDI Audit

Retain Richard Ewing to calculate your organization’s Product Debt Index and present financial stabilization roadmaps to the board.

[EXECUTIVE ADVISORY]MEASURES
For: Engineering Directors & CFOs

Calculate Carrying Costs via Interactive Tool

Run the interactive PDI calculator to quantify technical debt carrying cost in dollars.

Note: Research specs and evidence ledgers remain independent and factual. Downstream pathways provide verified implementation channels for teams managing this operational problem.

Academic & Industry Attribution Standard

Recommended Citation

Canonical Reference String

Ewing, R. (2026). "Product Debt Index (PDI)." Richard Ewing Research Canon. Available at: https://www.richardewing.io/concepts/product-debt-index

BibTeX Citation
@article{ewing_product_debt_index,
  author = {Ewing, Richard},
  title = {Product Debt Index (PDI)},
  journal = {Richard Ewing Research Canon},
  year = {2026},
  url = {https://www.richardewing.io/concepts/product-debt-index}
}
First Origin & Provenance:Internal Research (August 2026)
Current Specification Version:Version 1.0 (Q2 2026 Baseline)