Skip to main content

Zuzana Fiantokova

Why Workarounds Are Not Resistance

Excel, který přežije každý nový systém. Change management

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

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?

One of your changes can wait a few weeks. Which one?

Change management

Our people are tired of change. How many times have you heard that sentence? I hear it and read it all the time. Last week, I heard it again during a mentoring session from someone whose organisation is running several transformations at the same time. I asked how many exactly. Silence. Then the answer: I don’t know. No one monitors that here. So I asked whether they had a canvas showing all the changes together in one place. They didn’t. They had never been asked to create one. Each of those changes has a sponsor, a plan, a budget, and a report showing green status. But no one is managing them as a whole. And yet the accountant who is dealing with a new system, a reorganisation, a new manager, and an AI pilot starting in spring does not see four separate projects. She sees a year in which almost nothing feels certain. And her capacity is not divided neatly between those projects, because each one assumes it has all of her attention. That is why I recommend creating a Transformation Canvas. Half a day. One wall. A flipchart. Sticky notes. And the people leading those changes in one room. You can do exactly the same online. Put every change that is currently underway or being prepared onto the wall, including its duration, the departments and roles affected, and the name of the person leading it. What starts to appear on that wall? – Two projects going live in the same month and affecting the same team – Departments carrying three changes at once, while others have none – Dependencies between projects that their respective leaders are unaware of – One manager through whom absolutely everything flows – A change that could be moved by six weeks without costing anyone anything That last one is often the biggest surprise. Sequencing can be changed. No one is simply making those decisions because no one can see the whole picture. Change saturation is not solved by better communication or more frequent training. It is solved by having someone who can see how much change is landing on people and who has the mandate to adjust the sequence. Imagine this in your organisation. If you put every current change onto one wall, how many sticky notes would there be? And how many of them could be moved? Sometimes we become so immersed in our own reality that we stop seeing the big picture. A small step back can open up entirely new perspectives and possibilities.

Myth #05

change management

“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?

Change management

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.

Myth #04

Change management

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.

Stakeholder Maps Aren’t Enough: Why Your Transformation Needs Personas Too

Mapa stakeholderů nestačí

For years, I was convinced that a well-built stakeholder map was a sufficient foundation for any transformation. Most projects do settle for this approach and on the surface, it works. You identify the key players, plot them by power and interest, plan your communications. Done. But after years working in change management, I’ve learned that this simply isn’t enough.   What a Stakeholder Map Does Well Make no mistake – a stakeholder map is an indispensable tool. It shows you: – Who holds the power to decide and steer direction. – Who has influence across the organisation. – Who has a stake in the outcome of the change. – Who you need to manage, mobilise, or simply monitor. This information is foundational. Without it, you’re navigating blind. But it only gives you half the picture.   When Personas Entered the Picture A few years ago, I started systematically bringing personas into my practice and it was an absolute game changer. Suddenly we weren’t just looking at roles and organisational positions. We started seeing people. – Their everyday experience. – The motivations that drive them. – The fears that hold them back. – The reality they actually work in. – And most importantly: what they need to feel, know, and be able to do in order to truly embrace the change. Personas shifted the conversation from “who’s on the project plan” to “who are we actually building this for”.   The Critical Difference If I had to capture it in a single sentence: A stakeholder map shows you who you need to engage. Personas show you how the change will actually land for them. And that distinction is where it gets decided whether you’re designing a change for a checkbox on a project plan, or for real human beings who have to live with it.   What Happens When Personas Are Missing You can have all the right people in the room. You can have your sponsors, ambassadors, and resistors perfectly mapped. And it can still fall flat. Because without personas, you’re often speaking to your stakeholders in completely the wrong language. The results are predictable: – Communication that doesn’t land. You send messages that are technically correct but say nothing to the people receiving them. – Training that never transfers into practice. People walk away with knowledge they can’t apply in their reality. – Engagement activities that look great on paper but miss the people they’re meant for. The workshop runs, attendance is recorded and nothing actually changes.   The Power of Combining Both What I know now is that the real strength lies in combining the two: – Stakeholder maps reveal influence, power, and political dynamics. – Personas reveal human experience, needs, and everyday reality. Change needs both. Strategic navigation through the stakeholder map and empathy built on personas. Lose the first and you lose direction. Lose the second and you lose the people.   Do you work with both of these concepts in your transformations? Or do you tend to lean on one more than the other? 

Why your transformation hurts and 4 ways to ease the pain.

“We’re preparing for a big bang in the company. How will people accept it quickly and painlessly?”   This was a question I was asked during a LinkedIn Live on the topic: Change management – an unnecessary luxury, or a necessity you can’t afford to ignore?   I’ll be brutally honest. It cannot be completely painless.   Even if you have built change management capability in your organisation and have an experienced expert on the project, change will always hurt.   Change will always hurt. Someone. In some way. To some extent.   It is scientifically proven that changing habits and ways of thinking causes the same physical pain as a physical injury.   Change affects habits. Certainty. Ways of working. People’s identity. What they know and what they believe in.   Some people are open to change. Others are perpetual resisters.   And the more changes are happening in an organisation at the same time, the more fatigue, resistance, and silent pushback grow.   The pain can be reduced. It cannot be eliminated.   How?   Clarify the WHY. Not in general terms – “we will be more efficient, agile, and modern.” But specifically – what does this change mean for leaders, for managers, for employees? It will be different for each group.   Build TRANSPARENCY and COLLABORATION across projects. Align with other projects – how you will inform each other about progress, risks, and resistance. Where are the overlaps, and where can you work together?   Name what is NOT CHANGING. People need to know what they can rely on. What in their established ways of working and thinking will remain. Communicate that regularly.   Set the RIGHT EXPECTATIONS. For yourself, for leadership, for managers, for employees. How? Have success metrics for the change. What does “accepted and adopted” mean for each group? Measure it regularly. Communicate it regularly.   This is what I consider the foundation. It is not everything.   I’ll share more techniques next time. They also form the backbone of the Change Essentials programme, which I built on my own experience in change management.

Why your stakeholders leave meetings confused and what to do about it.

Proč vaši stakeholdeři odcházejí z meetingů zmatení — a co s tím udělat

Have you ever sat in a meeting where you understood only half of what was being said? Acronyms. Charts. Status updates. Slides full of technical jargon.   And you sit there thinking: Why am I here? What do they actually want from me? And what of this is even relevant to me?   It feels like you are speaking two different languages. And that is exactly what meetings with business stakeholders in projects and transformations often look like. We invite people from the business. We explain what we are doing. But we stay inside our own bubble. We do not say why we invited them. We do not say what we need from them. And sometimes we do not even ask for the decision we urgently need.   We simply keep walking down our own well-worn path. It is not bad intent. It is professional blindness. We are so immersed in our expertise that we stop noticing what is unclear to the other side. We do not build bridges to the other side of the river. We do not extend a hand to help them cross successfully. We do not explain the change from the user’s perspective. We do not explain what it means for the business.   We are missing a basic skill that anyone introducing innovation, change, or new processes needs.   I call it Common Language.   The language most people speak. A skill that requires empathy, not just expertise. The ability to translate the complex into something clear. The ability to leave out what is interesting to the project but irrelevant to the other side. The ability to say: “I need this and this from you…” — instead of hoping the other person will guess your intention.   From my experience, HR people tend to do this naturally. Communication professionals too. For others, it is often quite a challenge. But it can be learned. Like any skill, it is a matter of practice and willingness. And also of empathy and self-awareness in the moment.   Once you start speaking common language, you begin to…