Sit in on almost any corporate conversation about AI and you'll hear the same unspoken assumption. Someone proposes using AI for a piece of work, and the room quietly pictures it running unsupervised: no human ever checks the output, nothing measures whether it's any good, and there's no way to catch a mistake before it spreads. Nobody says it out loud, but the line between "AI helps with this" and "AI does this on its own" is never drawn.
With the line undrawn, the risk feels unbounded. And when nobody can say what's being approved, the safest move is to approve nothing. The proposal goes to a steering committee, the steering committee asks for more analysis, and months later the company is still doing nothing.
The problem isn't that people are too cautious. It's that they're picturing the most autonomous version of every idea, because there's no shared vocabulary for the versions in between. Every AI decision gets treated like a Level 5 decision.
That causes three predictable problems:
-
You can't set milestones.
If the only options are "no AI" and "AI does everything," there are no steps in between to plan, fund or celebrate.
-
You can't estimate cost or complexity.
Letting an AI draft a spec and letting an AI deploy to production have wildly different engineering costs. Lumped together, both look expensive and scary.
-
You can't size the security risk.
Read-only help with a draft and write access to production deserve different reviews. When everything is reviewed as the worst case, low-risk work stalls and real risks get the same attention as trivial ones.
The auto industry ran into this exact problem more than a decade ago, and it solved it. We can borrow the solution.




01




