From Technical Debt to Cognitive and Intent Debt: Rethinking Software Health in the Age of AI

From Technical Debt to Cognitive and Intent Debt: Rethinking Software Health in the Age of AI

Generative AI is dramatically accelerating the velocity of software development, enabling small teams to ship features at a pace that would have seemed implausible just a few years ago. I saw this firsthand in an entrepreneurship course I taught recently. Student teams were building software products over the semester, moving quickly to ship features and meet milestones. By week eight, one team hit a wall. Simple changes were breaking things in unexpected places, and progress had stalled. When I met with them, they initially blamed technical debt: messy code, hurried implementations, architectural shortcuts. But as we dug deeper, a different problem emerged. No one on the team could explain why certain design decisions had been made, or how different parts of the system were supposed to work together. The code might have been messy, but the deeper issue was that the team's shared understanding, the theory of the system, had quietly fragmented. They had also failed to write down or communicate the rationale behind decisions. They had accumulated cognitive and intent debt faster than technical debt, and it had paralyzed them.

This is not an isolated story. Generative AI does not remove the challenges of software engineering; it redistributes them. In this article, I propose a triple debt model for reasoning about software health, built around three interacting debt types: technical debt refers to problems in the code layer, cognitive debt refers to erosion of shared understanding across a team over time, and intent debt refers to a lack of externalized goals, constraints, and rationale that both humans and AI systems need to work safely and efficiently with the codebase. Technical debt makes systems harder to change. Cognitive debt makes systems harder to understand. Intent debt makes it difficult to know what the system is actually for.

The Hidden Cost of AI-Generated Code

For years, software engineers have worried about technical debt, the long-term cost of messy code that accumulates and compounds when teams prioritize speed over quality. But generative AI may be quietly shifting where the real risk lies. Today, AI systems can generate code faster than developers can read or understand it, and as those models improve, the systems show growing promise for reducing debt through automated refactoring, test generation, and automated code review. That is, generative AI may reduce technical debt while simultaneously accelerating the accumulation of cognitive and intent debt. Organizational expectations for rapid productivity gains, without corresponding investment in learning support, can create a paradoxical effect where developers lack the time to develop the understanding that would actually save them time.

The code may work. It may even be well-architected. But the team may not adequately understand how it works or remember why it was built the way it was. Over time, the shared understanding that makes a software system safe to change quietly erodes. This gradual loss of understanding increases cognitive debt, while the loss of captured rationale leads to intent debt. In AI-assisted development, cognitive and intent debt may quietly become the risks that matter most.