Most enterprise AI programmes share the same blind spot. Pilots run well at headquarters, adoption numbers look reasonable in the board update, and then the rollout hits regional teams, and the returns stop making sense.
Language is often the culprit. Google's April 1 update expanding language availability for Gemini-powered features in Workspace, including AI-assisted form creation, directly targets that problem. It is a small update on paper. In practice, it goes to the heart of why so many Workspace deployments underdeliver.
Why AI adoption stalls before it reaches the whole workforce
In February, UC Today reported on Google adding Gemini usage and threshold reporting to the Workspace Admin console. For the first time, IT teams could see exactly who was using AI features, and who had never opened them.
The picture was uncomfortable. Google's own research found that only 3% of organisations have meaningfully transformed with AI, with 72% still in early stages. Executives are 15% more likely than employees to report significant AI impact: a gap that suggests the two groups are not experiencing the same rollout.
Language contributes directly to that gap. Research from DeepL found that nearly 70% of US enterprises face daily operational challenges from language barriers, with 96% considering AI tools to address them. A 2026 review of AI adoption patterns, meanwhile, found that countries where lower-resource languages dominate show lower AI uptake even after controlling for economic factors.
Build AI productivity tools around English and a significant share of the global workforce stays in the zero-usage column. Zero usage means zero ROI.
The workflows where language friction costs the most
Form creation sounds minor. But forms start the high-volume internal workflows that drive real operational cost: IT and HR intake, purchase approvals, change requests, project submissions, facilities tickets, compliance sign-offs.
When an employee submits a request in a second language and the intent is unclear, the workflow does not fail, it just slows down. Someone asks a clarifying question. The requester replies a day later. A team assigns the ticket with incomplete information. It comes back. The cycle repeats.
Across thousands of internal requests per month, the cost is cumulative rather than dramatic. Delays, rework, and duplicated effort inflate the operational cost of collaboration without appearing on any single invoice.
If Gemini helps more employees submit clearer, more complete requests in their working language, the value is not better writing. It is fewer back-and-forth exchanges, faster throughput, and less rework — and those are outcomes finance teams can recognise.
