Governance by Lockdown Is Not Governance

Why Restricting AI Creates the Exact Problem You Were Trying to Prevent

Why Restricting AI Creates the Exact Problem You Were Trying to Prevent

When AI tools started showing up in enterprise workflows, the response from IT and legal departments followed a predictable sequence. Assess what employees are using. Identify what has not been approved. Block it at the browser or network level. Then wait for the approved tooling to catch up to the problem. That response makes sense on paper. The risks of unvetted AI tools are real: consumer AI products may train on what you feed them, compliance obligations around data handling are still evolving, and the liability questions are still being sorted in courtrooms. Caution was warranted. But there is a critical difference between caution and prohibition. And blanket prohibition has a failure mode that is worse than the risk it was designed to address. When you block AI tools without providing a sanctioned alternative, employees do not stop using AI. They route around you.

The Scale of What’s Happening Underground

This is not a fringe behavior at the edges of the workforce. It is the default response of most employees in organizations with restrictive AI policies. A 2026 PagerDuty survey of office professionals found that two-thirds of respondents, 66 percent, had used unauthorized AI tools at work in spite of explicit organizational policy. When Kong surveyed employees at companies with AI restrictions, 60 percent said they either ignored those restrictions or found ways around them. Twenty-six percent used personal devices. Another 24 percent used alternative browsers or technical workarounds to reach tools that were blocked. This pattern has a name: shadow AI. It refers to the unsanctioned use of AI tools without IT oversight, approval, or monitoring. It includes AI platforms accessed on personal email accounts, AI extensions installed outside enterprise device management, and AI features embedded in SaaS products that IT never noticed when the original tool was approved. Shadow AI governance, or the absence of it, is the problem most organizations are actually managing right now. Most of them do not know it.

The Visibility Trap

Here is what makes the lockdown approach so counterproductive. The premise of blocking AI tools is that it prevents risk. But once an employee is using AI on a personal account, via a personal device, outside any enterprise monitoring, you have not prevented the risk. You have made it invisible. The data being fed into that unmanaged personal AI account is the same sensitive data that would have gone into the approved tool. The difference is that now there is no audit trail, no visibility, no ability to respond when something goes wrong. There is also no way to know what went wrong until long after the fact. The organizations that experience the worst shadow AI outcomes are not the ones that tried to deploy AI tools and struggled to govern them. They are the ones that enforced prohibition confidently, assumed the problem was solved, and discovered eighteen months later that their employees had been routing work through personal AI subscriptions the entire time. Lockdown does not eliminate the risk. It relocates it to a place where you cannot manage it. This is the pattern that distinguishes productive friction from friction that only creates blind spots. Productive friction develops people or protects something real. A blanket prohibition without a sanctioned alternative is friction that builds nothing and protects nothing it claims to protect, because the risk moves rather than disappears. If you want to understand the difference between friction that does something and friction that just relocates risk, The Friction Discernment Test is worth reading alongside this.

What We Hear From Leaders in Regulated Industries

In conversations across our executive network, we hear a version of the same story with some consistency. A leader describes their organization’s AI policy: robust browser blocks, no approved enterprise tools yet, a security review queue for every new request, no exceptions while the official guidance catches up to the market. They describe it as a thoughtful, cautious approach. This is the policy as designed. Then, almost in the same breath, they describe what they are personally doing. Finding a workaround for a corporate chat tool so restricted it was functionally unusable. Running a personal AI subscription against their work email because the approved options could not meet the actual demand on their time. Quietly advising colleagues in their network to do the same. These are not bad actors. They are experienced, senior leaders in regulated environments who understand what AI can do and who have assessed the cost of being locked out of it. They know their organization’s risk posture better than most. And they are routing around the restrictions anyway, because the policy created an unworkable situation and offered no legitimate alternative. What they are describing is the rational response to an inadequate governance model. Shadow AI governance fails when the governance conversation is only about restriction. The person who has determined that AI will materially improve their work, and who has found every legitimate path to using it blocked, will find an illegitimate one. You have not addressed the underlying behavior. You have only ensured that it is invisible to you.

Shadow AI Governance That Actually Works

