Skip to main content

Zuzana Fiantokova

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 apply system thinking in change management

Transformace ve firmách

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.

zeměkoule globus

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.

Seven Layers of Context That Decide Whether Your Transformation Succeeds

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?

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? 

Are you good at building relationships?

Spolupráce a vztahy na pracovišti

No, I’m not asking you into a relationship. But I do want your changes to work. I’m asking because this is exactly what decides today whether a technology change in a company really lands well.   We are all focused on the tools. AI. New platforms. New processes. New ways of working.   But technology does not create change on its own.   People do. And people do not follow a system. They follow trust, collaboration, and relationships.   When I speak about my experience implementing new technology in different countries, relationship building is exactly what created the foundation for high adoption and engagement. Not Excel. Not a slide deck. Not a perfectly documented project plan.   Relationships.   With the sponsor – the global leader. With the programme manager. With the subject matter experts most affected by the change. With HR teams in each country. With change ambassadors. With different local groups impacted by the change.   That is what created the space for trust, openness, faster responses to people’s concerns, and better collaboration across the whole change journey.   And it’s not only my experience. Prosci has consistently shown that employee engagement is one of the top factors in successful change.  Deloitte confirms that high-performing teams are built on respect, trust, and support.  McKinsey reminds us that without real buy-in and role modelling from leaders, transformation starts to stall.    And psychology is almost uncomfortably clear on this point: in moments of uncertainty, people first assess whether they are safe – and only then do they listen to what is actually changing.   So no: First the system, then the people. More like: First relationships, then collaboration, and only then real adoption.   Relationships cannot be rolled out like new software. They cannot be generated with a prompt. They are built slowly. Consistently. Through presence.   How consciously are you building relationships in your team today – before asking people to go through yet another change?

MYTH #02

Odpor ke změně

But we communicated it to people “I didn’t know this was happening.” Forty-seven messages. And people still didn’t feel informed.   “We told them everything. We did the maximum.” Over six months, we sent 47 separate communication items – newsletters, town hall recordings, videos from the director, plenty of emails.” Everything was prepared. Everything was sent. Everything went according to plan.   “I didn’t know this affected me.” That statement did not come at the beginning. It came late. Nine months after implementation, adoption was at 31 percent. Management could not understand it.   “This is the maximum we could have done.” No. This was the maximum you could have broadcast. Because the problem here was not signal strength. The signal was strong. The problem was reception.   A signal that is too strong turns into noise. And noise is something the brain automatically ignores. Not out of resistance. Not out of indifference. It is a survival mechanism.   And that is the lie companies keep repeating to themselves again and again: “If we communicated it a lot, we communicated it well.” You didn’t. You communicated it often. That is something entirely different.   In week seven of the transformation, employees received three separate emails about the new system in a single day. Each from a different sender. Each with a different emphasis. Each marked as important.   By week fourteen, most of them could visually recognise the transformation newsletter header – and closed it before even opening it.   Forty-seven items did not create awareness. They created an escape reflex. After every town hall, after every GMs video, employees could quote the transformation strategy. They knew the company was “going digital.” They knew the platform would bring “efficiency and transparency.”   But no one could answer these three ordinary questions:   That is not a lack of information. That is a lack of translation. The organisation had an excellent communication plan. But it forgot how to ensure understanding of the impact and a mindset shift. And so a gap opened between information and understanding. A gap into which 69% of users fell.   Employees do not understand the meaning of change through a corporate newsletter – especially one they have already learned to ignore. They understand it through familiar faces: their direct managers or colleagues. Through questions asked in a close and familiar environment. Through someone who can say: “For our team, this specifically means this…”   Prosci’s research is very clear on this point: Employees prefer to hear messages about the personal impact of change from their direct manager – not from HR, not from a communications team sitting somewhere at headquarters But from the person standing with them every Monday morning in the team meeting.   This company sent 47 messages through central channels.   Sending the same message content to everyone is not communication.   William Bridges separated two things that organisations still keep confusing: Change = the external event. Transition = the internal psychological process.   Companies manage the change. They leave the transition to chance. You can send people 47 accurate pieces of information about a change and still leave them completely alone in the process shifting their minds.  A mindset shift does not happen on the intranet. It happens in an employee’s head on Monday morning when they open the new system and do not know what to do if it does not work. At that moment, the GMs video does not help. Neither does the newsletter they have trained themselves to stop reading.   What helps is a manager or a change ambassador who has already gone through it with them. Or no one helps. And adoption stays at 31 percent.   People were informed. They were not prepared.   A strong signal ≠ change adoption   How is it in your organisation? What other ways does your organisation use when introducing change?

