How should an organisation train staff on AI?

Split the curriculum by audience. Those who decide need enough fluency to set direction, judge risk, and resource the work: what these systems do and do not do, what they cost, and where accountability sits. Practitioners need applied depth in retrieval, agents, evaluation, and production delivery. The wider workforce needs working literacy: how to use approved tools well, what never to paste into a prompt, and how their roles change.

AI Curriculum Map for Three Audiences

Last updated: 2026-08-14

AI capability building fails when it treats everyone the same. Three audiences need three different things: those who decide need enough fluency to set direction, judge risk and resource the work; practitioners need applied depth; and the wider workforce needs working literacy about approved tools and what never to put into a prompt.

A single AI training programme delivered to an entire organisation satisfies nobody: it is too shallow for the people building systems and too technical for the people approving them.

The template

Audience 1: those who decide. Executives, directors, budget holders, governance body members.

Format: three sessions of two hours, spaced two weeks apart, cohort of twelve to twenty
Content: what these systems do and do not do reliably. How to read a business case. Consequence tiering and where accountability sits. Vendor questions worth asking. Cost of the operating year.
Method: live proposals from their own portfolio, assessed in the room
Artefact: each participant reviews one real proposal and produces a written decision with rationale
Assessment: quality of the interrogation, not the conclusion

Audience 2: those who build. Data, engineering, analytics, and delivery staff.

Format: extended cohort over eight to twelve weeks with project work
Content: evaluation design, failure mode analysis, retrieval and grounding patterns, agent permission design, monitoring and drift, deployment path, secure integration
Method: build against the organisation's own platform and standards
Artefact: a working system passing the internal gate, or a documented decision not to proceed
Assessment: peer and faculty review against the gate checklist

Audience 3: those who use. Everyone whose work the tools touch.

Format: ninety minutes, role specific, plus an open office hour weekly
Content: what the approved tools are, what may and may not be entered, how to verify an output, when not to delegate the task, how to report a problem
Method: participants work on their own live tasks during the session
Artefact: one task in their own workflow, completed and verified
Assessment: self-reported at ninety days with an example

How to use it

Split by decision role rather than by seniority or department.
For executives, use short spaced sessions with a small cohort rather than a single long briefing.
Teach practitioners on the organisation’s own material and failure cases, not on generic examples.
Give the wider workforce concrete rules about approved tools and prohibited inputs, which is what they actually need.

This template comes from the AI Leadership and Workforce Capability: A Practical Playbook, which sets out the reasoning behind it, the rules of thumb that govern its use, and the signals that tell you the approach is failing. The full playbook is also available as Markdown. See all AI governance templates.