What is happening inside the people you are presenting the AI transformation to?

Before you present the change timeline next time, look at that day through the eyes of the people in the room: Tuesday, 10:04. All-hands. The slide behind the CEO says “Working smarter with AI.” Then the sentence lands. Some positions will be replaced. Details in the coming weeks. Your body knows before your mind does. You hear your own pulse. Your face goes warm. Someone asks a question and the voice reaches you as if through water. Adrenaline is getting you ready to run. There is nowhere to run in a town hall. By lunch you are not hungry. Or you eat the sandwich and taste nothing. The gut has its own nerve network wired straight to the brain. It got the news first. The afternoon turns to fog. You open the follow-up email and read the same paragraph three times. Nothing sticks. Stress hormones quietly turn down the exact part of your brain you need right now, the part that holds several things at once. Evening: wrung out and wide awake at the same time. Tired but wired. The most reliable marker there is. 3:47 You surface from sleep as if someone flipped a switch. The meeting replays. This time you ask the question you did not ask, with better lines. Your brain is rerunning the data, trying to build a model of a future nobody has given it. The days after are stranger. Your jaw aches and you cannot say why. Choosing lunch feels like a decision with consequences. A two-word reply from your boss reads like a verdict. A closed door means something. You are fine at breakfast, furious by eleven, moved to tears by an advert at nine. And under all of it, one quiet question: who am I, if not the person who does this job? Even the commute you complained about for years suddenly looks like something you could lose. None of this is weakness. It is a healthy brain doing exactly what it was built to do when the future goes missing. Research on uncertainty keeps showing the same thing: not knowing registers in the body almost like a known threat. If you lead change, this is what sits in the rows in front of you while you present the timeline. The rollout plan is fine. Then people enter.
Why Workarounds Are Not Resistance

Have you ever implemented a new system, only to find that people keep going back to the spreadsheet they have been using for the last twenty years? I have seen this many times. That spreadsheet lived with five people. They knew every formula, every hidden column, and every exception someone had added years ago. Three departments worked with it. Then came the new system. It could do the same thing, only automatically and without copy-paste errors. And yet, the three departments kept opening that spreadsheet. Not everyone. But most of them. Why does this happen? Because no one explained to those people what the new system was supposed to give them. Or what the company would gain from it. Because they did not have time to build trust in it. They were not involved when it was being designed. Because no one asked them what kind of outputs they needed, and in what format, so that the system would make their work easier, not harder. And because they were not involved in planning the go-live either. One day, an email arrived saying that the system was launching and that they should attend a two-day training. By the way, this is a completely reliable recipe. If you want your spreadsheets to survive the next three systems as well, do exactly that. Because workarounds are not resistance. They are a message about what was skipped in the preparation. What can be done differently is not complicated. It just needs to happen early enough: The people who will work in the system are involved in the design. Not at the end, as an audience. Someone asks them what they need to see and in what format. And their answer is reflected in the requirements. The explanation does not start with system functionality, but with what will change in their Tuesday afternoon. The go-live is planned with them, not for them. And after the launch, someone continues to own the change. This is what change management means. It is not about the system. It is about the people who are expected to start working in it on Monday. Whether they understand why. Whether they trust it. Whether they were involved early enough. And whether the new way of working makes sense to them. What spreadsheet is still surviving in your organisation?
Myth #06

