AIToday
Zenn AI/MLPublished: Nov 16, 2026, 16:00 JST

和田 卓人: AI code brings 認知負債 and 意図負債 to teams

Send on LINE
和田 卓人: AI code brings 認知負債 and 意図負債 to teams

3 Key Points

  1. What happened

    At TechLead Conference 2026 Autumn, 和田 卓人 said AI has not removed problems but relocated them — adding 認知負債, where a team's shared understanding erodes as AI-generated code skips the mental models built by hand-coding, and 意図負債, missing rationale that AI fills in on its own.

  2. Why it matters

    Because this debt never surfaces in the code itself, organizations and individuals chasing productivity can become unwitting accomplices, leaving understanding behind while code keeps being generated — and checking comprehension via plan mode or AI-made explainer HTML can breed false confidence, since people accept wrong explanations.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Context & Analysis

The talk reframes a familiar worry about AI and code. Technical debt is visible in the codebase; 認知負債 and 意図負債 are not. 和田 argues that when writing code by hand was unavoidable, understanding came as a free byproduct — and now that byproduct has stopped appearing, so understanding has to be designed into the process on purpose.

That is why his prescriptions focus on routines rather than tools. Having people explain their reasoning out loud — the プロトジェ効果, where teaching deepens the teacher's own learning — is presented as the most reliable way to measure understanding. The author's team had already started a weekly review meeting for exactly this, and left the conference reassured the direction was right.

The context is a broader split the conference traced: as AI speeds up writing, researching, and deciding, what remains with humans is understanding, deciding, and building with others. 和田's session covers the first of those; the other two sessions took up decision-making and co-creation.

FAQ
What exactly are 認知負債 and 意図負債?
認知負債 is a team's shared understanding breaking down over time — the mental models once built by writing code by hand disappeared along with that process. 意図負債 is the absence or loss of the rationale, goals, and constraints behind a decision; AI, unaware of human context, fills in the gaps itself.
Why is 認知負債 described as the hardest to fix?
Because it does not show up in the code, so it is invisible. Organizations and individuals focused on productivity can become accomplices, generating code while leaving understanding behind.
Does 和田 卓人 recommend banning AI for junior engineers?
No — he says it is not a two-way choice between banning AI and letting juniors use it freely. Teams should separate where AI is used from where it is not, and explain the reasons.
Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Next articleThailand GDP grows 2.9% on AI-related exports