What real AI training for teams actually looks like

A head of marketing called me last month, two weeks after their team had finished a "company-wide AI training programme" with a big consultancy.

"They watched four hours of videos," she said. "There was a quiz at the end. Everyone passed. And now nobody's actually doing anything differently."

She's not alone. Most "AI training" I see being sold to teams in 2026 is the same training people were getting in 2023, just with newer screenshots. Slides, talking heads, a "framework," a quiz. Then the team gets back to work and… nothing changes.

Here's why, and what works instead.

Why slide-deck AI training doesn't transfer

Three problems, all of them obvious in hindsight.

★ Problem 1

Watching is not doing. Nobody learns to ride a bike from a deck on bike-riding. AI is the same. You don't understand prompt engineering until you've sat with a real tool, given it real input, gotten frustrated, fixed it, and shipped something. Slide decks bypass the muscle the team actually needs to build.

★ Problem 2

Generic examples don't transfer. "Here's how AI could help with sales emails" lands as theory if the example isn't your team's sales emails. People nod, take notes, and never act on it because the example was abstract and the bridge to their actual job was left unbuilt.

★ Problem 3

No artefact = no momentum. A team leaves the training with… what? Notes? A certificate? Nothing they can show their colleagues, nothing they can keep iterating on, nothing to point at next Monday and say "we did this in the workshop." The behaviour dies on the bus home.

What we do instead

Every Pathwise corporate workshop is built around one principle: your team ships something real before they leave.

A typical four-hour Pathwise corporate session looks like this:

• 0:00 — Coffee, intro, and "what are we actually trying to build today?" Not generic AI literacy. A real, specific outcome someone on the team cares about. We pre-scope this with the team lead before the day so the room walks in pointed at something.
• 0:30 — Live demo of the toolchain on their problem. Not "this is how Claude works in general." This is "let's open Claude and start solving the thing you brought in." Five minutes in, the room is already engaged because the example is theirs.
• 1:00 — Hands-on building, in small groups. Pairs or trios. Each pair takes a piece of the team's actual workflow and builds an AI-augmented version of it. We circulate, unblock, push back, suggest. Nobody is watching slides.
• 3:00 — Demos to the room. Every group shows what they built. Real artefacts: prompts, working tools, deployed apps, drafted copy. Five minutes each.
• 3:45 — "What you're taking back." A 15-minute structured conversation about which of these get adopted, who owns each, and what the next two weeks look like.

By 4:01 PM, the team has built five real things, knows how to repeat the process, and has a written list of what comes next.

That's it. There's no magic. The magic is that every minute was spent doing the actual thing, on the actual problem.

A real example

Last year a marketing team came to us with a recurring pain: they were spending 8–10 hours every Monday compiling the week's campaign performance into a Slack-ready summary. They wanted that down to under an hour.

We didn't teach them "AI for marketing analytics." We sat down with their actual dashboards, their actual Slack format, their actual brand voice, and built a working Claude-driven workflow that pulled the raw numbers, summarised what changed week-over-week, drafted the Slack post in their tone, and flagged outliers for the team to review.

By the end of the day they had:

• A working prompt template they ran every Monday
• A documented hand-off from "AI does first draft" to "human reviews and posts"
• An estimate of ~7 hours/week saved across the team

We didn't tell them they'd save 7 hours. They figured it out themselves, on the whiteboard, after building the thing. That's how it sticks.

The ROI conversation

People ask me about ROI on AI training. Honestly, I think it's the wrong question — or at least the wrong framing.

The right framing isn't "how many dollars per training hour do we save?" It's "how much faster can your team move on the things you already want to do?" AI training that works doesn't replace people's jobs; it removes the friction between their idea and their output.

The unlocked velocity is the ROI. It's just hard to measure in a quarterly review.

What this means for you

If your team is about to do AI training — your own or vendor-led — push on these questions:

1. What will my team actually build during this session? If the answer is "nothing, but they'll learn," walk away.
2. What does my team take home that they can use Monday morning? A deck doesn't count. A working artefact does.
3. Will the examples use our problems, or generic ones? Generic examples are a red flag. Either you're paying for off-the-shelf content, or the trainer doesn't know how to adapt.
4. What does success look like 6 weeks later? If the trainer doesn't have a clear answer, they're not building toward retention.

We run corporate AI workshops across Singapore, Hong Kong, and APAC — half-day, full-day, weekend formats. Every session ends with something real your team has built. Onsite at your office or online for distributed teams.

If you're scoping a workshop, book a free 30-minute discovery call and we'll talk through the specific outcomes you want. No slides on that call either.

— Mr. Brown