Debt Severity Rubric¶
Classification rubric — instantiates Technical Debt Containment
A fixed scoring scheme that ranks each debt item by risk, reversibility, dependency breadth, and compounding potential, so repayment attention flows to the highest-drag debt rather than the easiest.
A list of debt tells you what exists; it does not tell you what to fix first. Debt Severity Rubric is the reproducible scoring scheme that answers that question, mapping each item's attributes — blast radius, reversibility, how many things depend on it, how fast its cost compounds — onto a severity tier and a repayment rank. Its defining move is making judgment consistent and drag-aligned: two people scoring the same item with the same rubric should land in the same tier, and the ordering that results should track how much future capacity an item is quietly eating, not how quick or pleasant it would be to clean up. It is a rule, not an inventory and not a live meter — it operates on items someone else has already listed, and it converts them into a defensible priority order.
Example¶
A research organization runs on a sprawling internal knowledge base: hundreds of wiki pages, undocumented analysis assumptions, and stale onboarding guides — classic knowledge debt. Everything is "worth fixing," so nothing decisive gets fixed. They build a severity rubric with four scored dimensions: reliance (how many people depend on the page), staleness cost (how wrong it now is), compounding (does its rot breed further rot, e.g. new hires copying an outdated method), and reversibility (how hard to reconstruct if lost). A stale "how we compute the headline metric" page scores high on every dimension — many rely on it, its errors propagate, and the original author has left. A stale set of old meeting notes scores low. The rubric reorders the cleanup queue so the high-drag pages are repaid before the next onboarding wave, instead of whoever happened to file the loudest complaint.
How it works¶
The rubric fixes a small set of scoring dimensions, a scale for each, and a rule for combining them into a composite severity and a rank. The craft is in the anchors: each score point carries a concrete descriptor ("dependency breadth: 3 = more than five downstream consumers") so that scoring is reproducible across raters and across time, rather than a vibe. Because severity by itself is not the same as urgency, the rubric folds in the forward-looking factors the archetype calls for — upcoming change to the affected surface, compounding rate, opportunity cost — so the output is a repayment ordering the review can act on, not just a static hazard label. What distinguishes it from ad-hoc triage is exactly this repeatability: the same inputs yield the same rank, and the rule can be inspected and argued about openly.
Tuning parameters¶
- Dimension set — which factors are scored (risk, reversibility, dependency breadth, compounding, safety). More dimensions capture nuance but slow scoring and invite double-counting.
- Weighting — how heavily each dimension counts toward the composite. Weighting toward compounding pushes structural debt up; toward blast radius pushes widely-shared debt up.
- Tier count — two or three coarse bands versus a fine numeric scale. Coarse tiers are fast and defensible; fine scores imply a precision the inputs may not support.
- Anchor specificity — how concretely each score point is described. Tighter anchors cut rater disagreement but take effort to write and maintain.
- Recalibration cadence — how often the rubric and its weights are revisited as the system and its risks shift.
When it helps, and when it misleads¶
Its strength is that it directly defeats the archetype's cleanup-capture-by-easy-items failure mode: by scoring drag rather than convenience, it stops trivial tidy-ups from crowding out the high-compounding debt that actually matters. It also makes prioritization arguable in the open — disagreements move to "is this really a 3 on dependency breadth?" rather than to whose project is favored. A well-known real analogue is the Common Vulnerability Scoring System (CVSS), a standardized rubric that turns heterogeneous security flaws into comparable severity scores.[n1]
Its failure mode is false precision and gaming. A composite number invites people to treat a 6.8 as meaningfully worse than a 6.4 when the underlying scores are rough, and once scores drive funding, they get argued toward — inflating a favored item's dependency breadth to jump the queue. Rubrics also drift: the weights that fit last year quietly mis-rank this year's risks. The guarding discipline is to keep the rubric simple, calibrate raters against shared examples, periodically audit a sample of scores for consistency, and treat the rank as an informed argument to be pressure-tested, not an oracle.
How it implements the components¶
severity_classification— the rubric is precisely this: the scheme that assigns each item a severity tier from its scored attributes.repayment_priority_rule— by folding in compounding, upcoming change, and opportunity cost, the rubric outputs the ordering that decides which debt is repaid first.
The rubric scores items but does not store them — the inventory is the Technical Debt Register, its nearest twin (the register lists what the rubric ranks) — and it does not measure live drag: interest_or_drag_signal and debt_service_ratio are the Debt-Service Dashboard.
Related¶
- Instantiates: Technical Debt Containment — the rubric turns a flat inventory into a drag-ordered repayment queue.
- Consumes: Technical Debt Register — it scores the items the register holds.
- Sibling mechanisms: Technical Debt Register · Debt Budget Review · Debt-Service Dashboard · Architecture or Process Decision Record · Quality or Health Scan · Repayment Reserve · Sunset or Replacement Plan · Exception Expiry Date · Refactoring or Cleanup Sprint
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Debt Severity Rubric operates as a non-executable information artifact that externalizes static or prospective structure because it a fixed scoring scheme that ranks each debt item by risk, reversibility, dependency breadth, and compounding potential, so repayment attention flows to the highest-drag debt rather than the easiest.
Independent corroboration: The frozen evidence defines Debt Severity Rubric as 'A fixed scoring scheme that ranks each debt item by risk, reversibility, dependency breadth, and compounding potential, so repayment attention flows to the highest-drag debt rather than the easiest', so its operative form is Representation, Specification & Plan.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Computer Science & Software Engineering
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Software maintenance practice cohered prioritization of technical-debt items by blast radius, reversibility, dependency load, and compounding remediation cost.
Related originating lineages:
- Organizational & Management Science — Risk and portfolio management supplied reproducible scoring tiers and repayment ordering.
- Security Studies & Intelligence Analysis — CVSS supplied a published exemplar for turning heterogeneous technical attributes into comparable severity bands.
Review resolution: Software maintenance practice cohered prioritization of technical-debt items by blast radius, reversibility, dependency load, and compounding remediation cost.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] The Common Vulnerability Scoring System is a widely used, published rubric that maps a software vulnerability's characteristics (attack vector, impact, exploitability) onto a numeric severity and qualitative band. It is a real-world exemplar of standardizing severity judgment so heterogeneous items can be ranked comparably — the same job a debt severity rubric does for debt. ↩