Short answer
Technical debt management assesses how technical constraints are evidenced, prioritized, and reduced according to delivery or operating impact.
About Technical debt management
The ability to identify, prioritize, and reduce technical constraints that impede safe delivery, maintenance, or operation.
Use this competency for
- Roles responsible for evolving code, systems, tooling, or operating practices over time.
- Functions where accumulated constraints affect change cost, defects, or service operation.
Do not use this competency for
- Work with no ownership of technical assets or influence over their future change.
Important distinctions
Code quality
Code quality assesses specific code and review standards. Technical debt management prioritizes accumulated constraints across competing work.
Delivery planning
Delivery planning sequences an outcome. Technical debt management decides which existing constraints warrant investment and how to reduce them safely.
Expectations by level
IC1
Individual contributor 1
Identifies a bounded technical constraint with guidance, records its impact, and improves it when the change fits the assigned scope.
Observable behaviors
- Links a debt item to repeated work, risk, or failure evidence.
- Avoids expanding a scoped fix into unrelated cleanup.
- Leaves the touched area no harder to change than before.
Examples
- Recorded a repeated manual step with examples and added a focused automation task.
- Removed an obsolete branch while changing the same module and confirmed no callers remained.
IC2
Individual contributor 2
Independently prioritizes and reduces debt in a team-owned area, balancing current impact, change risk, and delivery needs.
Observable behaviors
- Compares debt work using observable cost or risk.
- Chooses an incremental reduction path for a risky constraint.
- Checks whether completed work reduces the stated impact.
Examples
- Sequenced replacement of a shared library behind an adapter instead of pausing feature work.
- Prioritized a slow deployment step after measuring the engineer time it consumed each week.
IC3
Individual contributor 3
Sets debt reduction direction across teams for constraints with shared ownership and creates decision rules that keep investment tied to evidence.
Observable behaviors
- Builds a cross-team view of constraints and affected outcomes.
- Defines ownership and safe stages for shared debt reduction.
- Retires debt items when evidence no longer supports the cost.
Examples
- Coordinated removal of a legacy interface through compatible stages owned by several teams.
- Created quarterly debt criteria based on incident risk, delivery delay, and maintenance effort.