AI transformation is too often treated as a purely technical project — a mistake that gets expensive fast. Without a well-designed change process, teams don’t accept new systems, and even the best technology ends up having no real impact. Time and again, the projects that stall aren’t the ones with weak technology, but the ones that skipped the human side entirely.
Why It’s 70% Culture, 30% Technology
Lasting success in AI transformation comes mostly from people and culture, not from the technology itself. Ignore that factor, and you risk resistance, weak adoption, and — in the worst case — a project that fails outright. The „70% culture, 30% technology“ rule of thumb captures where attention and budget actually need to go in a transformation project.
In practice, this means the choice of AI tool is rarely the biggest risk. Far more decisive is whether employees understand why their way of working is changing, whether they trust the new processes, and whether leadership visibly walks the talk. Underestimate this dimension, and even a well-chosen system risks being quietly worked around rather than genuinely adopted.
The Three Phases of Successful Change Management
Successful change rarely moves in a straight line — it builds through phases, each demanding its own kind of attention:
- Listen: take the workforce’s concerns, expectations, and existing knowledge seriously — people who feel heard resist less and bring valuable practical insight into shaping the new process
- Facilitate: actively guide the change process instead of simply mandating it, with regular, transparent communication about progress, setbacks, and what comes next
- Enable: equip teams step by step to live the new structures in their day-to-day work, through training, pilot groups, and champions who act as go-to contacts for colleagues
Each phase needs time. Skip one — often because time pressure pushes straight to rollout — and the consequences usually surface months later as quiet resistance, or as employees running „shadow“ workarounds on the old tools they know.
Common Forms of Resistance — and How to Address Them
Resistance to AI projects rarely shows up openly. More often it looks like quiet worry about job security, a fear of being seen as „no longer needed,“ or plain skepticism about whether a new system can be trusted. These reactions are understandable and shouldn’t be dismissed as simple reluctance to change.
The most effective response isn’t top-down persuasion, but small pilot projects where employees experience firsthand how an AI-supported process actually makes their work easier — that’s far more convincing than any announcement. Being clear about exactly which tasks will change, and which won’t, helps as well.
Change Management and Knowledge Architecture Go Hand in Hand
A well-designed change process only reaches its full potential once it’s built on a solid knowledge foundation. Culture and structure — the two building blocks — should always be designed together. AI built on incomplete or unstructured knowledge disappoints regardless of how well-prepared the workforce is.
The reverse is equally true: the best knowledge architecture delivers little value if no one actually uses it day to day. That’s why we plan change initiatives and knowledge-base development together from the outset — the technical structure provides the foundation, while the change process makes sure it’s genuinely put into practice.
Talk to us about where you stand today.