New job reality

Nová pracovní realita

It is already starting to peek through every crack and in every direction. And Forbes has finally written about it.   “Job roles are breaking apart.” The pressure is rising. Burnout is just around the corner.   “Traditional job positions are gradually breaking down into individual tasks that can be carried out by different types of workers – employees, external specialists, or the technologies themselves.” *(Forbes)*   I agree. But at the same time, I keep thinking – what is no one saying out loud?   Until now, most of the conversation has focused mainly on AI, automation, and new technologies. On tools. On productivity. On the future of work. On early adopters eagerly jumping into the new.   But the most important part has stayed in the background for far too long: What is all of this doing to people?   Very few people stop to think about the 70% who need time to accept change.   And yet Forbes itself writes: “Many employees are facing growing pressure to perform, alongside a higher risk of burnout. According to a number of studies, low employee engagement is among the main factors reducing company productivity.”   Companies invest in tools. In processes. In technologies.   Very few invest in how to actually help people move through that change.   This is not a side issue. This is reality – and it is already affecting companies, teams, and individuals.   So far, I have seen very little discussion about what these changes are doing to people’s mental wellbeing, their confidence, their identity, their sense of direction in life.   Forbes mentions adaptability and soft skills as part of the answer.   “Companies are also increasingly pointing to a lack of soft skills, such as collaboration, adaptability, or critical thinking.”   And I would add one more capability that is still talked about far less than it deserves:   The ability to go through change in a healthy, conscious, and supported way. Not only for employees. But also for managers. And yes, at C-level too.   Because: → Adaptability does not develop from a workshop on growth mindset → The ability to handle change does not appear automatically in a job description → Working with emotions during transition is not “soft” – it is a hard business issue   Change in work is inevitable. How people handle that change – that is a choice.   People need to learn how to deal with change. How to work with uncertainty. How to understand their own emotions. How to maintain their value in a world where work is being rewritten in real time.   What about you – is your company investing in people’s ability to navigate change, or only in the change itself?

5 mistakes I made before I knew what change management is

Chyby v change managementu

Every mistake I made early in my career became a lesson I now incorporate in change strategy. Which one shaped you the most? In my early HR Executive days, “change projects” often landed on my desk for one simple reason: Someone wanted to save costs or had a preferred supplier. Back then, I didn’t know much about change management. I simply rolled up my sleeves and got to work. Looking back now – from my change strategist seat – I see the blind spots clearly. ✨ Mistake #1 – Jumping in without the WHYI delivered the change before defining why it mattered – for the business and, more importantly, for the people affected. ✨ Mistake #2 – Focusing only on the tip of the icebergWe never gathered real business requirements or assessed change impacts. We assumed the obvious was obvious – it wasn’t. ✨ Mistake #3 – No structured planEverything was done intuitively. We reacted instead of anticipating. There was no roadmap to guide us through uncertainty. ✨ Mistake #4 – No back-up planWhen things backfired (and they did), we were surprised instead of prepared. ✨ Mistake #5 – Trying to change leaders, not approachesI thought I could shift their mindset without their buy-in.Lesson learnt: without motivation and understanding, there’s no will to change.   These early career missteps shaped how I approach change today – with clarity, structure, and heart. Because every transformation deserves more than good intentions. It deserves a plan, a purpose, and people who understand the why.