The reason your team isn’t using AI has nothing to do with AI

A few weeks ago I posted on LinkedIn that one topic got me out of bed early during my focus break. AI Agents. And more broadly: why AI adoption moves so much slower inside most organisations than it should. Those weeks didn’t just change how I think. They produced Linelia’s first workshop product.

I’ll be honest: six months ago I would have smiled politely and made quiet jokes about everyone becoming an AI expert overnight. What changed was time and focused attention. Scepticism turned into clarity. That is the only position from which I think it is worth offering anything to a client. Not enthusiasm. Clarity.

This post shares what we built, why, and three things your team can try today. No new tools required.

Start here: a five-minute audit for your team

Before any tool, before any prompt, there is one question worth asking honestly: where are you still doing manually what AI could already handle?

The right starting point is your last five working days. Run through these three questions:

🗂️ Where did you spend time formatting, summarising, or restructuring information?
Meeting notes into action items. Email chains into briefings. Reports rewritten for a different audience. Not glamorous. Exactly where AI saves the most time, fastest.

📄 Where did you start from a blank page when you didn’t need to?
First draft of a proposal. Opening of a difficult message. Structure for a presentation you’ve given a dozen times. Starting from zero is a habit, not a necessity.

🔀 Where did you context-switch instead of focus?
Information from three sources. A brief rewritten three times. Twenty minutes on something that should have taken five. AI removes the friction that makes task-switching so costly.

If you answered honestly, you probably identified two or three hours per week. Without changing a single tool in your stack.

The question is never which AI tool to use. It’s where in your actual workday the friction is highest.

One prompt technique worth trying this week

Tool-agnostic. Works in whatever your company already uses. It’s called the role-task-format prompt.

Instead of typing what you want, tell the AI three things: who it should be, what you need done, and what the output should look like.

Weak prompt: “Summarise this meeting.”

Strong prompt: “You are a senior project manager. Summarise this meeting transcript into five bullet points, each no longer than one sentence, focused on decisions made and next steps agreed. Flag any open questions that still need an owner.”

Same tool. Completely different output. AI responds to specificity the same way a good colleague does. Vague input produces vague output.

In the workshop, this is usually the moment something clicks. Not because the technique is complicated. Because people realise they have been treating AI like a search engine instead of a thinking partner.

🎙️ One more tip: use your voice. Speak your prompt instead of typing it. You’ll add context more naturally and get better results instantly. You already send voice messages without a second thought. Talking to your AI is exactly the same habit. Just more useful.

Vague input produces vague output. AI responds to specificity the same way a good colleague does.

The honest reason AI adoption for teams stalls, and it’s not the tools

Everything above, you could have figured out yourself. The audit questions are not proprietary. The role-task-format prompt is not a trade secret. So why are most teams still stuck at the curiosity stage?

Not because the content is hard to find. Because the calendar always wins.

In every organisation I have worked with across energy, FMCG, media, and agencies, the pattern is the same. A topic – like AI – goes on the agenda. Someone shares an article. A pilot gets discussed. Then a real deadline appears, and the topic goes to next quarter. Then the quarter after that. This is not a motivation problem. It is a structural one.

That is the actual reason external workshops exist. Not because the facilitator knows things your team does not. But because booking three hours with an outside person makes it real. The calendar gets blocked. Laptops come out. People work on their actual tasks, not invented scenarios.

In my work at Linelia, I designed the workshop around exactly this insight. No slides. No demos. No case studies from other industries. Teams share their real briefings and workflows in advance. Every output from the three hours is something participants can use the following Monday.

Three hours of protected focus time, working on real tasks, is worth more than six months of “we should really explore AI.”

What your team walks away with

The workshop runs two to three hours, groups of six to eight, in-person or remote, tool-agnostic by design. Every participant leaves with four things:

📚 Prompt library tailored to their specific role
📅 30-day action plan tied to real workflows
🗺️ Tool map that fits your existing stack, no vendor pitch
Real outputs created during the session itself

The format is modular: a single pilot for one team, department-by-department rollout, or a company-wide programme including a leadership track covering governance and adoption. It scales to where you are.

The pilot starts with one kickoff call. If this sounds like something your organisation is ready for, find out more about it or get in touch directly.


Common questions


What does an AI adoption workshop actually involve?

The session runs two to three hours with a group of six to eight people working on their own real tasks, not invented scenarios. Before the session, participants share actual briefings, reports, or workflows they want to improve. Every output is something usable the following week.

Do we need specific AI tools installed before the workshop?

No. The workshop is tool-agnostic by design. It works with whatever your team already uses, whether that is Microsoft Copilot, Claude, ChatGPT, or any other AI assistant already in your stack. No new software or licences are required.

Why bring in an external facilitator instead of learning internally?

The content is freely available. The facilitator’s job is to create protected time where learning actually happens, focused on your real workflows, so every person leaves with something concrete rather than a slide deck they will never open again.

How quickly can we expect results after the workshop?

Participants leave with a 30-day action plan tied to specific tasks in their existing workflow. Most teams report meaningful time savings within the first two weeks, typically in the areas identified during the self-audit at the start of the session.

Working on an AI adoption challenge in your organisation? I am happy to talk it through. Reach out via linelia.io/contact/ or connect with me directly on LinkedIn.

Comments are closed