AI training for employees, on the work they already do
Most AI training teaches people about AI. Mine teaches your team to run AI on their own work, and to share what they build with each other.
Why most AI training fades
A team sits through a session. A few people leave excited. A month later, the same two people use AI and everyone else has gone back to the old way.
The training wasn't bad. It just wasn't attached to anything. People were shown what AI can do in general, then sent back to work that had never been written down clearly enough for AI to help with.
What I do differently
I train people on their own work, after it has been defined and built.
- Write the work down. I sit with your team and capture how one piece of work really gets done.
- Build it. I set up AI to run that process on the tools you already use.
- Train on that. Your team learns to run it, check it, and change it. The lesson is the job they do every week, not a demo.
People keep using what saves them time on Monday morning. They drop what they learned in the abstract.
Everyone, not just the curious two
Training only one or two champions is how AI ends up living on one laptop. I set up the whole team, and give them a way to share what they build.
At a 25-person marketing agency, that meant:
- One command to set up a teammate's laptop, on Mac or Windows.
- A health check that says what's wrong in plain words.
- Onboarding sessions for each team, a weekly check-in, one-to-one help, and written best practices.
- A safe way to share: someone says "share this with the team", it gets checked automatically, and it's available to everyone.
The result: 22 teammates set up, 16 shared team processes, and at least 5 people besides the founder contributing their own. Most of those processes were written by the team, not by me. That's the point.
More on this in How to get a whole team using AI, not just the curious two.
The people side
Every team has someone who's uneasy about AI: worried about their job, burned by a tool that didn't work, or just tired of change. Alongside the AI work, I'm a mindset coach. I make time for those people, hear out what's actually bothering them, and help them see what AI takes off their plate rather than what it takes away. People who've been heard give a new way of working a real chance.
What your team can do afterwards
- Run the AI on the work it was built for.
- Read the rules it follows, and change them when the work changes.
- Build something new and share it with the rest of the team.
- Spot when the output is wrong, and know what to do about it.
Common questions
How long does AI training for employees take?
It runs alongside the build. A typical start is one process, one team, a few weeks, with check-ins until the team runs it without me.
Do our employees need to be technical?
No. Most of the people I've trained don't write code. The rules are in plain language, and setup is one command.
Which AI tools do you train on?
The ones you already pay for: ChatGPT, Claude, Gemini, Copilot or another. I'm not tied to any of them.
What about team members who don't want to use AI?
I work with them directly. I'm also a mindset coach, so I hear out what's worrying them and help them see what AI takes off their plate. Nobody gets left watching.
Do you train the whole team or a few champions?
The whole team. Champions alone is how AI gets stuck with two people.