Glossary
AI strategy
An AI strategy states where an organisation intends to use AI and where it does not, and the second half is what makes it useful.
In plain terms
A document saying what the organisation will and will not do with AI. Most of them contain only the first half, expressed as ambitions nobody could disagree with, and a document nobody could disagree with has not decided anything. The useful ones are shorter and contain refusals, because a refusal is the only part that changes what happens on a Tuesday.
Why it matters
Because in the absence of decisions, every individual purchase becomes its own argument, and the arguments are settled by whoever is most confident rather than by anything agreed. A strategy that rules things out saves that conversation repeatedly, which is a concrete saving of time and goodwill. One that only expresses enthusiasm adds a document without removing a single question.
How it works
The negative half is what carries the weight. Where the organisation will not use AI, what material must not go into it, which decisions stay with a person: these settle questions in advance and are what somebody can actually act on. Ambitions about transformation settle nothing, which is why they are easy to agree and easy to write.
It has to name who decides what is not covered, because the interesting cases are always the ones nobody anticipated. A strategy is a set of decisions made in advance and the world produces situations outside them continuously, so the route for handling the unanticipated case is worth more than another paragraph of coverage.
It works best written after some real use rather than before any. A strategy composed by people who have not yet used these tools describes what they imagine, and the imagining is usually wrong in both directions: fearful about things that turn out fine and relaxed about things that turn out awkward. A few months of actual experience makes the document considerably more specific.
The test is whether reading it would change anybody's behaviour this week. If a colleague could read the whole thing and continue exactly as before, it is a statement of position rather than a strategy, and it will be treated as one. That test takes a minute and is the most reliable thing available in a subject that attracts a great deal of writing.
Two documents, one page each
Seen in the wild
Deciding that a general assistant is sanctioned for internal drafting but not for anything going to a client unreviewed.
ChatGPTDeciding that unattended automation may summarise and route records but may not send anything externally without a person.
n8nDeciding that anything reaching across internal systems is administered centrally rather than adopted by a department.
Glean
Common misconceptions
People assume
We need a strategy before we start.
In fact
Usually the reverse. A document written before anybody has used these tools describes what was imagined, and the imagining tends to be wrong in both directions. A few months of real use produces a far more specific and more useful document, and the interim can be covered by a short policy about material rather than a strategy.
People assume
A strategy is about which tools we will buy.
In fact
Tool choices date within a year and the decisions worth writing down do not. What material may be used, what stays with a person, who decides the unanticipated case: those hold while the products underneath change completely, which is what makes them worth the effort of agreeing.
Telling them apart
AI strategy vs AI policy
AI strategy
Where the organisation intends to use this, and where it will not.
The rules for using it: what may go in, what must be checked.
The strategy chooses the ground; the policy governs conduct on it. Most organisations need the policy sooner.
Questions
- What makes one useful?
- Refusals. Naming what the organisation will not do, what material must not be used, and which decisions stay with a person settles questions that would otherwise be argued case by case. A document containing only ambitions has added a paragraph without removing a single conversation.
- How do we tell whether ours is any good?
- Ask whether reading it would change what a colleague does this week. If somebody could read it entirely and carry on unchanged, it is a statement of position, and it will be treated as one however carefully it was written. The test takes a minute and is the most reliable one available.
- When should we write it?
- After some real use rather than before. Written first, it describes what was imagined and is usually wrong in both directions. Written after a few months, it is specific about things that actually happened. A short policy about permitted material covers the interim and is the more urgent document anyway.
Key takeaways
- The refusals are the part that does any work.
- Name who decides the case the document did not anticipate.
- Written before any real use, it describes what was imagined.
- If reading it changes nobody's week, it is a position rather than a strategy.
Last checked July 2026