AI Training & Workshops
Building practical AI skills across a team
A training plan that connects approved tools, recurring tasks, review habits, and sustained use.
← GuidesIn this piece
For a manager responsible for AI adoption, the difficult part begins after the demonstration. People return to deadlines, familiar tools, and work that rarely looks as tidy as a training example. A usable training plan gives them a place to practice, a standard for reviewing output, and someone to ask when the method fails.
This guide focuses on skill development over time. If you need to organize one session, start with planning an AI workshop.
Start with tasks people can judge
Choose work that recurs often enough to practice and whose quality the team can assess. Drafting a handoff from approved notes is easier to evaluate than asking an assistant for an unfamiliar legal interpretation. The right starting point depends on the team's knowledge, approved tools, and consequences of an error.
Create a small task inventory. For each task, record the input, intended output, reviewer, data restrictions, and current effort. Include review and correction time in that effort. A quick first draft can still be an expensive workflow if someone has to reconstruct the sources afterward.
Here is an illustrative selection exercise:
| Candidate | Why it may be suitable | What must be resolved first |
|---|---|---|
| Internal meeting summary | Source notes and participants can verify it | Permission to process the notes; handling missing decisions |
| Customer reply draft | Staff can compare it with approved guidance | Human approval and limits on commitments |
| Automated staff performance rating | Consequences extend beyond a writing task | Governance, appropriateness, specialist review; defer from introductory training |
The exercise is meant to reveal boundaries. There is no obligation to choose an AI use case from every department.
Teach a complete working method
A prompt is one part of the method. The team also needs to know what source material to provide, what a useful result looks like, and what to do when the answer cannot be supported.
Teach participants to state the task, provide relevant approved context, describe the output, and identify constraints. Then ask them to inspect the result against the source. Requiring “do not invent” in a prompt is useful direction, but it is not a substitute for checking the answer.
NIST's generative AI profile identifies confabulation among the risks to manage. In training, that translates into a concrete exercise: include an input that omits a necessary fact and check whether participants notice a confident unsupported answer. NIST Generative AI Profile.
Use a practice record that exposes rework
The following is a recommended record, not a claim about client results. Have participants use it on a small set of comparable tasks:
- What was the task and which approved sources were used?
- What did the assistant produce that was usable?
- What needed correction, and how was the correction verified?
- How long did preparation, generation, checking, and editing take together?
- Would the person use this method again for this type of task?
Review the records with the people doing the work. If the source documents are inconsistent, another prompt may not be the remedy. If permissions prevent access, training cannot resolve that on its own. If the task simply takes longer this way, keep the original method while investigating.
Give managers a useful role
Ask managers to inspect a completed artifact and the corrections, rather than request a declaration that everyone is using AI. This makes the discussion about work quality.
Assign one owner to the shared instructions. Version changes should have a reason: a recurring omission, a changed process, or a newly approved source. Keep a few difficult examples to check whether an edit fixes one problem while introducing another.
Make it acceptable to stop and ask for help. If staff are rewarded only for speed or usage, they may conceal the checking effort that determines whether the workflow is useful.
Expand after the method holds up
Expansion can mean a second task, another team, or deeper integration with existing software. Each changes the requirements. A process that works for an internal draft may need additional approvals when it sends messages or changes records.
The AI Training service covers tailored team sessions and optional follow-up. The published sales training example explains a specific sales-focused scope; it does not supply a workforce-wide performance benchmark.
For this kind of engagement, agree the audience, task pack, review method, materials, and follow-up before comparing estimates. Tailored training is scoped individually. Existing package fees apply only to the commitments listed with that package.
When the next obstacle is repetitive movement between tools, use the workflow automation guide. That is a separate decision from teaching people to use an assistant well.
Put this into practice
Bring the decision you’re working through.
A working session is a chance to review your goal, the tools or website you have, and the help you need. We’ll identify a sensible next step and discuss scope before any project commitment.
AI Training for Teams →Book a working session