AI & Work

Using AI is not the same as running it

The numbers sound like progress. Eighty-nine percent of learning and development teams now use AI in some part of their work. That figure comes from LearnUpon's 2025 L&D report, based on a survey of L&D professionals in the US and UK.

The number that matters more: eleven percent say AI is consistently embedded into how their team works.

That is not a technology gap. Everyone has access to the same tools. The gap is in how the work is set up around those tools.

Most teams adopt AI at the edge of their workflow. Someone uses it to draft a module outline. Someone else runs a transcript through it after a session. These are not wrong moves. But they are individual hacks, not systemic shifts.

What changes when AI is embedded rather than dabbled with: the team has agreed on where context lives, what gets checked before output goes out, and who owns the quality step that AI cannot do. Context first, then prompt. Review plays an essential role throughout the process.

This is what the AI Content Ops method is built around: the operating layer that makes adoption stick. If your team is working through what that looks like in practice, aicontentops.online is a starting point.

Earlier on this blog: The Machine Is Doing It

Where are you in that gap? Are you using AI, or have you built the layer that makes it run?

Sources: LearnUpon 2025 L&D report (survey of L&D professionals in the US and UK, self-reported); AI Content Ops.

Send feedback

Goes to my inbox. Nothing is published.

All posts