Technical debt
The accumulated cost of structural and code quality decisions that prioritized short-term convenience over long-term maintainability. Structural technical debt in a robotics codebase specifically refers to wrong package boundaries, undeclared coupling, duplicated logic, and naming inconsistencies that slow down every future development activity. Like financial debt, it accrues interest: a small debt at month one is a large debt at month twelve.
Defined in 4 GAGE programs, which carry 5 distinct definitions of it. The wording above is taught in Foundations of Robotics and Physical AI.
How each discipline defines it
The same term does different work depending on who is using it. These are the definitions as each program teaches them, unedited.
The accumulated cost of structural and code quality decisions that prioritized short-term convenience over long-term maintainability. Structural technical debt in a robotics codebase specifically refers to wrong package boundaries, undeclared coupling, duplicated logic, and naming inconsistencies that slow down every future development activity. Like financial debt, it accrues interest: a small debt at month one is a large debt at month twelve.
The accumulated cost, usually paid in slower future engineering work, of choosing a faster, less complete solution now over a more thorough one, with the implicit or explicit intention of improving it later. A concept popularized by Ward Cunningham in the early 1990s, and the direct conceptual source for process debt in this topic.
The accumulated cost of past shortcuts (integration, data, infrastructure, and process debt). For AI it is prioritized by impact on AI rather than general IT health, then contained, repaid incrementally, modernized opportunistically, or strategically replaced.
The future cost incurred by choosing the fast, expedient option now rather than the right one; coined by Ward Cunningham in 1992, where the "interest" is the compounding extra effort every later change requires.
the accumulated cost, in money, time, and risk, of systems built or maintained in ways that make future change harder. Like financial debt, it charges interest: every AI initiative pays it until you address the principal.
Where it is taught
The exact lessons this term appears in. The first module of every program is free with a free account.
- AI Workflow Design Fundamentals and Preventing Technical Debt · Practical AI Workflow Design and Prompt Engineering, Certified AI Practitioner: Workplace Foundations
- Enterprise Integration Strategy · Technology, Platforms and Vendors, Certified AI Transformation Professional (CATP)
- Legacy System Transformation and Technical Debt · Technology, Platforms and Vendors, Certified AI Transformation Professional (CATP)
- Structuring a robot codebase so it stays manageable · Software Engineering and Team Workflow, Foundations of Robotics and Physical AI
- Engineering responsibility without slowing the build · Responsible Physical AI in Practice, Engineering Judgment and Professional Formation
Where it shows up at work
A definition is where Technical debt starts. The lessons above teach it inside the competencies below, which are what job descriptions ask for and what the GAGE credential records. Every link here is drawn from the same careers map that builds a role's readiness check.
Briefs a model like a good manager: context, constraints, examples, verification, and knows when to stop delegating.
One lesson on this page teach it as a primary outcome.
Designs role-based AI training that measures skill, not attendance, with approved-use guidance, office hours and communities of practice.
One lesson on this page teach it as a primary outcome.
Decides where AI should be used, where it should not, and which use cases create measurable value, tied to the organization's priorities.
One lesson on this page teach it as a primary outcome.
Roles that hire for it
Each role page shows the full competency set, what the seat decides, and a readiness check against your own evidence.
- AI Literacy Leadneeds it at depth
- AI Adoption and Enablement Leadneeds it at depth
- Chief AI Officerneeds it at depth
- Responsible AI Leadneeds working knowledge · 7 open postings this week
- Chief Information Officer, technology leadership editionneeds it at depth
- Chief Technology Officer, AI engineering editionneeds working knowledge
How job descriptions say it
Postings rarely use the textbook word. These are the phrases the careers map reads as asking for the competencies above.
Where the frameworks place it: EU AI Act Article 4; DOL AI Literacy Framework.
One interview question about it
Describe a workflow you redesigned around an AI tool. What did the prompt have to contain for the result to be reliable?
Asked of candidates for prompting and workflow design with ai. Answering it in your own words is exactly how a GAGE topic is passed, and the credential records the pass where an employer can check it.
If you come from another field
Some backgrounds already carry this competency, and the readiness check gives credit for it.
- A computer science or software engineering degree carries it as work you can show: Prompting and tool workflows are already in your daily work.
- Human resources and people operations carries it as a claim to back up: Training design and delivery are part of the function.
- Operations, claims, customer service and administration carries it as a claim to back up: Onboarding and job aids are training design.
Terms it appears with
Not an alphabetical neighbourhood: these are the terms taught in the same lessons, ranked by how often they appear together.