ai:training
Why most AI training fails at agencies (and the format that works).
By Loan Laux · June 16, 2026 · 4 min read
Most AI training fails because it teaches tools instead of changing workflows: a two-hour feature tour on demo data, applause, and an unchanged Monday. Training that sticks looks different: role-specific groups, live client work on screen, artifacts left behind (prompts, templates, skills), and office hours while the habits form.
The standard workshop, and why it changes nothing.
You've seen the format: an outside speaker, a deck of capabilities, impressive demos on generic examples, a list of prompting tips. Everyone leaves mildly inspired. Two weeks later, usage is exactly where it was.
The failure isn't the speaker. It's the transfer assumption: that watching capability translates into changed behavior. It doesn't, for the same reason watching a cooking show doesn't change what you make for dinner. The gap between 'I saw it work' and 'it's how I work' is where all the value sits, and the standard workshop never crosses it.
The format that works.
- Role-specific tracks. PMs on scoping, tickets, and client comms. Designers on briefs, exploration, and handoff. Developers on coding agents, review discipline, and tests. Mixed-audience sessions bore everyone in rotation.
- Live client work. This week's proposal, this sprint's tickets, this staging site. Demo data lets everyone stay hypothetical. Real work forces the questions that matter, like 'what about our NDA client' and 'this output is wrong, now what'.
- Small groups, hands on keyboards. Six to ten people, everyone driving their own session. Watching is the failure mode.
- Artifacts left behind. Every session ends with something that persists: prompts in the shared library, a template, a Claude Skill encoding the process just practiced.
- Office hours after. Four to six weeks of a weekly hour where people bring stuck moments from real work. This is where habits either form or quietly die, and it's the part almost everyone skips.
What each role should learn first.
:
Project managers
Meeting-to-ticket flow, scope drafting from discovery calls, status reporting from the PM tool, and first-draft client emails in the account's voice.
:
Designers
Brief expansion, variant exploration, copy drafts for mockups, accessibility and handoff checks. AI speeds the work around the craft without replacing the craft.
:
Developers
A coding assistant used well: context discipline, test-first prompting, review standards for generated code, and knowing when to stop prompting and think.
:
Account leads and leadership
Reading AI-drafted work critically, pricing implications, and what to tell clients about how the agency uses AI.
Measuring whether it worked.
Skip the post-workshop survey. Satisfaction doesn't predict usage. Look at deliverables four weeks out: proposals started from the new process, tickets drafted from transcripts, PRs with generated tests, reports assembled from exports. If the artifacts of work don't show it, the training didn't take, whatever the feedback forms said.
In-house champion, outside trainer, or both?
An internal champion knows your clients and stack, but often lacks the time and the standing to change how senior people work. An outside trainer brings patterns from other agencies and the credibility of distance, but needs your context to avoid teaching party tricks. The combination works best: outside for the format and the first sessions, inside for continuity.
That's how our team training is built: role-specific workshops on your live projects, artifacts left in your accounts, then office hours while it settles. On-site or remote.
Frequently asked questions.
How long should AI training for employees take?
A half-day per role track, then a weekly office hour for a month. Multi-day bootcamps front-load more than people can absorb. The durable format is short sessions plus supported practice.
Should we train everyone at once?
Everyone should get access and the usage policy at the same time, but train in role groups, starting where the workflow wins are clearest (usually PMs and developers). A whole-company session is a kickoff, not training.
Do people need prerequisites before AI training?
No. Mixed skill levels are fine within a role track because everyone works on their own tasks. The one real prerequisite is paid access to the sanctioned tools before the session, not after.
Is remote AI training as effective as in-person?
Both work in different places. In-person concentrates attention for the kickoff sessions; remote fits 1-on-1 coaching and office hours better. What doesn't work is a recorded course assigned as homework.