AI Skills by Role

AI training fails most often because it teaches the same thing to everyone. A finance lead, a salesperson and an operations manager use AI differently, check different things and need different examples. Teaching them together produces a session that is relevant to nobody, and a quarter later the tools are unused.

This guide sets out what each role needs to be able to do, what the universal skills are, and the order in which to teach them. It is part of the Skills, Change & Measurement pillar.

Two skills are universal. Everything else is role-specific, and the examples have to come from the learner’s own work.

The two universal skills

Whatever the role, two capabilities are non-negotiable and are taught first.

1. The data rule. What may and may not be entered into a tool, and who to ask when uncertain. This is a five-minute skill with a profound effect on risk, and it applies to everyone from the managing director to the newest joiner.

2. The verification habit. That AI output is a draft, what must be checked, and how the check is recorded. For most roles this means figures against source, claims against evidence and citations opened.

These two are taught to everyone, practised by everyone, and assessed for everyone. Everything else depends on them, which is why they come first.

Skills by role

The pattern is consistent: each role learns the same two universal skills, plus the specific workflow and check for their own work.

What leadership specifically needs

Leadership skills are different in kind and most often missing.

• Choosing use cases on frequency, cost, verifiability and containment — rather than on enthusiasm.
• Setting the data rule and being visibly bound by it, because staff calibrate to leadership behavior.
• Owning the policy, or appointing an owner with the authority to change it.
• Reading the measures — usage, time, quality and risk — and asking for them.
• Resisting scope creep, because the most common cause of a failed pilot is an expanded use case.

Without the fourth and fifth, an AI program loses its evidence and its discipline, and it becomes a series of demonstrations.

The teaching order

A sequence that works.

1. Context and limits. What AI does well and badly, and what the business has decided. One hour, all staff. 2. The rules. The data rule and the disclosure position, with examples. One hour, all staff. 3. The workflow. The six steps, demonstrated on the learner’s actual task. Ninety minutes, by team. 4. The playbook. Working through the prompts, including a deliberately flawed output to discuss. One hour, by role. 5. Practice. Running the workflow on live work with review. Self-paced. 6. The check. The verification drill, on outputs containing seeded errors. One hour. 7. Assessment. A short practical test: run the workflow, explain the check, catch an error.

Two notes on the order. The rules come before the workflow, because a workflow taught before the rules produces behavior the rules then have to correct. And the check comes near the end, but is practised, not merely described.

Assessing the skills

An assessment is what separates training from attendance, and it need not be formal.

• Run it. The learner completes one cycle of the workflow unaided, on real work.
• Explain it. The learner states what they checked and why, in their own words.
• Catch an error. The learner is shown an output containing a seeded error and identifies it.

The third part is the one that matters most and is the most often omitted. A person who can run a workflow but cannot catch an error does not yet have the skill the business needs, and the gap will show up in a client deliverable rather than in a training record.

How skills decay, and what to do about it

Skills learned once and never used are lost within a quarter. Three practices prevent the decay.

• Use the workflow weekly, on live work, so the skill stays current. A workflow used monthly is relearned each time.
• Refresh after change — a new tool, a revised process or a new output type — because a change invalidates part of the skill.
• Onboard with it. New joiners receive the module in their first weeks, so the standard is set before habits form.

The practical test is whether a colleague who has not run the workflow for a month could do it unaided with the playbook. Where they cannot, the playbook is missing something, and that is worth fixing rather than re-teaching.

What the learner should be able to say

The clearest test of a role skill is what the learner can explain afterwards, in their own words.

• Finance: “The figures come from the frozen extract. I do not let the tool calculate anything. I check every number back to the extract before the pack goes out.”
• Sales: “I confirm every claim about a prospect before it goes in an email, and I never let the tool set terms.”
• Support: “I check the answer against the knowledge base, and I never let it promise a refund.”
• Marketing: “I check every factual claim, and I run the claims register check before publishing.”
• Leadership: “I can tell you which use case we are running, who owns it, what it is measured on, and what our data rule prohibits.”

Where a learner cannot say something like this after training, the training has not transferred, and the likely cause is a missing practice or assessment step rather than a learner problem.

Common mistakes

• One course for everyone. Relevance collapses, and with it retention.
• Teaching the tool rather than the workflow. Feature tours do not change Monday.
• Rules taught last. Behavior is established, and then corrected.
• No practice. Knowledge without repetition does not become behavior.
• No error-catching drill. The verification skill is described and never practised.
• No assessment. Attendance is recorded and capability is assumed, which is how a training record and a working standard diverge.

Frequently asked questions

What AI skills does a team need?

Two universal skills — the data rule and the verification habit — plus the specific workflow and check for each role’s work.

What should we teach first?

The data rule and the verification habit, then the role-specific workflow. Rules first, because a workflow taught before the rules produces behavior that must then be corrected.

Do leaders need AI training?

Yes, and a different kind: choosing use cases, setting the data rule, owning the policy, reading the measures and resisting scope creep. Without these, the program loses its evidence.

How do we assess AI skills?

Three parts: run the workflow unaided on real work, explain what was checked and why, and identify a seeded error in an output. The third is the part that proves the skill.

Should we train everyone at once?

Train the universal skills to everyone at once, then the workflow by team and the playbook by role. A single all-hands session covering everything is the design that fails.

How long does role training take?

Around six hours per person for one workflow, delivered alongside the rollout rather than in one session. The second workflow takes less, because the rules and the check are already learned.

What if a role uses AI only occasionally?

Then the universal two skills matter more, and the workflow training can be lighter — but the verification habit still applies every time the tool is used, so it is never optional.

Next step

Teach the two universal skills this month, then build the role-specific workflow and playbook. See Training Your Team to Use AI Well for the curriculum, Training Staff to Verify AI Output for the drill, or book a team training session and we will deliver it with your team.

Sources

• Skills framework reflects standard capability-model practice applied to AI: universal rules plus role-specific workflows and checks.

No statistic in this article is invented; where figures appear in the linked guides, they are cited there with their source and date.