Almost every company has now started AI projects, introduced tools or run first pilots. Expectations are high: more efficiency, better decisions, new business models.
Reality looks more sober. An MIT study found that only about five per cent of AI pilots make the leap into productive use — ninety-five per cent peter out. From my own work I know: The reasons rarely lie in the technology. They lie in the organisation.
Three core problems that reinforce each other
Inflated expectations
AI is no cure-all. Without a clear use case, without precisely stated target figures and without measurability, you are left with big promises and small effects. The State of AI report puts it plainly: the majority of companies experiment, but only a fraction draws measurable benefit. The reason is usually the same — expectations are not synchronised with strategy and reality.
Data and process chaos
“Garbage in, garbage out” applies to AI more than ever. Studies show that more than eighty per cent of AI projects fail not on algorithms but on poor data quality. Data sits in silos, is incomplete, has grown historically or is simply inaccessible. The biggest obstacle is not computing power but the missing data strategy.
Missing enablement
Even when the use case and the data are right, AI stays ineffective if people are not brought along. This is a people topic, not an IT topic. Around seventy per cent of employees feel uncomfortable when AI takes over management decisions. At the same time, Bitkom surveys show that seventy per cent of employees in Germany have received no AI training at all.
The result: shadow IT, mistrust, uncertainty. Employees have long been reaching for AI tools privately; at work they lack orientation.
What the companies where it works do differently
They start with the business, not the tool. The question is not “which model do we take?” but “what do we want to achieve for our customers, and what can we improve internally?”
They treat data as a product. More and more organisations create roles such as AI data stewards or compliance specialists in order to manage data as a strategic asset rather than a by-product.
They combine stability with adaptability. Deloitte calls this “stagility”. Years of iterative working pay off here — making processes pragmatically more flexible without losing focus.
Three examples from practice
Automotive group: self-service instead of a central project
An international manufacturer faced hundreds of potential use cases from its business units. Instead of central projects, a platform was built on which teams could develop their own applications — from quality checks in production to automated documentation. Alongside it, clear guard rails: data access, compliance rules, governance for traceability. Within a few months more than ten solutions were running in daily operations, not as pilots.
Logistics: routes in real time
A European group wanted to make its supply chains more resilient. The existing route planning worked on fixed rules — too slow for today's dynamics. An agent was built that combines traffic, weather and customer data. The result: measurably shorter delivery times, a double-digit fall in fuel consumption. Importantly, the dispatchers kept the decision; the system only proposed options.
Mid-sized manufacturer: spotting faults before they get expensive
A machinery manufacturer wanted to reduce scrap and energy consumption. Previous systems only detected problems after the fact. With sensors and continuous analysis, scrap fell by almost twenty per cent and energy use per unit dropped. Decisively, the skilled workers on the shop floor helped determine which indicators were monitored and which thresholds were set.
All three examples have the same thing in common: AI only takes effect when organisation, data and people work together.
What leadership, HR and teams must deliver now
Leadership sets the frame instead of steering the detail. Successful organisations show that it matters less to take every decision yourself than to set the frame. Define priorities, create transparency, connect use cases to company goals — and take responsibility for data quality, compliance and ethics.
HR becomes the architect of enablement. Standardised mass training is not enough. It takes reskilling, short learning units and individual learning paths — and new role profiles that become indispensable alongside AI.
Teams become designers instead of users. Teams allowed to develop their own ideas, work with data and reshape processes secure acceptance and the capacity to innovate. Autonomy in action, embedded in a stable frame.
Fazit
AI does not run by itself. It only adds value once organisation, data and people work together. Leadership must set guard rails, HR must enable capability, teams must be allowed to shape.
AI is a change topic, not a question of tools. Everything else stays a demo.
Sources
- MIT study on moving AI pilots into production — share of pilots that reach operations
- State of AI Report — ratio of experimentation to measurable benefit
- Bitkom survey on AI skills in Germany — share of employees without AI training
- Deloitte: stagility — the balance between stable processes and adaptability
- Project experience of CALADE GmbH — anonymised examples from 2021 to 2025
This article offers a professional assessment and does not replace legal or management advice.
