A man works at his desk unaware his shadow on the wall is the silhouette of a robot — Just a Regular Tuesday

It doesn't feel like Shadow AI. It feels like Tuesday.

AI Governance · Tech Audit Goes Deep

When Does AI Cross from Personal Productivity Tool to Shadow AI?

Governance isn't triggered by the size of a decision. Reliance is the distinction that reframes everything.

Scott Curtner, CIA, CISA | June 2026 | 7 min read

I've been wrestling with a question that sounds simple until you actually try to answer it.

At what point does using AI stop being a personal productivity tool and become something the business depends on... something that needs to be formally identified, governed, and understood?

I started where most people start. I assumed the line was drawn by impact. Big decisions... large financial consequences, significant workforce changes, high-stakes outcomes... should carry more scrutiny. Small decisions could fly under the radar. That felt intuitive. It felt reasonable.

Then I started testing it against real examples, and the intuition fell apart.


The most documented example happened at a scale that made headlines. A ProPublica investigation found that DOGE and VA officials used AI formulas and algorithms to make or inform contract cancellation decisions, cutting out meaningful input from VA career experts who understood what those contracts actually did. The AI tool reportedly relied on outdated contract versions, sometimes analyzed only the first 10,000 characters of a document (roughly five single-spaced pages), and in some cases hallucinated financial values entirely. Over 650 contracts were cancelled. Lawmakers subsequently demanded the VA Inspector General investigate the data inputs, the logic, and who gave the AI its instructions... because nobody could answer those questions.1

What made it worse was the admission from the DOGE staffer who wrote the AI code himself. Asked about the errors, Sahil Lavingia told ProPublica:2

"I would never recommend someone run my code and do what it says. It's like that 'Office' episode where Steve Carell drives into the lake because Google Maps says drive into the lake. Do not drive into the lake."

The veterans on the other end of those cancelled services couldn't get an explanation. They just got a result.

Now consider something less visible, but just as consequential in its own way. A financial institution's fraud detection team begins using an AI tool to score and rank incoming alerts, letting the system surface which cases investigators should prioritize each morning. It starts well... the tool is helpful, the team is still engaged, and human judgment is still in the room. But over time, the investigators stop reading the low-scored alerts entirely. The AI isn't assisting the workflow anymore. It is the workflow. If the model's training data was biased, if the scoring logic drifted, if the inputs were stale... nobody would know, because nobody is checking. When a regulator asks why a pattern of fraud went undetected for six months, the only available answer is the one that should never be acceptable: the algorithm didn't flag it.

No headlines. No congressional inquiry. Just a quiet, inadequately governed dependency that started out well and drifted one morning queue at a time.

Then there is the example nobody thinks to flag at all. A manager begins using an AI tool to draft performance review language for their direct reports. At first it's a time-saver... a starting point they shape with their own judgment. But gradually the edits get lighter. The manager reads, adjusts a phrase or two, and submits. The AI is now generating the documented basis for compensation and promotion decisions affecting real people's careers. No one registered the tool. No one owns the output. No one could reconstruct the reasoning if an employee challenged the assessment. It doesn't feel like Shadow AI. It feels like Tuesday.


In each of these cases, the impact was undeniable. But impact alone didn't create the problem. The problem was something else entirely.

The more I sat with these examples, the more the real distinction came into focus. It isn't about the size of the decision. It's about the role AI plays in making it.

If AI is used as one input among many... to brainstorm options, summarize information, or pressure-test thinking... and the human decision maker is still reasoning through the problem with multiple sources of evidence, then the human is in control. AI is a tool. That's personal use.

But the moment a process begins to rely on AI... when the AI is evaluating, scoring, ranking, or materially driving the outcome, and the human couldn't reconstruct the reasoning without it... something fundamental has shifted. The AI is no longer supporting the decision. It is the decision. And if that's happening in a structured, repeatable business context, it needs a name, an owner, documented inputs, and a human being who can stand behind it.

So what is the actual trigger? What separates personal AI use from Shadow AI that requires formal governance?

The Insight

Governance isn't triggered by consequence. It's triggered by dependency.


This matters beyond policy and compliance. I've become increasingly interested in what it actually looks like to build AI systems that take this seriously from the ground up... systems with narrow, well-defined scope, verifiable outputs, documented data lineage, and logic that a human can interrogate and explain. Not AI that operates as a black box and asks for trust. AI that earns accountability by making its reasoning visible.

That's a harder problem than it sounds. But it's the right problem to be working on.


When no human owns the decision, no human owns the consequence. And right now, there are decisions being made where nobody up and down the org chart could tell you why.

That's not an AI problem. That's a governance problem. And it starts with knowing where the line is.

Sources

  1. The VA contract cancellation story was reported across multiple outlets:
  2. The Lavingia quote is sourced directly from ProPublica's reporting and corroborated across three outlets:

Connect

Let's talk technology audit

Questions about this article, the tools I used, or just want to connect? Find me on LinkedIn.

Connect on LinkedIn

← Back to scottcurtner.com