The organizations managing AI risk well are not the ones with the strictest restrictions. They are the ones with the most deliberately scoped allowances. The difference is not permissive versus restrictive. The difference is between undefined and defined. Broad prohibition without a sanctioned alternative is not a governance stance. It is an abdication that presents itself as caution. A policy that says employees may not use unsanctioned AI tools tells people what they cannot do but gives them no legitimate path to what they actually need to do. The behavior that follows from that policy is predictable. Shadow AI governance that works specifies what is allowed, at a level of practical detail. Not a vague principle but a working policy: these tools, for these purposes, with these constraints on what data may be included. That sentence creates a perimeter. A perimeter is something that can actually be managed, because it is defined. Within that defined perimeter, effective organizations run pilots before they scale. They do not deploy AI organization-wide on day one. They pick one function, define one use case, instrument it to understand what happens, and study what results. The pilot is both the safeguard and the evidence base. Real risks materialize in a controlled pilot, where they can be managed. Real capability becomes visible in the pilot, which builds the case for expanding access responsibly. The third element is the one most organizations skip, and it is arguably the most important: share the AI’s synthesis back to the group before discussion begins. One of the dynamics that sustains shadow AI behavior is that employees getting value from unauthorized tools have no legitimate channel to demonstrate that value. The knowledge stays private. The tool stays underground. The organization never develops a shared practice, because all the learning is happening in invisible individual silos. When organizations make AI synthesis visible in a room, when the tool’s output gets shared with the group as a starting point for discussion rather than a finished answer, the behavior that was happening underground becomes observable. The organization begins to develop a collective AI practice. Employees who were routing around restrictions find that the legitimate channel can provide the value they needed. And the organization gains visibility into what AI is actually producing, which is the only foundation on which real governance can be built.

Starting From the Right Question

Most AI governance conversations start with “what are we afraid of?” That impulse is understandable. The exposure from unmanaged AI use is real: researchers have found that 93 percent of employees admit to inputting confidential data into unapproved AI tools, including source code, customer records, financial projections, and legal documents. The compliance implications under GDPR, HIPAA, and similar frameworks are not hypothetical. But a governance conversation anchored in fear produces lockdown governance. And lockdown governance, as the evidence makes clear, addresses the fear while relocating the actual risk. The more productive question is: what would it take for employees to have legitimate access to AI tools that work well enough that they do not need workarounds? That question leads somewhere useful. It leads to defined allowances, scoped pilots, and visible behavior that the organization can actually measure and manage. The accountability argument matters here too. As we explored in the context of the Air Canada chatbot case and the iTutorGroup EEOC settlement, AI does not absorb organizational accountability. When something goes wrong, a decision made on an incorrect AI output, a sensitive document processed by a consumer tool with no enterprise controls, the organization remains responsible. That logic runs in both directions. You cannot hold people accountable for AI outputs they were never permitted to produce legitimately. And you cannot manage risks you have driven underground.

How to Start Building Shadow AI Governance

The first step is an honest audit. Before your organization defines its shadow AI governance stance, find out what AI is actually being used. Not what has been officially approved. What is actually running, including personal accounts, browser extensions, and AI features in tools you have already licensed. This conversation produces uncomfortable findings in most organizations. Leaders are often surprised by the gap between their stated policy and what is actually happening. But it is the only foundation for a governance framework that will hold, because governance built on a fictional baseline produces fictional outcomes. From that honest accounting, the work is definitional: specify what is allowed, for what purpose, with what constraints on data handling. Run a pilot in one function. Bring AI synthesis into the room, into the actual meetings where decisions get made, before discussion begins. Watch what happens. Adjust. That sequence, audit then define then pilot then share back, is shadow AI governance that works. It is not permissive. It is precise. And precision is what makes governance governable.

The Illusion of Control

The organizations that handle AI risk well are not the ones that banned everything first and asked questions later. They are the ones that understood what employees actually needed and built a framework capable of providing it under real conditions. Lockdown feels like control. It creates a clear line, a firm policy, a documented stance. But if employees are routing around it on personal accounts, using personal subscriptions against their work email, outside any monitoring, you have neither prevented the risk nor gained any ability to manage it. That is not governance. That is the appearance of governance. And it is more dangerous than no policy at all, because it convinces the organization that a problem has been addressed when it has actually been made worse. Real shadow AI governance starts with honesty about what is already happening. From there, the path is specific allowances, observable pilots, and AI practice that is shared rather than hidden. Not broader prohibition, not unlimited access, but defined and visible use that your organization can actually see and manage. The difference between those two approaches is not how much risk you are willing to tolerate. It is whether you can see the risk you have. Want to explore what an AI governance model that works looks like for your organization? Voltage Control’s AI transformation programs help leadership teams design AI practices that are both usable and manageable. Learn more about our approach.