A tour of buttons is not a change in how work gets done.
Many AI classes have the same problem. People see a fun demo and try a few prompts. Then they go back to work with no clear plan. A few people keep trying. The rest stop.
A useful class must change real work. Each person should pick a task they own. They learn when AI can help, what facts to give it, and how to check the result. They should be able to use the steps without the teacher.
It is a real task with a clear start, safe facts, a useful result, and a person who checks it.
Four reasons business AI training stalls
Start with work that is frequent, visible, and forgiving.
Pick work that matters but is safe to test. A private board report is too risky for a first try. A customer reply, meeting note, file check, or short research task is easier to test and fix.
Use the FIRM test
Frequent
The responsibility happens often enough to practice several times during the next month.
Ask: will the employee use this again next week?Inspectable
A knowledgeable person can compare the result with a real standard, source, or outcome.
Ask: how will we know the output is good?Relevant
The responsibility belongs to the role and affects time, customers, revenue, quality, or coordination.
Ask: what becomes easier if this works?Manageable
A mistake can be caught during review before it creates legal, financial, safety, or customer harm.
Ask: can we practice in draft mode?A ten-minute task inventory
Ask each person to list five tasks they do often. Write down how long each task takes, what facts it needs, and who checks it. Pick one task that passes the FIRM test. Use that task for practice.
Teach FRAME, then let the tools change.
AI tools will change. A good work method should last. FRAME is a simple way to plan and check work made with AI.
Frame the job
State the outcome, audience, deadline, and form of the result. “Help with this email” becomes “Draft a six-sentence reply that answers the customer's two questions and leaves the price unchanged.”
Reference approved facts
Provide the relevant policy, notes, examples, or source documents. Tell the system to identify missing information instead of filling gaps.
Assign boundaries
Name what it may do, what it may not decide, which claims require support, and what must be escalated.
Make the work visible
Ask for a useful structure: a table, draft, checklist, comparison, summary with sources, or list of decisions and owners.
Evaluate and improve
Check facts, reasoning, tone, completeness, privacy, and next action. Correct the method, not only the final sentence.
Outcome: [what useful result should exist]. Audience: [who will use it]. Sources: [approved information]. Boundaries: [what the system may not decide or invent]. Format: [the exact output]. Review: [facts and risks a person must check].
This is a work brief, not a magic prompt. Improve it as the team learns.Spend less time presenting and more time watching people work.
A two-and-a-half-hour class can teach the first steps. It cannot change a whole company in one day.
Explain assistance, automation, human responsibility, and why a confident answer is not automatically a correct answer.
Review approved tools, permitted data, restricted data, required review, and the path for questions.
Show the weak first attempt, missing context, improved work brief, verification, correction, and final human action.
Participants work on their selected responsibility. A partner tries to find missing facts, weak assumptions, and unclear boundaries.
Save the work brief, approved sources, examples, review checklist, and owner in a place the team can find.
Each participant names when the workflow will run next, what will be measured, and who will review the first week.
Use approved or redacted material during practice. When real data is too sensitive, create a realistic sample with the same structure and decision points.
Every trained responsibility needs a one-page role card.
A role card saves the steps from class. Keep it to one page so people will use it.
“I read it” is not a review method. Name the facts, sources, calculations, tone, and authority limits that must be checked.
Use a 30-day adoption plan that is boring enough to work.
Employees use the selected workflow with full review. Record what was missing, wrong, slow, or surprisingly useful.
Add better examples, approved sources, clearer boundaries, and a shorter review checklist. Remove instructions that do not change the result.
Hold a 20-minute review. Each person shows one useful result and one failure. Update the shared role cards.
Review time, corrections, quality, adoption, and business movement. Keep the workflow, revise it, or stop using it.
The manager's weekly questions
Where did you use the workflow? What did it make easier? What did you have to correct? What information was missing? What should we change before the next use?
The goal is learning, not catching employees doing AI incorrectly.Count useful work, not enthusiasm.
Saving three minutes is not a win if checking takes ten. The same speed may still help if the work finds missed customer needs. Measure the whole task.
Clear rules make safe practice possible.
Name which systems employees may use for company work and which account type or privacy setting is required.
Define public, internal, confidential, regulated, and prohibited information with examples employees recognize.
Keep legal language, financial commitments, employment decisions, sensitive customer communication, and unusual exceptions with authorized people.
Require links or citations for important factual work and verification against the system of record.
Tell employees what to do when protected information is entered, an output is harmful, or an automated action behaves unexpectedly.
Record who owns each reusable workflow, when it was reviewed, and which systems or policies it depends on.
NIST has a guide for AI risk. Use rules that fit your laws, contracts, and type of work. This page is not legal, privacy, security, or job advice.
Useful questions before you build.
What should employee AI training include?
Useful training should cover task selection, context, examples, verification, data boundaries, human approval, reusable workflows, and measurement. Employees should practice on responsibilities close to their real jobs rather than watching a general product tour.
How long does it take to train employees to use AI?
A focused working session can establish the method, but competence requires repeated use. A practical starting point is one live session followed by four weeks of role-specific practice, manager review, and a weekly improvement check.
Which AI tool should a company teach first?
Begin with an approved tool that fits the company data and the selected task. The durable skill is not a particular interface. It is the ability to define the job, provide reliable context, inspect the output, and know when a person must take over.
How do we know whether AI training worked?
Measure use on selected responsibilities, time to a usable result, material correction rate, quality or service measures, and whether employees can repeat the workflow without the trainer. Login counts and prompts generated are weak substitutes for useful work completed.
Should every employee receive the same AI training?
Everyone needs shared foundations for safety and verification. Practice should then follow the role. A salesperson, bookkeeper, operations manager, and field technician have different information, risks, outputs, and review requirements.
Sources and further reading
- NIST AI Risk Management Framework
- NIST Generative AI Profile
- CISA artificial intelligence guidance
- Utah Office of Data Privacy
We use local talks as clues, not proof. Numbers are examples unless we link to a source.