10/15/2026
I told a client last week to delete their AI policy.
It was 14 pages. Beautiful formatting. Very corporate. Straight from a template service.
Nobody in the company had read past page two.
The one instruction people did remember was “Consult HR before using AI.”
That raised more questions than it answered:
→ Which tools count?
→ What counts as “using” AI?
→ Who is HR, exactly?
So we started over.
The new version fits on one page. Three rules and a list of approved tools. That’s it.
The next week, adoption went up. We didn’t loosen anything. People could finally tell what they were and weren’t allowed to do.
A policy nobody can follow isn’t protecting you. It leaves people guessing, or quietly avoiding the tools altogether.
If you’re a founder looking at polished AI policies online and thinking you need one like that, you probably don’t. You need one your team will actually read.
What’s in your AI policy that no one reads?