- Different Jobs, Different Sessions
AI Training by Role
A single company-wide AI session teaches everyone a little and nobody enough. Here is what each group in a small business actually needs, and how long it takes.
WHY ALL-HANDS FAILS
The Same Session Cannot Serve the Owner and the Front Desk
The default approach is one AI session for the whole company. It is efficient to schedule and it teaches nobody enough to change what they do on Monday, because the questions a practice owner has and the questions a scheduler has share almost no overlap.
Splitting by role costs a little more time and produces training people can act on immediately, which is the only kind that survives. The breakdown below is how we structure it, and total contact time is usually smaller than the all-hands version because each session covers only what that group needs.
Role-based training is what actually sticks in the Dallas businesses we work with, because a front-desk coordinator and a managing partner have nothing in common in what they need from AI. We build the session list around your real org chart, not a generic curriculum.
FOUR AUDIENCES
What Each Group Needs
OWNERS & LEADERSHIP
Judgement, not usage
How to evaluate a vendor claim, what questions to ask before approving spend, where the liability sits, and what a realistic timeline looks like. Half the value is learning to recognize an overpromise.
Typically: one session, plus the vendor question list.
EVERYONE
The safety baseline
Which tools are approved, what never goes in, how to spot AI-assisted phishing and voice cloning, and who to ask. Short, mandatory, and repeated for new starters.
Typically: thirty minutes, plus the one-page policy.
DAILY USERS
Their actual work, hands on
Run on the real tasks this group does, with their own documents, in the tool they will use. Not a demo. They should leave having completed real work with it.
Typically: a working session, then a follow-up two weeks later.
REVIEWERS & APPROVERS
How output goes wrong
The most-skipped session and probably the most important. What plausible-but-wrong looks like, why fluent output earns unearned trust, and how to check quickly without redoing the work.
Typically: one session with real failure examples from your own workflow.
Train when they get the tool, not before
Training delivered weeks ahead of access is entertainment. People retain what they use within a day or two, so the session should sit immediately alongside the license being switched on, which is why we sequence enablement to follow configuration rather than lead it.
We are fifteen people. Do we really need four sessions?
Often the same people are in more than one group, so it collapses to two or three in practice. What we would not collapse is the safety baseline and the daily-user session. They have genuinely different purposes and combining them means one always gets rushed.
Is online training enough?
For the safety baseline, yes. For daily users, no, generic courses cannot use your documents, your systems, or your rules, and that specificity is the entire reason the session works.
How do we handle people who joined after the training?
Put the safety baseline into onboarding permanently, and let an internal champion cover the practical side. A program that depends on us returning for every new hire is a program that decays, which is the point of building champions.
BK
Written and reviewed by Bob Kehr, President & Founder of Kehr Technologies, Plano City Council member, and Plano Chamber Small Business Person of the Year 2022. He has run the all-hands version and learned why it does not work.
Last reviewed August 2026. Questions we have not answered here? Call 214-444-3583. Kehr Technologies is based in Plano, Texas, and works with businesses throughout the Dallas area.