“Employees won’t even notice that we’ve been acquired.” Not long ago, I was having coffee with a friend. She works in payroll. Her employer has been acquiring one company after another at a rapid pace. And every time, the same scenario plays out. No change management. No impact assessment. Nothing. “Why not?” I asked. “Because leadership says that nothing really changes for employees anyway.” And yet she sits exactly where the changes become visible first. She processes payroll for several companies that have become one over the past two years. And she knows that from a legal perspective alone, something always changes for employees. The company name changes. An addendum to the employment contract may be required. Different rules and processes apply. If there are trade unions in the organisation, it becomes even more complex. It is not just a piece of paper for an employee to sign. A small process detail. Invisible to leadership. For the person receiving an addendum to sign, it is the beginning of a whole series of questions. This is the illusion companies often repeat to themselves during acquisitions: “It’s just administration. We change the company name on the contract and carry on.” But the name on the contract is not just administration. It is a signal. And the brain reads it as change, even if management sends it as a formality. The employee receiving that addendum does not care about the legal entity. They care about how the change affects them. “What does it mean that my contract is changing? Will I have to work differently? Will there be new rules? Will I keep the same manager, or will I get a new one? Does what we agreed last year still apply?” In an acquisition, it is not only the name on the contract that changes. What changes is whose rules now apply. One company takes over another. With that comes the way approvals work, the company culture, the language people use, whether people leave at five or stay until seven, who is trusted, and what is actually considered good performance. Two cultures walk through the door, but the expectation is that only one will live there. That is not a change of stamp. It is one of the most demanding changes a company can impose on people. And most employees learn about it in fragments. From an addendum. From a new logo in the email footer. From a new brand manual. From the fact that a colleague who used to approve something is no longer allowed to. No one has told them what specifically is changing for their role, because no one asked that question on their behalf. William Bridges described this in his transition theory. Change is an external event. A new name on the contract, a new owner, a new logo. It can happen in a single day. Transition is what a person goes through internally, and that takes much longer. You can sign the change on Friday. Employees may go through the transition for months. Leadership sees an effective date. The employee lives through the uncertain period between what they knew and what they do not yet understand. This gap is exactly what a change impact assessment can help identify in detail. It is the tool that asks what the change means for specific groups. – What changes for Payroll? – What changes for Sales, which now reports into a different structure? – What changes for the team whose manager is no longer their manager? Different groups. Different impact. Different questions. Without this analysis, leadership works with one average, generic idea of “the employee.” The assumption that “nothing changes for people” is not harmless. It is a decision not to look. A change impact assessment is exactly the tool that can change that. And it is not useful only for mergers and acquisitions. You can use it across all types of change and transformation: technology, AI, process, and culture. It is also one of the topics we cover in the Change Academy Masterclass. You can sign a contract in a day. It can take years to bring cultures together.
What is the role of HR in an era of continuous change?
Quite often, organisational leaders assume that HR’s role during change is to communicate and deliver training. But that is a very misleading view. At an HR breakfast for the Association of HR Professionals, I asked several questions, including these two. And the answers explain much of why change initiatives in organisations fail to deliver as expected. The first question: “How many changes are currently affecting one of your employees?” Most of the audience did not choose “one” or even “two to three.” They chose the option that there are more, but they can no longer quantify them. No one is counting those changes. No one is managing them as a whole. The second question: “When were you, as HR, brought into the change?” Most people answered: only after the decision had already been made. Or when the project was already underway and communication needed to be sent out and training planned. An organisation overloaded with change needs someone who understands people, keeps an eye on capacity, impacts, and the sequencing of change. Yet HR often gets a seat at the table only when all that remains is the role of communicator. Because change management is still too often confused with communication and training. It is not a communication campaign. It is a structured process that enables people to move to a new way of working sustainably and with measurable results. It has its own lifecycle, from the first day of an initiative through to embedding new habits. And HR brings the greatest value at the beginning. Before there is even anything to communicate. By the very nature of its role, HR understands people. It is the voice of employees and a mirror for leadership. Those are extremely important roles and attributes. I sat in that HR chair myself for ten years. At the time, I managed change intuitively, inconsistently, and without much structure. It cost me far more energy than it needed to. And those changes did not always stick. When change is managed reactively rather than proactively, change fatigue arrives very quickly. At the same time, many of those initiatives fail to deliver what their sponsors originally expected. When were you last brought into a change initiative?
Myth #05

