Stop buying an AI academy brochure: the three levels that actually move adoption (literacy, workflow, governance)

The procurement email is usually short. A learning platform has a new AI academy, the seats are discounted if you sign this quarter, and the completion dashboard will look healthy by Christmas. The person who has to say yes is rarely the person who will change a workflow on Monday. That gap is where these purchases go quiet.

The pattern in a learning review is familiar. The academy reports a high completion rate. The business reports that the same people still paste a brief into a chat window, accept the first draft and call it a pilot. Nobody is lying. The academy measured attendance. The business needed a different behaviour.

What the brochure is built to sell

A brochure is a catalogue with a narrative on the front. It is good at three things: a wide menu, a badge and a usage chart. Those are not nothing. A mid-market learning team of two cannot write a hundred modules, and a recognised badge gives a nervous executive something to show the board. The trouble starts when the catalogue is treated as the adoption plan.

Adoption is a change in how work gets done, under rules the organisation can defend. A course can support that. A course cannot be that. If the only artefact after the purchase is a login and a completion rate, you bought distribution of content. You did not buy a change in the work.

Literacy is the first level

Literacy is the shared language. What a model is good at, where it invents, what must never be pasted into a tool, and how to tell a fluent paragraph from a useful one. Everyone who will touch the tools needs this, from the graduate to the general manager. It is also the level a brochure can actually deliver, because it does not depend on one team's process.

Do not skip literacy, and do not stop once people can talk about the tools. A team that can explain a model in a town hall, and still processes Monday's inbox the way it did last year, has a shared language and an unchanged job. The language is useful. It is not the adoption plan.

Keep literacy short and concrete. A half day is enough for most knowledge workers if the examples come from their own documents, not from a generic marketing prompt. People should leave having broken a model on purpose, so they have felt a confident wrong answer, and having written the three things they will not put into a tool. That is literacy. A long academy that never leaves the vendor's sample data is a longer version of the same tour.

Workflow is where adoption moves

The second level is a named workflow. Pick a specific job, such as the weekly customer summary, the first pass on a policy exception, the research brief before a pitch or the triage of a ticket queue. Give it one owner, a before and after, and a rule for what a person still checks. A slogan about using the tools more often is not a workflow.

This is the level a use case library gestures at and then leaves to you, because it cannot be copied from a bank to a council to a manufacturer without becoming bland. The work of L&D here is not to author another module. It is to sit with the operator, pick one workflow that is frequent and low risk, and design the new steps so a person can run them next week without a facilitator in the room.

A practical cut looks like this.

1. Name the workflow in the operator's words, including how long it takes today and what a wrong output costs.
2. Mark the steps a model can draft, the steps it must not touch and the step where a person decides.
3. Run it on real work for two weeks, with the same person, and keep the outputs.
4. Write the failure you actually saw, not the failure you feared in the abstract.
5. Keep the workflow, change it or stop it, and put that decision in a sentence a sponsor can read.

If you want that day built around a team's own work rather than a sample prompt, the AI training workshop is the format we use. The point of the day is the workflow they leave with, not a tour of features.

Governance is the third level

The third level is the set of decisions that let the first two scale without a nasty surprise. Who may use which tool. What data is in bounds. When an output can reach a customer. Who is accountable when it is wrong. What an agent is allowed to do without a person.

Literacy without governance produces shadow use. Workflow without governance produces a local success that legal hears about from an auditor. Governance without the other two levels produces a policy nobody can apply, which is how you get both a ban and a dozen unsanctioned accounts.

Non-lawyers can hold this level if you give them questions instead of a statute. What is the data? Who sees the output? Can the system act, or only draft? What would we do if it were wrong in public? Those four questions will catch most of the trouble a product or operations team is about to ship. A longer framework, whether that is NIST, ISO 42001 or the EU AI Act, is how you organise the answers once you have them. It is a poor place to start a Tuesday afternoon.

How to buy

Before you sign the academy, ask for the three levels as separate offers. If they cannot be separated, you can still buy the literacy layer and build the other two yourself. That is often the right split. Pay for a decent common language. Do not pay for a promise that a catalogue will redesign work.

Use a short test on any proposal, internal or external.

1. Which level is this, in one word: literacy, workflow or governance?
2. What will a named person do differently within 30 days, and how will we see it?
3. What data is in play, and who has already said that is allowed?
4. What gets stopped if the two week trial does not change the workflow?
5. Who owns the habit after the completion email goes out?

If the answers are that it covers everything, that people will feel more confident, and that you will review it next quarter, you are looking at a brochure. Confidence is worth noticing, and it is not a result you can point at. A changed workflow is.

What to do this month

Pick one cohort, not the whole company. Give them literacy in a half day, using their documents. Choose one workflow with the manager who will feel the pain if it fails. Run it for two weeks. Write the governance answers on a single page before anyone is tempted to let a tool send the output on its own.

Then look at the academy again, if you still want it. You will know which modules are worth the seats, because you will have met the work. Keep the completion chart as a record of who showed up. Judge the purchase by whether the named workflow is different two weeks later.