anaboo.ai
A confident employee presenting AI tools on a screen to sceptical colleagues in a meeting room, representing internal advocacy that overshoots what the business is ready for
← All posts

Why your biggest AI enthusiast might be slowing your rollout down

21 November 2026Brett Alegre-Wood7 min read
AI adoption cultureinternal AI championAI rolloutAI change managementbusiness AI cultureAI implementation
Listen to this article0:00 / 5:31
Two AI hosts discuss this article. Generated from the text.Download

TL;DR

The person in your business who is most excited about AI is often doing more damage to your rollout than your most vocal sceptic. They build personal workflows nobody else can follow, make promises AI cannot keep, and burn through your team's goodwill before any structured adoption begins. The credibility gap they create is harder to close than any resistance you could have addressed head-on. Identifying and redirecting them is one of the quietest wins available in AI adoption culture.

Why resistance is the easier problem to solve

Resistance you can see. A team member who refuses to use a new tool raises their hand, explains their concern, and gives you something to work with. You can address the objection, run a demonstration, or find a case study that lands. It takes effort, but the obstacle has a face.

The over-enthusiastic internal champion is harder to spot because everything they do looks positive. They are learning, building, sharing. From the outside, they look like exactly the culture you want. The damage they cause takes longer to surface, and by the time it does, the credibility around AI in your business is already eroded.

The loudest advocate in the room and the biggest obstacle to adoption are sometimes the same person.

What the typical AI enthusiast actually builds

Left to run without structure, the internal AI champion tends to follow a specific pattern. They start with a genuine problem, something genuinely painful in their daily work, and they solve it. That part is good. Then they keep going.

They connect tools, build prompt libraries, create automations that depend on their specific setup, and eventually arrive at something that works brilliantly for them and is completely opaque to everyone else. The workflow lives in their head as much as it lives in the tools.

When colleagues ask to use it, one of two things happens. Either the champion tries to explain it and the explanation is so long it puts people off, or they share it and it breaks immediately because the colleague does not have the same accounts, permissions, or tribal knowledge to make it run.

Neither outcome moves your business forward.

How overselling creates a credibility gap

The enthusiast does not just build. They advocate. Every conversation becomes a pitch. Every meeting is an opportunity to evangelise. And because they are genuinely excited, they make AI sound easier than it is.

They tell a sceptical operations manager that their monthly reporting job will take two minutes instead of two hours. The operations manager tries it, runs into a hallucination or a formatting problem, and concludes that AI does not work. The enthusiast moves on to the next thing. The operations manager does not.

That is the credibility gap. One failed demo from a trusted internal voice lands harder than a failed pitch from an outside vendor, because the operations manager feels foolish for having believed it. Scepticism hardens into something closer to contempt, and contempt is far more difficult to shift.

Straightforward resistance never creates this problem. The sceptic who says "I don't think this will work" is easy to engage. The convert who now says "I told you so" is not.

Why they become a single point of failure

The personal workflows the enthusiast builds are fragile in a specific way. They depend on one person knowing how they work.

When that person is away, the workflow stops. When they leave the business, the whole stack collapses. When they are promoted or moved to another team, the people left behind have no idea how to maintain what they inherited. The business has built a dependency, not a capability.

This is the opposite of what AI adoption culture is supposed to produce. The goal is to augment the team as a whole, to build capacity that does not walk out the door with any single individual. A well-run AI rollout makes the business smarter. An enthusiast-led one makes one person indispensable.

A capability owned by one person is a liability. That is true for any skill, and it is especially true for AI.

There is also a subtler version of this problem. When the enthusiast is the only one who really understands what AI can do in your context, every decision about AI runs through them. They become an informal gatekeeper, and their personal preferences about tools, platforms, and use cases shape your whole adoption trajectory without that ever being a deliberate choice.

Start here

See where AI fits in your business. Free.

A 60-minute audit. We map the highest-value automations and what they're worth in time and money. No pitch, no pressure.

What separates a genuine champion from a liability

The distinction is not about enthusiasm. Genuine excitement about what AI can do for a business is valuable. The question is whether that enthusiasm is directed outward or inward.

A genuine champion builds things other people can use. They document as they go. They run small, controlled demonstrations rather than grand promises. They bring sceptics in early rather than presenting finished solutions and expecting applause. When something does not work, they say so, because protecting the credibility of the programme matters more than protecting their own standing as the AI expert.

A liability builds for themselves and then tries to convert others after the fact. The pitch is always slightly breathless. The demos are always the best-case version. The caveats come later, if they come at all.

The honest test: ask them to hand their workflow to a colleague and step away for a day. If they cannot do it, or if they try and the colleague fails, you have a dependency.

What good adoption culture actually looks like

