Why large organizations spend hundreds of millions on artificial intelligence while most employees use it for less than an hour and a half a week—and why this is primarily a UX problem, not a technological one.
Open ChatGPT or Microsoft Copilot. What do you see? A white box, a blinking cursor, and a prompt reading, "What are we working on?" This is precisely why ordinary people find it so difficult to use AI as anything other than a search engine.
The Numbers That Don't Appear in AI Presentations
Reports about AI sound impressive. 87% of large enterprises today say they are "implementing" AI. However, McKinsey's data distinguishes between implementation and actual deployment that delivers value. Only about 1% of organizations belong to the latter category.
Microsoft Copilot is the most widely distributed corporate AI tool in the world. Microsoft 365 has 440 million paying users. As of late 2025, 8 million of them—or 1.8%—were paying for Copilot, two years after its market availability. When employees can choose between Copilot and ChatGPT, 76% reach for ChatGPT, while only 18% choose Copilot.
According to a 2025 survey by S&P Global Market Intelligence, the share of companies that discontinued most of their AI initiatives before reaching production rose year-over-year from 17% to 42%. On average, organizations halted 46% of projects between the proof-of-concept phase and broader rollout.
Gartner predicted that by the end of 2025, at least 30% of generative AI projects would be abandoned after the proof-of-concept stage. Key reasons cited include low data quality, escalating costs, inadequate risk governance, and unclear business value.
The average manager in a large enterprise spends roughly an hour and a half per week using AI. That is less time than a routine LinkedIn scrolling session.
Where It Gets Stuck: An Interface That Offers Nothing
In product design, there is a concept few laypeople know by name, though everyone experiences it daily. It is called affordance—the visual clues an object or interface gives about how it should be used. A button looks like a button because it can be pressed. A slider looks like a slider because it can be dragged. A door handle suggests whether you ought to pull or push.
The empty text box of a language model has almost no affordance. It suggests nothing. It shows no list of capabilities, provides no examples of specific work situations where it might help, and sets no boundaries for its abilities. It simply waits for user input.
For someone who has not worked with AI before, this interface is virtually impenetrable. You know something is there, but you don't know what to do with it. It is like being handed a professional musical instrument without sheet music, without a teacher, and without anyone telling you what kind of music it can play.
The result is what we see repeatedly in organizations: employees open the tool, don't know what to write, and close it. After three attempts, they stop entirely.
Four Blind Spots of Today's AI Interface
The issue goes beyond surface appearance. Looking at current LLM interfaces through a design lens reveals four systematic gaps that explain why they fail even with motivated users:
Lack of orientation in mental space. A chat interface is an endless scroll of conversation. At any given moment, the user doesn't know where they are in the process, what has been decided, what remains hypothetical, what constitutes the final conclusion, or what data the model is relying on. The entire cognitive load of orientation shifts back to the human. We call this context management fatigue.
Lack of affordance for trust. A model responds confidently to almost anything. Yet the interface rarely indicates confidence levels, source quality, or where output reflects inference versus verified facts. Users need to know what a conclusion is built on and what might disprove it. This is not a model problem; it is a UX problem that current interfaces fail to address.
Lack of thought visibility. People doing complex work need more than just an answer. They need to see how the AI reasoned, what alternatives it considered, and what it ignored. Without this, a black-box effect occurs: output arrives, but how the model reached it remains opaque. Future interfaces will need to support inspectable cognition—thought processes that can be reviewed and edited.
Lack of calibration. With the rise of agentic AI systems, a new dimension comes into play. Today, it is rarely clear when AI is merely suggesting, when it is deciding, or when it is directly taking action. As model autonomy grows, interfaces must clearly communicate authority limits and action reversibility. Otherwise, trust in AI systems will rapidly erode.
This is a situation we have seen several times in tech history: the arrival of the graphical interface over the command line, early web browsers, the iPhone, and the mobile web. There has always been a moment where technology outpaced the interface, requiring a new way of working to be invented. LLMs are in that moment right now. Models can already generate intelligence at a level that would have felt like science fiction three years ago, but the environment for working naturally with that intelligence is only just being created.
The Problem Isn't Motivation; It's the Adoption Curve
Technologists are familiar with Everett Rogers' diffusion of innovations model, which describes how new technologies spread through society. At the beginning are innovators and visionaries—the early adopters. These are people who figure out how to use a new tool on their own, who experiment, tolerate quirks, and discover their own use cases. In corporate environments, they typically represent 10% to 15% of employees.
Next comes the early majority—the pragmatists. They aren't looking for technology for its own sake. They are looking to solve a specific problem holding them back today. They want to see that it works, saves time, and can be used without extra effort. This group accounts for another 34% of the market, and without them, no technology becomes standard.
An empty text field is designed for early adopters—for someone actively searching for something to do with the tool. The early majority lacks that inclination, nor should they need it. That isn't laziness; it is rational behavior. Why invest time searching for something no one has demonstrated as a clear solution to your specific problem?
AI Training Isn't Enough. You Need Concrete Solutions to Concrete Problems.
Most corporate AI programs follow the same pattern: licenses are purchased, prompting workshops are held, and employees are told to start using AI. Then, leadership waits for results.
Results don't come. People within organizations lack the capacity and time to invent how to integrate AI into their daily workflows on their own. Their job is not to experiment with technology; their job is to process contracts, prepare reports, answer emails, and attend meetings.
Investing in AI adoption does not work like investing in traditional software training. It isn't like the year 2000, when companies sat employees in front of computers and said, "This is how we work now." A computer performed clearly defined tasks and made its functionality obvious. A language model can do thousands of things, yet shows you none of them until you figure them out yourself.
An effective approach looks different. Instead of general training, the team receives a ready-made solution for a specific problem that genuinely slows them down: transcription and summarization of meeting notes; automated briefing preparation prior to client meetings; generating initial proposal drafts from internal templates; or analyzing document sets with outputs in a predefined format.
An employee does not need to understand what AI can do in general. They need to see that a specific task currently taking two hours can now be completed in ten minutes.
Why You Can't Fix This Once and For All
The environment is shifting at a rate unprecedented in enterprise software history. New features, new models, and new integration options arrive every week, not every few years.
A use case that was impossible or overly complex six months ago is routine today. Company employees waste time trying to reinvent the wheel because they don't know what can be done today compared to what was possible last year.
This is why it is critical for organizations to have a partner whose job is to track the pace of these changes—a partner who can step in and say: "This is how this is done today; this isn't possible yet, but will be in three months; and a solution exists for your specific topic that you might not know about."
The role of an AI advisor today is not to teach people how to prompt. It is to continuously map what new tools can do, translate that knowledge into concrete client situations, and recommend where to deploy ready-made solutions that deliver measurable time savings.
The Bottom Line
Low corporate AI adoption is not a technical problem. It is a problem of an interface that offers no guidance, combined with an approach that places the burden of experimentation on people who have neither the time nor the mandate for it.
The early majority—the segment of the organization that determines whether AI becomes standard practice or remains stuck in pilot phases—needs to see ready-made solutions to their specific daily problems. They need it to work immediately, without having to figure out how to integrate it.
Organizations that realize this ahead of their competitors—and stop funding generic training in favor of targeted implementations—will build a lead over the next two years that will be very difficult to close.
Kogi CON helps mid-market and enterprise organizations identify specific areas where AI realistically saves time and deploy working solutions without needing to train the whole company in prompt engineering. If you'd like to explore where untapped opportunities lie within your organization, reach out to us.