Shadow AI Explained: The AI Tools Your Company Cannot See

Business Pill · The AI you cannot see

Shadow AI is staff using AI tools the company has not approved, and cannot see. A ban does not remove the need. It removes the visibility.

A short explainer video, under a minute. The company, the employee and the chatbot are an illustration.

At a glance

The Short Answer

Picture a company that bans AI tools. Problem solved, says the memo.

At her desk, an employee has forty contracts to summarize by Friday. She opens a chatbot on her own phone and pastes them in.

What Shadow AI Is

That is called shadow AI: staff using AI tools the company has not approved, and cannot see.

The employee is not breaking the memo out of spite. She is doing the work.

What the Ban Changed

In short: the need is still there, the visibility is gone, and company data now sits on personal accounts.

The ban did not remove the need. It removed the visibility. The work still goes through AI, now with company data and no record.

The Idea in Parts

The Fix

The fix is rarely a stricter ban. It is an approved tool, good enough to use, and clear rules about what may go into it.

Why It Matters

The video turns this into one question: what are our people already using that we cannot see?

People use what helps them work. Give them a safe way, or they find their own.

Where This Shows Up in AI Business Today

The Business Engineer Lens

Where this idea sits in the Business Engineer library:

Related Business Pills

All Business Pills

• The Memory Wall: Why a Faster AI Chip Is Not Faster AI
• Tokens per Watt: What an AI Data Centre Actually Produces
• Why AI Can’t Be Both Instant and Cheap: Latency vs Throughput
• The Model and the Harness: Why Same-Model Products Differ
• Context, Not Capability: Why a Smart AI Model Gives Poor Answers
• Discardable Software: When Code Is Cheap Enough to Throw Away
• Human in the Loop vs Human on the Loop: Supervising AI Agents
• The AI Audit Problem: When Making Work Is Cheaper Than Checking It
• AI Evaluation as Acceptance Test: How to Know It’s Good Enough
• Extensibility Is Control: Who Holds the Power in an AI Product
• RLHF Explained: How an AI Model Learns What People Prefer
• Pretraining Explained: How an AI Model Learns Before Anyone Teaches It
• Fine-Tuning Explained: How to Adapt a General AI Model to One Job
• Tokens Explained: The Unit AI Reads, Writes and Bills In
• Embeddings Explained: How a Machine Compares Meaning
• RAG Explained: How a Model Answers From Your Documents
• AI Hallucination Explained: Why Models State False Things
• Distillation Explained: How a Small Model Learns From a Large One
• Reasoning Models Explained: What Changes When AI Thinks First
• Tool Use Explained: How an AI Model Goes From Text to Action
• Capex and Depreciation Explained: Why Chip Lifetime Drives AI Profits
• Run-Rate Revenue Explained: What an AI Company’s Number Means
• Backlog Explained: Revenue That Is Signed but Not Yet Earned
• Switching Costs Explained: Why It Is Hard to Leave an AI Supplier
• Temperature Explained: The Dial That Sets How Predictable an AI Model Is
• Guardrails Explained: Rules Enforced Around an AI Model, Not Inside It
• Benchmarks Explained: Why a Test Score Is Not Your Own Result
• Agent Memory Explained: How an AI Assistant Remembers You Between Chats
• MCP Explained: The Shared Plug That Connects AI Models to Tools
• Quantization Explained: How a Large AI Model Is Shrunk to Fit
• Parameters Explained: Where an AI Model’s Knowledge Lives
• Scaling Laws Explained: Why AI Labs Keep Building Bigger
• Synthetic Data Explained: When a Model Writes Its Own Training Examples
• Transformers and Attention Explained: How AI Reads Every Word at Once