Structured AI adoption culture does not depend on one enthusiast dragging the rest of the team along. It starts with a clear decision about which problems are worth solving, made by the people who own those problems, not just the person who is most excited about the tools.

It runs experiments that are scoped tightly enough to succeed or fail clearly, with the failure being as informative as the success. It documents what works in a form that does not require tribal knowledge to use. And it keeps the feedback loop between the people using AI and the people running the business short enough that bad ideas get killed quickly.

When a team builds on AIOS, the enthusiast's energy gets redirected rather than suppressed. They are still useful. They still run faster than most people. But they are running on a track the whole team can follow, not off into the bush on their own. The enthusiasm feeds the system instead of bypassing it.

The other shift that matters is how wins get measured. An enthusiast measures wins by what they personally built. A structured team measures wins by what changed for the business: time recovered, errors reduced, capacity freed. Those are very different scoreboards, and only one of them compounds.

The conversation most owners avoid

There is a reason this problem persists. The AI enthusiast is often one of the most motivated people in the business. Telling them their approach is creating problems feels like punishing initiative, and most owners would rather have a motivated person running too fast than a disengaged one doing nothing.

But there is a version of that conversation that is honest and direct without being demoralising. It starts by acknowledging what they have built and what they have demonstrated. It names the specific problem their approach creates: not their competence, but the business's dependency and the team's experience of being left behind. And it ends with a clearer mandate.

The goal is to make their work useful to more than one person.

That framing is usually enough. The enthusiast almost always wants to be genuinely useful. They have just been operating without a structure that tells them what useful actually looks like for the business as a whole.

What to do this week

  • Map the informal AI activity in your business. Ask each team member what AI tools they are using, what they have built, and whether anyone else can use what they have built without the original builder present.
  • Have a direct conversation with your most active AI user. Not to reprimand them, but to understand the scope of what they have built and where it is brittle. Ask them to walk a colleague through it and watch what happens.
  • Set a documentation standard before the next experiment. Any AI workflow worth keeping should be explainable and operable by someone other than its builder. Make that the entry requirement, not an afterthought.
  • Create a simple intake process for AI ideas. A short form or a standing agenda item gives enthusiasts a constructive outlet and gives you visibility before problems compound. It also signals that AI development is a team function, not a solo sport.
  • Identify which existing workflows are single points of failure and decide what happens if that person leaves. Start with the most-used ones and work backwards.**

Where to from here

Book a free AI audit and we'll show you what's worth augmenting first in your business, and what isn't.

Live with passion & AI,

Brett

Podcast

Host a podcast? Have Brett on as a guest.

Straight talk on implementing AI in real SMEs, no jargon, plenty of receipts from the businesses we run.

Frequently asked questions

How do I know if my AI champion is creating a problem rather than solving one?

+

The clearest sign is that the workflows they have built only work when they are in the room. If their AI output cannot be explained or maintained by another team member, it is a liability regardless of how impressive it looks.

Should I stop people experimenting with AI on their own?

+

No. Individual exploration is valuable and shows you where the real friction is in your business. The issue is not experimentation, it is when personal experiments are presented as business solutions without the documentation or reliability to back them up.

What is the right role for an AI enthusiast in a rollout?

+

They should be one of several people involved in scoping and testing, not the sole architect and advocate. Their energy is an asset when it is channelled into experiments that other people can replicate and verify.

How do I repair credibility damage after an oversold AI demo?

+

Start smaller than you think you need to. A quiet, underpromised win for a sceptical team member does more work than any number of presentations. Let the tool speak without a cheerleader attached.

Does AIOS help with this kind of internal adoption problem?

+

That is part of what structured AI operating systems are built for. AIOS gives teams a framework for what gets built, how it gets documented, and who can use it, so AI capability becomes a business asset rather than one person's side project.

What if the AI enthusiast is a senior leader?

+

The pattern is the same but the stakes are higher. A senior leader who oversells AI to the whole organisation creates a much larger credibility gap when things fall short. The same principles apply: scope carefully, document everything, and measure what actually changes.

Brett Alegre-Wood, founder of Anaboo
About the author
Brett Alegre-Wood

Brett is a four-time founder (Darra Tyres, Gladfish, EzyTrac, Anaboo) and the operator behind AIOS, Anaboo's AI Operating System. He writes from inside the build, installing AI in his own businesses first and reporting back what actually moves the numbers. Based between Singapore, the UK and Australia.

WE USE AI: All images are made with programmatic AI (a prompt is used rather than real photos) so when you meet Brett and the team they may look slightly different from these images. This is done to show you what's possible.

Want Anaboo AIOS in your business?

Free 60-minute audit. We'll show you what's worth automating first.