You know that moment when you try to explain generative AI to someone who only hears the word chatgpt and their eyes glaze over, but then a week later they ask if it can paint their living room? That gap between fascination and real usefulness is where most large companies get stuck. After a long conversation with Ben Hoyle, I came away convinced that embedding generative AI across a big enterprise is less about models and more about culture, translation, and a little bit of showmanship.
The single most effective strategy Ben described was simple, obvious, and often ignored, show people what their colleagues are already doing. If someone in your company builds a chatbot that helps engineers parse requirements docs, make a short video, share it broadly, and let other teams see the mechanics. As Ben put it, seeing “this person who’s also in my business unit or who has a similar job” using AI gives others permission to think, maybe I can use it too.
That kind of peer-to-peer inspiration beats conceptual slide decks every time. People don’t want abstract promises, they want a mirror, something that says, this solves a task I actually do. The trick is curating showcases that live inside the company, not on a distant demo page, so employees can make the leap from curiosity to experimentation.
Access without guidance is chaos. Ben explained how Zeiss paired internal tools with training and a recommender system that nudged employees toward relevant learning. The goal isn’t to create prompt engineers overnight, it’s to make people comfortable enough to try, iterate, and ask for help.
Employees want rules before they start, not after. Practical guidelines that answer the question, what data can I put into this tool, and how should I use it, remove the friction. Once people understand the safety boundaries and the basics of how to prompt or hand a task to the AI, adoption moves from stealthy survival tactics to explicit practice.
You need both the top-down nudge and the bottom-up momentum. Convince your board that this matters, but also build grassroots communities of developers, back office staff, and curious problem solvers who can get their hands dirty. There’s a multiplier effect when a senior leader publicly uses an internal AI tool during a demo, because people think, if the boss of the boss is doing it, maybe I can too. Ben summed it up with brutal clarity, when an exec shows the tech, subordinates think, “if this person can use the tech then for sure you can as well.”
That public legitimization removes the unofficial taboo, the “we all know it’s happening but don’t talk about it” dynamic that leads to risky, unsanctioned usage.
Trust is the slow variable here. Many organizations remember the early data leak stories and reacted by banning public AI tools. That knee jerk makes sense, but it also creates a vacuum where people resort to shadow usage. The real work is rebuilding trust, not banning everything, but offering controlled, compliant alternatives. Ben’s team responded with a cross functional effort involving information security, legal, and cloud ops to give employees safe internal options.
And you need to acknowledge disappointment, sometimes people tried early tools and thought they were useless. That’s on the table too. Ben talked about “rebuilding trust in a technology that they’ve used and maybe they didn’t get good results from.” Show them how far the tech has come with real use cases, not marketing.
Generative AI is tempting, but not always the right tool. Ben’s blunt advice was worth repeating, “don’t use it to solve problems which you can already solve with existing technologies.” If Excel formulas or tried and tested scripts do the job, use them. But that doesn’t mean we ignore AI. Use it as a copilot, an orchestrator, a way to wrap deterministic tools in a flexible interface. If AI can call the right deterministic function at the right time, you get the best of both worlds, creative reasoning and reliable execution.
An internal data-thon model is a great way to surface real problems and test solutions quickly. Bring business owners, data scientists, cloud engineers, and product people into short bursts of focused problem solving, then follow the winners with proper productization paths. Infrastructure teams handle the tech scaling, but the real scaling challenge is human, getting hundreds or thousands of users comfortable, competent, and supported.
Practical moves that make scaling realistic include: – Clear classification rules for what data can go into which tool – Pre-baked templates and training for typical tasks – Showcases that map to common job functions – Executive demos that normalize usage – Rapid internal hack events that create a pipeline of solutions
The tech will, and should, become invisible. Copilot in your standard office apps, conversational access to internal docs inside Teams, automated agent-to-agent payments, a checkout you never have to scan, all of that is less about breakthrough science, and more about systems integration. Ben’s optimistic point was straightforward, much of the next wave is just integration, patience, and a nudge to make it happen.
So here’s my stance, messy as it is, adopt aggressively but thoughtfully. Don’t throw everything at AI because it’s shiny, but don’t hide under a policy either. Show, train, legitimize, and iterate. If you can translate the right problems to the right tools, and give people the confidence to try, you’ll get the cultural change you need much faster than you think. And then, maybe, we get to spend less time looking at screens, and more time doing the human things we actually enjoy.
Commenting Rules: Being critical is fine, if you are being rude, we’ll delete your stuff. Please do not put your URL in the comment text and please use your PERSONAL name or initials and not your business name, as the latter comes off like spam. Have fun and thanks for your input.
Join a growing community. Every Friday I share the most recent insights from what I have been up to, directly to your inbox.
