Table of contents
Ask a US employee whether their own employer has rolled out AI. A decent share of them cannot answer, and shadow AI grows in exactly that kind of confusion.
Gallup changed the question because of it. The methodology note says, “Starting in Q3 2025, Gallup added a ‘don’t know’ option to this question to capture uncertainty about AI adoption.” Results from Q3 2025 onward are no longer directly comparable with earlier measurements.
A polling company broke its own time series because too many people had no idea what was happening inside the building they work in.
The second number nobody quotes
As of May 2026, 47% of US employees say their organization has implemented AI. Only 25% say the organization communicated a clear plan.
Every headline takes the first number, but the second one is the story.
Between “we have this thing” and “somebody told me how to use it” sits a gap, and in that gap are contracts, patient records, draft tenders, source code, whatever your people happen to be pasting today.
Shadow AI is the default state of that gap.
Adoption is the wrong argument
There is a long running fight about how many people use AI. Gabriel Weinberg of DuckDuckGo summed up the skeptical side in June 2026 as “one third actively using AI, one third occasionally using AI, and one third never using AI”. He cites Microsoft telemetry putting it at “more than 30 percent of the US working-age population is using AI, an increase of 3 percentage points from the end of 2025”.
Gallup’s workplace numbers run higher. 15% of US employees use AI daily. Weekly or more is 30%, and 52% touch it at least a few times a year.
Pick whichever camp you like, it changes nothing for my job.
Move the user base up or down, the 25% who got a clear plan stays where it is. That fight pulls attention away from the only question that matters, which is who wrote the rulebook and who read it.
Shadow AI is a confidentiality problem with no attacker
Strip the vocabulary and that is all this is.
No phishing mail, no exploit, no command and control, nothing that trips an alert. An employee opens a browser tab and pastes a client document into a chatbot to get a summary. The data leaves the organization. Most of what you bought assumes somebody is trying to break in. Shadow AI walks out the front door during working hours, moved by people who just want to finish faster.
OWASP keeps an entry for sensitive information disclosure in its Top 10 for Large Language Model Applications, and almost all of that guidance assumes an application you built. The tab your sales team opened this morning is nobody’s application.
Scott Brinker named the shape of this back in 2013 and called it Martec’s law. Technology changes exponentially, organizations change logarithmically. Your staff adopted AI in an afternoon, your document set moves at the speed of a committee.
The Gallup manager numbers show the same thing from the other side. 36% strongly agree their manager supports the team using AI. Where that support exists, employees are 1.7x more likely to use AI weekly or more and 8.7x more likely to report a transformational change in how they work. Encouragement travels by conversation and rules travel by document. Shadow AI takes the faster route.
What shadow AI looks like on a Tuesday
Nobody sits down and decides to run shadow AI. It shows up as small, reasonable moves.
A sales rep pastes a signed contract into a chatbot to pull the renewal dates out of it. An HR assistant drops a salary spreadsheet into a chatbot to reformat the columns. A developer sends a stack trace holding a production connection string to a free tier account. A clinic receptionist rewrites a referral letter with the patient name still in it.
None of those people are careless. All of them were told AI makes them faster, and none of them were told where the line sits.
Deleting the client name before pasting does not turn the text into anonymous data either, and I went through the research on that in ChatGPT privacy leak.
Every one of those actions is invisible to the security team, because nothing was breached and nothing alerted.
Low numbers are not safe numbers
Daily use runs at 42% in technology, 27% in finance, 22% in professional services, and 9 to 15% everywhere else.
Read the low end carefully, because a law firm or a clinic sitting in that bottom band is not in a better position. It is a place where a smaller group does the same thing with far more sensitive material, and with less chance that anyone in IT has ever looked at it. Low usage hides shadow AI.
The 65% of employees in AI-implementing organizations who report a positive effect on productivity are not lying either. It works, and that is exactly why nobody is going to stop when you ask them to. A ban moves shadow AI further out of sight.
One page before you buy anything
Do not start with a tool. Start with one page that answers four things.
- Which categories of data never go into an external model.
- Which tools are approved, listed by name.
- Who an employee asks when the answer is not obvious.
- What happens when something has already gone in, and who hears about it first.
That page will not cover a regulated environment or replace a contract with the vendor. It covers what is leaking today.
I keep the editable template for it behind my shadow AI risk calculator, so you do not have to start from a blank file.
Then do the boring part and send it to everyone, with one person named as the owner. A rule nobody can find works the same as no rule at all, and that is where shadow AI restarts. It is not fancy work and it does not need a consultant.
One page beats a procurement cycle. If you cannot write it, you do not have an AI program, you have 47% and hope.
So remember, if you write only one line on that page, write this one. Never put anything into an LLM that you would not email to a stranger.
Source: https://www.gallup.com/699797/indicator-artificial-intelligence.aspx