“When change makes sense, people will accept it.” Early in the morning, an email arrived from the CEO announcing a new way of working and a new organisational structure, effective immediately. Three paragraphs about revised processes, a new organisational structure, and a new operating model. Not a single sentence about what would change for specific people in specific roles. At two o’clock that afternoon, a town hall was held to provide more information. The CEO and COO explained the logic: faster decision-making, clearer accountability, fewer approval layers. It all connected neatly. The presentation was beautifully structured and clean, using the company’s new colours and branding, which were also introduced as part of the changes. The email received that day by one of the procurement managers was also sent to the warehouse, Finance, IT, and all the support functions. The same message for everyone. No one had done a change impact assessment for her team. No one had identified her as a key stakeholder, even though twelve people reported directly to her. The message was not designed for her or her team because no one had analysed what the change would specifically mean for her role and department. After the town hall, she quietly said to a colleague by the coffee machine: “I understand it. It makes sense. But I don’t know whether I’ll still be here in a month.” No one had lied to her. But no one had answered the questions she had not dared to ask out loud during the meeting. The brain does not process change simply as information. It processes it as risk, assessing that risk through five different sensors at the same time, not just one. In 2008, David Rock described these in the SCARF model: Status Certainty Autonomy Relatedness Fairness Many questions linked to these five areas run in the background of every workplace interaction. During a major change, whether it involves structure, processes, or ways of working, they all light up at once. Will I still be someone who knows what they are doing in the new way of working, or am I starting from zero? What will still apply tomorrow if the rules I have worked by until now are changing? How many decisions about how I do my work will I still be able to make? Will I continue working with the same people in the same way? Am I expected to change as much as everyone else, or not? And many more. The manager by the coffee machine did not need more logic. She needed an answer to one of those questions. She did not receive it, not because leadership deliberately ignored her, but because the process that should have produced that answer had never taken place for her. Fourteen days later, something changed. No, no one organised another town hall. She was contacted by a colleague from another department was appointed as a change ambassador for her area,. Someone who had been involved in an early engagement network from the beginning of the project. He told her what he knew before leadership formally announced it. The only issue was that this could have happened earlier. Before the email was sent. Before the town hall was broadcast. That same week, she received an invitation to a short conversation with her manager. The discussion was not based on the generic company-wide presentation, but on an impact assessment conducted specifically for her team. They discussed three things: – what would remain within her area of responsibility – who she would continue working with – and that the same criteria had been applied across the team when decisions were made about the new roles. Autonomy, relatedness, fairness, named openly, clearly, and factually. Someone had mapped them beforehand. They had not been estimated based on instinct. Those fourteen days of uncertainty had been somewhat unnecessary. She left that conversation feeling different. Not because the change had become smaller, but because it had stopped being a vague threat and had become a concrete situation she could work with. This is where most transformations stop. The project team delivers one intervention like this, presents it as evidence that “we are addressing the human side of change,” and then the next phase of the transformation, often the final one, continues without an intervention map and without support. SCARF describes what is happening in a person’s mind at that moment. It is an extremely valuable tool for helping people understand and embed change. But SCARF alone is not enough. A stakeholder map. Personas. Change impact assessment. A change ambassador network. Communication tailored to specific groups. A learning strategy. Adoption measurement after go-live. Each of these phases exists because SCARF sensors do not light up only once. They light up again and again during every project stage, for different people and with different intensity. Skip stakeholder mapping and persona identification, and you do not know who will be affected most. Skip the impact assessment, and you send a generic message where a specific one is needed. Skip adoption measurement, and you may never discover that those sensors have been activated again. One well-managed conversation does not mean the change has been accepted. It does not mean that SCARF has been resolved and ticked off either. The real work is to move through the entire change cycle, from the analytical phase through to the months after go-live. This is exactly where attention tends to disappear: during the post-launch period, when everyone believes the change is already behind them. But the sensors are still lighting up there too.
How to engage people in transformations?

