You can damage an engineering culture in the name of AI — and then wonder why the AI work keeps getting worse.
There is a failure mode I have watched play out more than once, and the current AI push is making it common again. Leadership decides the organization must be "AI-first." Reasonable. Then it enforces that through pressure: mandated tool usage, activity tracking, performance signals tied to how much AI you visibly use, less autonomy over how the work gets done. The dashboard lights up. More AI "activity" everywhere. And the actual engineering quietly gets worse.
The reason is not mysterious. Strong engineering has never run on compliance. It runs on agency, clarity, and ownership — on people who feel safe enough to say "this automation is making the system worse" and senior enough to be heard. The moment AI adoption is wired to fear of looking insufficiently modern, you lose exactly that. You get engineers performing AI use instead of exercising judgment, and judgment is the thing you actually needed AI to free up.
This is the part leaders miss: AI does not replace your engineering culture, it runs on top of it. A weak, low-trust culture does not become high-output because you added agents. It becomes a faster way to ship things nobody owns. The tooling amplifies whatever operating conditions were already there — good or bad.
So the real adoption question is not "how do we get everyone using AI." It is "are the conditions under which good engineering happens still intact after we did." If the rollout traded away trust and ownership to buy visible activity, that is not transformation.
If your AI rollout quietly destroyed the culture that made good engineering possible, you did not transform the org. You just put an AI label on organizational debt.