It usually starts with a survey. Leadership asks employees which AI tools they're using and what they're using them for. The answers come back varied: different tools across different teams, different use cases, different levels of exposure. And then a decision gets made: we're going to standardize. One approved platform for the whole organization. Contained, managed, and secure.
The thinking is understandable. If everyone is on the same tool, company information stays in one place, access can be governed, and sensitive data is theoretically more protected. On paper, it looks like responsible AI adoption.
In practice, it often creates the problem it was trying to prevent.
The Workaround Problem
When a company mandates a single AI tool across finance, marketing, engineering, and customer success, there are two likely outcomes. Either people lose the value they were getting from tools that actually fit their work, or they keep using those tools anyway.
That second scenario is the one worth paying close attention to.
A company that has standardized on one approved platform and believes it has controlled AI usage may, in reality, have a workforce still relying on unapproved tools in the background to get real work done. Code ends up in one place. Financial analysis in another. Customer data in a third. Sensitive internal information moves into tools the company doesn't govern, can't monitor, and in many cases can't pull back from.
That's not a theoretical risk. It's a predictable consequence of mandating a tool that doesn't fit the work. And the irony is that it happens most often in the name of security and efficiency.
Once sensitive information leaves the systems a company controls, the exposure can't always be undone. The company traded the appearance of control for the reality of less of it.
Why One Tool Rarely Fits Everyone
Every department handles different information, carries different risks, and solves different problems with AI. What helps a marketer brainstorm campaign angles is not what helps an engineer reason through a complex architecture decision. What works well for customer success drafting responses at scale is not the right fit for finance modeling forecasts or analyzing churn. A tool that's good enough for everyone on the surface is often ideal for almost no one underneath.
The questions a department-based approach forces are more honest: what does marketing actually need from an AI tool? What should finance never put into a model without strict controls? Where are the highest-risk workflows, and where are the biggest time-saving opportunities? What kinds of information does each team handle daily, and what governance does that require?
Those questions rarely all point to the same answer. And a procurement decision made without asking them will produce a rollout that either gets quietly circumvented or simply fails to deliver the value that made AI adoption worth pursuing in the first place.
What a More Realistic Strategy Looks Like
None of this means companies should allow a free-for-all. The case for governance is real. The risks of ungoverned AI use are real. But governance and uniformity are not the same thing. The goal isn't to force every team onto one platform for the sake of a simpler procurement conversation. The goal is an AI environment that is secure, useful, and aligned with how work actually gets done.
That might mean one core company-approved platform for general use, paired with additional approved tools for specific departments or functions where the fit and the risk profile are meaningfully different. It means clear policies about what can and cannot be entered into any model, regardless of which tool is being used. And it means training that goes beyond how to use the tool: into when to use it, what risks to watch for, and what responsible judgment looks like in practice for each team's specific work.
Thinking about AI adoption by department costs more than a blanket mandate. It takes longer. It requires more nuanced conversations. But it's more likely to produce adoption that actually holds, governance that actually works, and value that actually compounds.
The companies that get this right won't necessarily be the ones that move fastest. They'll be the ones that were honest enough about fit to resist the simplest answer.
Want more practical approaches like this? Explore my curated library of AI tools, prompts, and workflows at resources.taneilcurrie.com