- Half of Large Companies Have Adopted Generative AI, But Only a Fraction Are Using It Effectively
- Organizational Push vs. Ad-Hoc Use: The Difference Lies in “Rules” and “Education”
- Learning from Ebara Corporation: The Winning Pattern of In-House Development
- Half Are Concerned About Accuracy: How to Resolve This
- Three Actions Leaders Must Take Now
- Summary: The 46.5% Adoption Rate Is a Milestone, Not the Finish Line
Half of Large Companies Have Adopted Generative AI, But Only a Fraction Are Using It Effectively
According to the latest survey by Teikoku Databank, the generative AI adoption rate among large companies has reached 46.5%. Research from Tokyo Shoko Research also reports that approximately 60% of large enterprises are promoting generative AI as an organization.
At first glance, AI adoption in Japanese companies appears to be progressing smoothly. However, I believe we need to view these numbers from both an “optimistic” and a “cautionary” perspective.
Why? Because behind the survey results, there are not a few companies that have “adopted AI but haven’t felt its effects” or “have left it to individual teams, exposing themselves to security risks.”
In fact, Teikoku Databank’s survey found that nearly half of companies are concerned about the accuracy of information generated by AI. This state of “adopted but unusable” is the real challenge that executives are facing right now.
From my own experience supporting AI adoption at over 38 clients, I can say there is a significant gap between adoption rates and actual utilization. Simply introducing a tool is not the end of the story.
Organizational Push vs. Ad-Hoc Use: The Difference Lies in “Rules” and “Education”
What’s noteworthy in the Tokyo Shoko Research survey is that about 60% of large companies are “promoting AI as an organization.” Conversely, the remaining 40% are leaving it to individual teams or the discretion of employees.
This difference directly impacts the results of AI utilization.
Companies promoting AI organizationally have established the following three elements:
– Development of usage guidelines
– Implementation of internal education programs
– Verification processes to ensure information accuracy
In contrast, companies that leave AI to individual teams often see the spread of so-called “shadow AI,” increasing the risks of information leaks and erroneous decisions. Moreover, because teams are experimenting in isolation, know-how isn’t accumulated, leading to a vicious cycle of knowledge becoming siloed with individuals.
This polarization is striking even among the companies I visit for consulting. In one manufacturing client, engineers had independently started using ChatGPT, but there were no unified rules, and management had no idea which tasks it was being used for.
Learning from Ebara Corporation: The Winning Pattern of In-House Development
Amidst this, the case of Ebara Corporation is worth highlighting. The company’s prototype bot, started by just two people, grew into a company-wide “generative AI project.”
The key was their choice of “in-house AI development” and “multi-cloud.”
Many companies tend to think, “If we introduce SaaS, AI adoption will begin.” But Ebara took the opposite approach. By customizing AI to fit their own operations and combining multiple cloud services, they achieved both flexibility and security.
I myself have built a multi-AI system using Claude Code, ChatGPT, and Grok in parallel, achieving a reduction of 1,550 hours of work per year. The key is not to rely on a single tool, but to choose the optimal AI for each purpose and make them work together.
Three lessons we can learn from Ebara’s case:
– Start small and build on successful experiences
– Customize AI through in-house development to fit your operations
– Diversify risk with a multi-cloud approach
Half Are Concerned About Accuracy: How to Resolve This
The fact that nearly half of companies in Teikoku Databank’s survey are concerned about information accuracy cannot be ignored. If left unaddressed, this issue will stall AI adoption itself.
However, with the right measures, this concern can be resolved.
Here are the three steps I practice:
– Clarify sources: Limit the data sources AI can reference (e.g., internal documents only, or only trusted public data)
– Build in verification processes: Create a system where humans always check AI outputs
– Establish feedback loops: When errors occur, analyze the cause and improve prompts or reference data
For example, when using AI for contract review, I always display the “original contract clause” alongside the “AI’s analysis results” and build in a workflow for humans to make the final decision. This ensures accuracy while reducing work time by 80%.
Three Actions Leaders Must Take Now
Based on the analysis above, here are three actions that CEOs, CTOs, and back-office leaders should take immediately.
– Establish usage guidelines
– Launch company-wide education programs
– Start with small successes
First, usage guidelines. Clarify what can be input, which tasks AI can be used for, and how to verify outputs. Without this, teams will be confused, leaving only risks.
Second, education. AI literacy is no longer just for IT staff. Every employee needs to understand “how to collaborate with AI.” At one of my clients, holding monthly AI study sessions reduced proposal writing time by half within three months.
Finally, start small. Trying to roll out AI company-wide all at once will inevitably fail. First, create a success story in one department or for one task, then expand it horizontally. Just as Ebara started with two people, a small start is the key to success.
Summary: The 46.5% Adoption Rate Is a Milestone, Not the Finish Line
The fact that generative AI adoption has reached 46.5% among large companies is a milestone in the digital transformation of Japanese companies. However, this is just the “beginning.”
What truly matters is how to “master” the AI you’ve adopted. Whether you promote it as an organization or leave it to individual teams—this gap will only widen.
I myself have created value equivalent to approximately 7.53 million yen (approx. $50,000) annually through AI utilization, but this was only possible because we “tackled it as an organization.” Individual effort alone could not have achieved these results.
I ask all leaders: Is your company’s AI adoption being left to individual teams? I hope this 46.5% figure serves as a catalyst for you to rethink your company’s AI strategy.


Comments