Traq Collective

Field note

Role-specific AI training vs generic workshops

By Last updated:

One teaches the concept to a full room. The other teaches your bookkeeper to close the month faster. Only one of them earns a second session.

Role-specific AI training teaches people to use AI on the actual tasks their job involves, like a recruiter screening candidates or a bookkeeper closing the month. A generic workshop teaches how AI works to everyone in the room at once. Role-specific training changes what people do on Monday. A generic session mostly raises awareness, then gets forgotten by Friday.

  1. Split by function

    Three or four groups, not one room

  2. Pick two real tasks

    The ones that eat time weekly

  3. Practice on real work

    Their own files, not a demo

  4. Name a session owner

    One person per group runs it

Order matters: skip the split and every later step trains the wrong task for someone in the room.

Why a one-size AI workshop rarely changes how anyone works

A generic workshop shows a room full of people, from sales to finance to operations, the same set of AI features. Everyone nods, a few people try the tool that afternoon, and by the following week most have gone back to working exactly as before. The session was not wrong, it just never touched the specific thing any one person actually does all day.

That gap shows up in the numbers. In a 2025 survey of 288 HR professionals, General Assembly found that HR teams who received AI training built around their actual job tasks were 35% more likely to say they felt very or completely confident using AI at work than colleagues who had to teach themselves generic AI skills on their own. The training content mattered more than whether training happened at all.

What role-specific training actually changes in practice

Role-specific training drops the general tour of AI features and starts from a person's real queue of work. A recruiter practises screening the resumes sitting in their inbox today, not a sample dataset. A bookkeeper practises reconciling this month's actual invoices. A salesperson drafts a follow-up to a real prospect they are already working. The tool is the same for everyone, the task in front of them is not, and that is the part a shared workshop can never supply.

Gallup's own workplace research makes the same point from the barrier side: the most common reason employees give for not using AI at all is that they do not believe it can help with the specific work they do, not that the tool is unavailable or unfamiliar. A demo of AI in general does nothing to answer that objection. Seeing AI do their own task does.

How to build role tracks without hiring a trainer for every department

You do not need a separate consultant per team to make training role-specific. Split the company into three or four functional groups (sales, finance, operations, and everyone else is a reasonable first cut), and for each group name the two tasks that already eat the most time every week. That short list becomes the entire training agenda for that group.

Run each group's session against its own real work, on the AI licence you already pay for, and put someone from that function in the room as co-facilitator rather than an outside trainer reading generic slides. If you do bring in outside help, hire for the ability to build those task-specific tracks, not to deliver one script to everyone.

When a single company-wide session is still the right call

Role-specific does not mean every session needs to be split. A one-time, whole-company moment still makes sense for announcing that AI is coming, setting the acceptable use policy, and naming which tools are sanctioned. That is a policy and awareness moment, not a skills moment, and one room handles it fine.

The mistake is stopping there and calling it training. The announcement earns attention. The role-specific sessions that follow are what actually change what people do with their hands on Monday morning.

35%

HR teams whose AI training was built around their actual job tasks reported far higher confidence using AI than colleagues who taught themselves generic AI skills on their own.

General Assembly, 2025

The takeaway

This week, split your team into three or four function groups and run one AI session per group on that group's own top two time-consuming tasks, rather than a single company-wide AI 101.

FAQ

Common questions

Is a company-wide AI kickoff a waste of time?

No. A single all-hands session is the right format for announcing AI is coming, setting the acceptable use policy, and naming sanctioned tools. The mistake is calling that session training. It builds awareness, not skill, so role-specific sessions still need to follow it.

How many people should be in a role-specific AI training group?

Small enough that everyone can practise on their own real work in the room, usually a single function like sales, finance, or operations. A group of eight to twelve from the same job type works better than thirty from mixed departments.

Do we need a different trainer for every department?

Not necessarily. One trainer can run every session if they build a separate, task-specific agenda for each group and bring someone from that function in as co-facilitator, rather than repeating one generic script to every room.

Book a call

Find where AI saves your team the most time.

Book a free call. No deck, no obligation.