AI Enablement · What we put in place
How to AI?
Your team already types this, into a licence somebody bought last quarter. The question is not the problem. Nothing on the other side of it was ever set up.
The gap
“It is rolled out. Everyone has access.”
Access is the first thing you do, and the least of it.
A licence is a door. Nobody was told what is behind it, what they are allowed to carry through it, or who to ask when it sticks — so the tool gets used the way a search box gets used. One question at a time, by whoever was already curious, on work small enough that nobody has to check it.
That is not a rollout stalling. That is a rollout doing exactly what it was set up to do, which is nothing in particular.
The workshop next door is about the question itself — how to ask for something a model can actually answer. This page is about everything around the question, and most of it is plumbing and permission rather than training.
What has to be true
Five things, and the order is the argument.
Nothing else on this site is numbered, because most conditions hold at once and a list that counts them promises a sequence that is not there. These five are the exception. Each one is worth almost nothing until the one above it is true, which is why so many rollouts begin at the fifth and then begin again.
Access nobody has to ask for
Inside the tools people already have open, on by default, with no request form and no named pilot group. A tool you have to apply for is a tool for the people who enjoy applying for things.
A line short enough to read
One page: what may go in, what may not, and who decides the edge cases. Nobody puts a real client's work into anything until they know which side of that line they are on, and a fourteen-page policy nobody opens is the same as having no line at all.
Patterns taken from your own work
Not a prompt library. Six or seven things your team actually does every week, worked through until each one has a shape somebody can copy on a Tuesday without thinking about it.
Somebody to ask, two desks away
The questions that stop people are small and slightly embarrassing, and they never reach a helpdesk. They reach whoever is nearest — so the enablement job is making sure that person knows the answer, and is allowed to spend the twenty minutes.
A way to see what stuck
Not a usage dashboard. A standing half-hour where somebody says what they tried, what came back, and whether they would do it again. Nothing compounds that nobody ever mentions out loud.
How we do it
Twelve weeks, on one workflow, then we go.
Enablement is not a purchase and it is not a policy document. It is five things being made true in one specific building, which takes being in the building. So it runs as the forward-deployed engagement: one workflow with real volume, a day a week from the people who do the job, and a last day written in before the first one.
By the end the five above are either true or they are visibly not, and you own every part of them — the line, the patterns, the standing half-hour. If the honest answer is that two days in a room would get you further, we will say that instead and sell you the smaller thing.
See it against everything else we doGive the question somewhere to land
Tell us what your team is already trying to do with AI, and the point where it stops being worth the effort. We will tell you which of the five is missing, and whether we are the right people to put it there.
[email protected]