Why do we need to involve people in change? Because presentations do not change behaviour. People do. In my earlier HR leadership roles, I experienced changes that were designed without the people affected by them. A small group created the solution behind closed doors. Everyone else learned about it only a few days before launch, when the decisions had already been made and there was almost no opportunity to influence anything. Today, I design change differently. I involve different groups at different stages, based on the knowledge, experience, and influence they can bring to the change: – Senior leaders from the very beginning We align on the why, the direction, and the non-negotiables. If leaders do not genuinely stand behind the change, the rest of the organisation will notice immediately. – Experts and people who actually do the work during solution design They see the exceptions, risks, and everyday realities that no steering committee can identify from behind a desk. Their involvement helps ensure that the solution is not only well designed, but also workable in practice. – The HR community throughout the entire change HR often hears concerns and questions before the project leadership does. Its role is therefore not limited to distributing communication. HR can help capture signals from the organisation and respond to them more quickly and sensitively. – Change ambassadors from design through implementation They are close to the teams and have a direct sense of what is happening within them. They test messages, gather feedback, and translate the change into the language of everyday work. When involved early, they become trusted guides for their colleagues. – Managers before and during implementation They are the translators of change for their teams. If they do not understand the change, do not believe in it, or have no space to ask their own questions, the message will be lost or distorted on its way to employees. Different roles. Different stages. The same principle. Involve people while they can still influence the change, not only when they are expected to accept it. When working with clients, I therefore ask: Who needs to be at the table now, not later? Where are we merely informing people instead of genuinely involving them? How can we use their experience to make the change more practical and effective? Because when people first see the change only after it has already been finalised, it is too late for genuine co-creation.
How to apply system thinking in change management

You never introduce change into a vacuum. When you change one part of a system or organisation, it is never only that one part that changes. In a leadership meeting or presentation, it often looks simple. We implement a new system. Adjust a process. Redesign the organisational structure. Train people. Then reality enters the picture. The new solution affects roles, decision-making, capacity, mindset, collaboration, motivation, informal relationships, and even what people are actually rewarded for. Systems thinking in change means stopping looking at individual activities in isolation and starting to see the organisation as an interconnected system. What does that mean in practice? Do not ask only: “How do we convince people to accept the change?” Consider instead: “What across the organisation supports, or blocks, the new way of working?” In practice, this means looking at change from several perspectives: – Change never impacts only one area. Technology impacts processes. Processes change roles. Roles change relationships and decision-making. And all of this shapes the way people think and behave. – People’s behaviour is shaped by their environment. What we label as resistance may be a logical response to conflicting goals, poor processes, overload, or unclear priorities. – Strategy and everyday reality must be connected. Leadership may support the change, while pressure on middle management, local habits, or operational realities block it. Systems thinking connects strategy, governance, managerial behaviour, and employees’ everyday experience. – Every intervention can create side effects. A company introduces AI expecting higher productivity. But if its processes have not been mapped and people do not know in which situations AI can genuinely help them, they will use it inconsistently, or not at all. The result is not time saved, but more experimentation, uncertainty, and different ways of working. Technology alone will not increase productivity. It must be clear where, why, and how it should be used. – Context matters more than blindly following a methodology. The same approach will not work equally well across countries, teams, and divisions. Organisational history, trust, culture, change fatigue, and parallel initiatives all shape how people respond to change. Systems thinking in change management regularly reminds us of an uncomfortable truth: People are not a problem that needs to be fixed. They are often simply responding to the system we have created for them, while being given no space for feedback, discussion, or involvement. Where do you most often look for the root cause of problems in your change initiatives, in people or in the system?
How I participated in research by Birkbeck, University of London, focused on managing change in multicultural settings.

In a global, multicultural transformation, translating the same plan into several languages is not enough. This year, together with 19 other change experts working in international environments, I took part in research organised by the Change Management Institute and Birkbeck, University of London, focused on managing change in multicultural settings. Many of the findings confirmed exactly what I experience in practice. A one-size-fits-all approach does not work. The global strategy can remain the same. The way it is implemented, however, needs to be adapted to the local context. Communication, stakeholder engagement, work with managers, workshop formats, the pace of decision-making, and the level of autonomy given to local teams may all need to differ. This does not weaken the global direction. It creates the conditions in which the change can genuinely work within a specific context. The research also reinforced something else for me: a change practitioner cannot enter every country as the expert who already has all the answers. They need to be ready to challenge their own assumptions. Listen before explaining. Ask before proposing a solution. Understand the context before applying a methodology. What stood out to me most in the research findings? 1. A multicultural environment is not only a source of complexity “Cultural differences and constraints” can support creativity. Different perspectives can reveal weaknesses in the original design. Local teams can significantly improve the change, provided we do not treat them merely as recipients of a global decision. 2. Not everything we label as “national culture” is actually national culture Corporate culture, organisational history, leadership style, or the habits of a particular team can influence people’s behaviour just as much, and sometimes even more. So where should we begin when managing change in a multicultural environment? By setting aside assumptions and automatic judgements. By listening actively. By communicating without imposing. And by being genuinely willing to accept that a different approach is not necessarily worse. It may simply be better suited to that particular context.
Myth #04

