
transcript
show notes
Sometime in 2026 the phrase shadow AI quietly changed its meaning, and almost no one marked the change. For two years it meant an employee pasting company information into a chatbot nobody approved. Now it means something with hands: an unapproved autonomous agent, running under a real employee's login, with permission to reach into systems and take actions that do not undo. The words stayed the same. What they point at grew a body.
This episode opens the comfortable belief that shadow AI is a discipline problem you solve with a ban and a blocklist. It is not. A ban does not stop the behavior. It removes your ability to see it. Shadow AI is a demand signal, a remarkably clear one: when half your workforce reaches for a tool you never sanctioned to do the job you did give them, they are telling you precisely where the distance between what you ask and what you provide has grown too wide. People route around that distance. They always have. The urge is one of the oldest in working life, and it predates anything intelligent: personal email moving files a clumsy system could not, banned file sharing spreading one invitation at a time, the quiet spreadsheet macro that ran a critical process for a decade. Technology people call it shadow information technology. What has changed, twice, is what the shadow contains.
The first change was the chatbot: a conversation your data flowed through, out of your walls, into a model you did not run. Harder to see than installed software, but with a ceiling on the damage, because a chatbot only ever leaks. The second change removes that ceiling and is the one almost no governance framework has caught up to. The shadow thing is no longer a conversation. It is an actor. An employee no longer pastes information into a model; they stand up an agent, give it a task and a set of borrowed permissions, and let it run. Now the shadow books, sends, moves money, changes records and emails customers, at machine speed, on one person's convenience and nobody's review. And the part that should hold your attention: a shadow agent runs as the person who built it. It borrows their identity. So the record does not say an agent did this. It says a person did. Your whole apparatus for knowing who did what quietly stops being able to tell a human decision from a machine one taken in that human's name.
Then the thread. Why do capable, honest people bring an unapproved actor into serious work? Not laziness, not rebellion. People take the path of least resistance toward doing the job well, and that is close to the definition of competence. The shadow path is only easiest when the sanctioned path is worse. The urge to automate is pressure, and pressure is neutral: it pours through whatever gap you leave, whether the gap leads somewhere safe or somewhere catastrophic. What is new is that for the first time the thing pressure carries through the gap is an actor, not a tool: a worker you never hired, running under a badge that isn't its own. The workforce can now grow without anyone hiring anyone.
The honest read: the answer is not a bigger blocklist, which is a bet you lose every quarter. The only thing that empties a shadow is a sanctioned path that is genuinely the easier one to walk. For agents that means an approved way to stand one up that is faster than the smuggled way, an agent that runs as itself rather than as an employee, observable and logged by default, with a clear line around what it may do alone and where a person has to say yes. Make the trustworthy path the path of least resistance, or keep forbidding the alternative and make sure no one is watching the actor work.