Managers are the bottleneck. They are the reason why our transformation is failing. The organisation was changing its structure. New teams, new roles, a new operating model. On the slides, it all looked logical. At an offsite leadership meeting, the design was approved in a single day. The next morning, managers received an email. Subject: Changes to the organisational structure — effective as ofJuly 1. The sales team manager read the email on the train. Then again in the office. Then waited to see if anything else would follow. Nothing did. That afternoon, he had a team meeting. Seven people. Several questions he could not answer. Who approves priorities now? How is my role changing? What will I be measured on? What tools will we get to handle the extra work you now expect from us? He answered carefully. Said it would be clarified. That details were still being finalised. That more information would come soon. Three weeks passed. Nothing came. But he did hear one thing. A message spreading among leadership: “Middle management is the bottleneck. They are holding this transformation back” You have probably heard this before: resistance to change comes from below. From people who do not understand the strategy. From those who are not change-positive enough. But resistance often does not start with employees. Without a briefing. Without a mandate. Without the space to say: “This will not work like this in real operations.” Statistically, people managers are often described as the biggest bottleneck in organisational change. Prosci, McKinsey and Gartner all point to their critical role in whether change succeeds or stalls. McKinsey found that the likelihood of a transformation succeeding increases 5.2 times when managers can explain the meaning of the change to their teams. Not if they are asked to forward a slide deck. Not if they just repeat lines from a town hall. But actually if translate what is changing in people’s daily work — and why it matters. And to do that, they need If they do not get that, they improvise. They go quiet. They soften the message. They delay. They translate the change in a way that at least helps the team survive the next quarter. From the outside, it looks like resistance. From close up, it looks like someone who protects their team from the ambiguity of the system. Before you label managers as the bottleneck, do two things. A manager in change is not a distribution channel for leadership decisions. They are a translator of reality. And a translator cannot translate anything without the original content. So before you call managers the bottleneck, ask one question: What exactly did you give them and what did you simply assume they would figure out on their own? Managers do not hold change back. The system does – when it fails to prepare them for it.
Seven Layers of Context That Decide Whether Your Transformation Succeeds

Why one methodology isn’t enough and how cargo cult change management is born Two transformations. Two organizations. Essentially the same change – a technology transformation. And yet, two completely different approaches. Another example: one organization, one global strategy, impact across five countries. One change strategy – five adaptations. Different environments, different cultures, different operating models, different numbers of parallel initiatives, different change histories, different levels of change fatigue. This is where I find myself as a Change Management consultant. And in these situations, one theory isn’t enough. One framework isn’t enough. One methodology isn’t enough. I have to know more than theory. I have to read context. And understand people. You won’t learn this from books or theoretical training. Only from practice. Seven layers to pause on before pushing one approach for everyone 1. History of change How many times have these employees already been “transformed”? What survived, and what crept back? Change fatigue is a very real currency. 2. Trust in the change sponsor The same message from the same person carries different weight after five years of consistent action than after recently cancelled bonuses. 3. Cultural element National, professional (manufacturing vs. sales), and corporate culture, including formal and informal power networks. 4. Change saturation How many initiatives are running in parallel? People have a capacity for absorbing change and it isn’t infinite. 5. Timing in the business cycle Year-end close, seasonal peak, fresh layoffs. This determines what’s realistically feasible. 6. Political terrain Who wins in this change, who loses and who thinks they lose, even when they don’t. 7. Emotional state Hope, cynicism, exhaustion. The same message lands differently in a different context. Without context, you get cargo cult Without this understanding of context, cargo cult change management emerges: blindly following one approach for every transformation and every group of people. Carbon copy. Same communication. Same training. Same timeline. Same expectations across every group. This is where the famous “70% of transformations fail” is also born. The framework usually isn’t what failed. What failed is the assumption that any framework, on its own, is enough. Contextualization translates generic change into the specific reality of each group. And this is the core craft of change management. How often do you really adapt change to context in your organization — and how often do you just copy the approach from the last project?