by The Change Compass | Agile, Change Initiatives
Most of us work in organizations where change is the constant, and where at any one time there is a myriad of changes. What happens when there is a lot of changes being worked on? How do effective organizations manage change within this common environment? And what plays out when an organization adopts agile within this environment? Here we will illustrate how one organization effectively manages lots of changes within an agile environment.
Meet company A which is a typical financial services organization. They, like most other financial services organizations, are undergoing multiple changes. In change management theory land most are concerned with managing one change at a time. The reality for a lot of organizations is that there are lots of changes, some times up to hundreds of changes at a given point in time within an organization. This is not taking the lens of formal ’projects’ that would have formalized governance and resources in place to plan and deliver the initiative. From a user-centric lense, change is any initiative that involves changing a current way of working. These includes product changes, marketing campaigns, process changes, and role changes.
Like other organizations, company A has several business units, each of which has a range of initiatives that mainly impact their own business unit. However, some of these also impact other business units. At the same time, there is a company-wide body or governance group that determines which intiatives are to be funded centrally and are of higher priority, depending on the initiative benefit case, strategic importance and overall business value.
Towards the end of the year every year, there seems to be a phenomenon emerging in this company. Within an agile environment there are many agile teams are working in self-driven teams iterating on various changes. Many of the initaitives are also focused on delivering changes that impact frontline staff that work directly with customers. Most of these initiatives are aiming to implement the change prior to the end of the calendar year as the peak customer volume for this financial services firm tends to be between December and February. The idea is that if the changes were rolled out prior to December, then the change would take place in time to capture the peak volumes and therefore provide a quick realisation of benefits.
However, the scenario is that in true agile form, there is bound to be delays in each iteration. As each agile team starts to work through and iterate on the change, often there are technical delays or that the team realizes that the scope of the project requires a longer period of time to deliver. As a result, it is common to delay the eventual initiative go-live. When there are several initiatives aiming to go-live prior to the December period, this becomes a peak change impact period for the business. This means that there are simply too many initiatives trying to launch at the same time, causing operational performance challenges and business risks.
So how has Company A managed this situation?
Data
Armed with the quantitative data of the impacts of every initiative, programs, projects and initiatives, the picture was clear in terms of what this meant to the business. The frontline staff, as well as team leaders of the frontline, will require significant time away from their normal duties to understand, digest and embed the various changes. This presents real
challenges in terms of ensuring the right resourcing given the number of hours required to undergo changes. The business also has historical data of what happened last time this level of change had impacted the business and what this meant to business performance. The data also included the overall operational environment and any challenges including customer volumes, performance trends, etc.
Governance
A series of governance session was organized to zoom in on this specific scenario consisting of project delivery managers, change management, business leaders and other support professionals (e.g.initiatives risk). The session focused on discussing the various business risks and how to mitigate these risks, including prioritizing agreed critical initiatives,
understanding sequencing implications, and de-prioritizing non-critical initiatives. With each meeting, there was also continuing delays for some initiatives (again, in true agile form). As these potential or actual delays were socialized and shared, stakeholders kept updating their plan of attack to ensure the was an effective way of managing the situation.
The role of the change practitioner
The change management professional’s role in this context is to lead and facilitate the discussion of the governance and stakeholders so that there is clarity of what the data is telling us, what options we have to deal with it, and agreed actions forward. Program managers play a role in sharing ongoing progress in initiatives. Business stakeholders also play a critical role in understanding, accepting and agreeing to any actions, as well as sharing any shifting business performance priorities. However, the change professional plays a key role as the core of the problem as about managing and coordinating the amount and pace of change at a given point in time.
The solution
There was a series of solutions proposed to manage this overall peak change period:
1) Less critical initaitives were either pushed out or stopped. This lead to various re-planning exercises
2) Higher priority initaitives were clarified and agreed
3) A set of communication and engagement actions were proposed to better engage the impacted teams to help them joint-the-dots around the myriad of changes and what these meant
4) Careful and continual monitoring and reporting of business performance was emphasized to track the outcome of the changes
The illustrated case for Company A is a very common scenario for a lot of organizations within an agile environment. Initiatives cannot operate in silos if we adopt a user-lens in managing change and the impacts of change. This case illustrates how critical it is to have strong data that tells a clear story of what is going to happen to the business and what it means. Data enables effective and strategic conversations. Data also provides significant power and value in putting change management at the driving seat of business management.
by The Change Compass | Change approach
Telling compelling stories of change is one of the most underinvested capabilities in organisational transformation. Leaders spend enormous effort designing the technical components of a change — the new system, the restructured process, the revised operating model — but comparatively little time on the narrative that will make employees understand why it matters, what it means for them, and why they should commit to it. The result is change programmes that are technically sound but emotionally absent, where communications are accurate but not persuasive, and where the case for change exists in a strategy document but never lands in the hearts and minds of the people who have to live it.
This is a significant capability gap with measurable consequences. McKinsey research on organisational transformations consistently finds that clear, compelling communication of the change rationale is one of the strongest predictors of transformation success — and that the absence of a coherent narrative is among the most common causes of change resistance. Stories are not soft extras layered on top of the real change work. They are the mechanism through which change becomes real for the people it affects.
Why stories work where data does not
Most change communications lead with data: the business case figures, the efficiency gains, the market share rationale, the cost savings. This is understandable — leaders feel more confident presenting quantified arguments, and finance departments require them. But data alone rarely generates commitment. It generates comprehension at best, compliance at worst, and it almost never produces the emotional engagement that sustains behaviour change through the difficulty and disruption that real transformation involves.
The reason stories are more effective than data at driving behavioural change is neurological. Research published in Harvard Business Review on the neuroscience of storytelling found that narratives trigger the release of oxytocin — a neurochemical associated with trust, empathy, and cooperation — in ways that data presentation does not. When we hear a story that involves a character facing a recognisable challenge, our brains synchronise with the narrator’s. We feel the tension, the stakes, and the possibility of resolution. This neural coupling is what makes stories memorable and motivating in ways that spreadsheets are not.
For change leaders, this means that the most important communication about a transformation is not the business case slide with the projected ROI. It is the story of why this change is necessary, who it will benefit, what the organisation is moving away from and what it is moving towards, and what is at stake if the change does not succeed. Told well, this narrative creates the psychological conditions for commitment. Told poorly — or not told at all — it leaves a vacuum that is filled by rumour, cynicism, and resistance.
The anatomy of a compelling change story
Effective change stories are not simply positive communications about a programme. They have a recognisable structure that mirrors the structure of compelling narrative across all human cultures: a protagonist facing a challenge, a turning point that requires action, a path forward, and a vision of what success looks like. This structure is not manipulative — it is the shape that human beings use to make sense of their experience, and it is the shape that makes information most easily retained and acted upon.
The protagonist in a change story is almost always the audience — the employees who are being asked to change. Not the organisation in the abstract, not the leadership team, not the technology platform. The people sitting in the room or reading the communication, whose daily work is about to be affected. A change story that positions the employees as passive recipients of decisions made elsewhere does not generate commitment. One that positions them as agents facing a shared challenge — and that offers them a meaningful role in the resolution — does.
The challenge in a change story is the honest account of why the status quo is not sustainable. This requires candour that many change programmes avoid: the competitor that is gaining ground, the customer experience that is falling short, the process inefficiency that is costing the organisation in ways that are no longer tolerable. Leaders sometimes fear that this honesty will create alarm or undermine confidence. The research suggests the opposite: employees who understand the real reason for a change are substantially more likely to engage with it than those who receive sanitised communications that never explain why the organisation cannot stay where it is.
The turning point is the decision to act — the moment at which the organisation commits to a different path. This is where the change programme itself enters the story, not as the whole story but as the response to the challenge. And the vision of success is the specific, concrete description of what the organisation will look like when the change has worked: not in the abstract language of values and aspirations, but in the lived experience of the employees who will inhabit that future.
Three types of change stories leaders need to master
Different moments in a transformation call for different kinds of story. The most effective change communicators have a repertoire — they know which type of story to reach for depending on the audience, the stage of the programme, and the specific barrier they are trying to overcome.
The vision story is the foundational narrative: where are we going, why does it matter, and what will be better when we get there? This is the story that senior leaders need to be able to tell consistently and compellingly from the earliest stages of a transformation. Its purpose is not to answer all the questions — those will emerge as the programme develops — but to establish the emotional north star that gives the change meaning. The best vision stories are specific enough to be credible and human enough to be motivating. They describe the experience of a customer, an employee, or a community in the transformed world, not just the organisation’s strategic position.
The progress story is told during implementation, and it serves a different function. Its purpose is to sustain momentum through the period — which is longer and harder than most change plans acknowledge — between the initial excitement of launch and the eventual consolidation of the new way of working. Progress stories celebrate early evidence that the change is working: a team that has adopted a new process and found it genuinely easier, a customer whose experience has improved, a metric that has moved in the right direction. Research on the power of small wins published in Harvard Business Review found that visible progress, even in small increments, is one of the most powerful motivators of sustained effort. Progress stories make that progress visible.
The challenge-and-response story is the one that most change communicators avoid, but it is often the most credible and most powerful. It acknowledges that the change has not gone according to plan in a specific area — and then describes what the organisation did to respond. This is the story that builds trust, because it demonstrates that leadership is honest, that the organisation learns rather than just reporting its successes, and that the people who raised concerns were heard. In an environment where employees have lived through multiple transformations and have grown sceptical of communications that consistently present the programme in a positive light, the candid challenge-and-response story is frequently more persuasive than any amount of good news.
The role of specific detail in making stories credible
The single most common failure in change storytelling is abstraction. Leaders default to general language — “we need to become more agile,” “our customers expect a better experience,” “we need to compete in a rapidly changing environment” — because it feels safe and avoids saying anything that might be contested. But abstraction is the enemy of persuasion. Employees who hear general language about the need for change do not feel the urgency. They do not see themselves in the story. They do not understand what, specifically, is expected of them.
Specific detail does the opposite. A story about a specific customer who experienced a specific problem with the current process is more persuasive than a reference to “declining customer satisfaction scores.” A description of what a specific team’s daily work will look like under the new operating model is more motivating than a slide about “improved ways of working.” The specificity signals that the change has been thought through, that leadership understands the real implications, and that the vision is achievable rather than aspirational in the vague sense of that word.
Specificity also supports one of the most important functions of change storytelling: helping employees understand what the change means for their role specifically, not for the organisation in general. The question that sits behind almost every employee’s engagement with a change communication is “what does this mean for me?” A story that answers that question — even partially, even incompletely — is far more effective than one that does not. This is why the most effective change stories are told at the team level, by immediate managers who can translate the organisational narrative into the specific daily reality of the people who report to them.
Equipping managers to tell the story
The research is consistent on this point: the immediate manager is the most significant mediator of how employees experience and respond to organisational change. Prosci’s research on the manager’s role in change found that employees who rated their manager as effective at communicating about and supporting change were five times more likely to report successful personal adoption than those with ineffective managers. This places an enormous premium on manager capability in change storytelling — and an enormous responsibility on the change team and senior leadership to equip managers to perform that role.
Equipping managers to tell change stories well requires more than sending them a communication pack and asking them to cascade the key messages. It requires giving them the underlying narrative — the honest account of why the change is happening, including the parts that are uncomfortable — and trusting them to translate it for their team. It requires giving them sufficient notice and context to have genuine conversations rather than reading from a script. And it requires giving them guidance on how to handle the questions they are most likely to receive, including the ones that do not yet have definitive answers.
This preparation is different from message training. The goal is not to create consistency of wording across all managers — employees notice when their manager is reciting a script, and it is counterproductive. The goal is to create consistency of understanding, so that every manager is drawing on the same honest account of the change and can answer questions authentically, with their own words, in ways that resonate with their team’s specific concerns.
Using data to support the story rather than replace it
Data and story are not alternatives — they are complements. The most effective change communications embed data within a narrative frame rather than presenting the data and expecting it to generate its own meaning. A statistic that the organisation’s customer satisfaction score has declined by eight percentage points over two years is a data point. The story of the specific customers who experienced that decline, what it means for their relationship with the organisation, and what the organisation has decided to do about it, with the data as supporting evidence, is persuasive.
This principle extends to the way change measurement data is communicated during implementation. Adoption rates, readiness survey results, and training completion figures are all useful, but they are most powerful when embedded in a narrative about how the programme is progressing, what the data reveals about where additional support is needed, and what the organisation is doing in response. A measurement report presented as a table of numbers generates much less engagement than the same data woven into a story about the programme’s journey and the actions being taken to support the people who are finding the transition difficult.
Platforms like The Change Compass support this integration by providing change leaders and portfolio managers with the structured data — change load, impact distribution, adoption indicators by team and programme — that can anchor a credible story about how the portfolio is being managed. The data does not tell the story on its own, but it gives change communicators the factual grounding that makes their narrative credible to sceptical audiences, particularly at the executive and governance level where the story needs to be told in the language of evidence as well as the language of meaning.
Frequently asked questions
Why is storytelling important in change management?
Storytelling is important in change management because data and logical arguments alone rarely generate the emotional commitment that sustained behaviour change requires. Stories trigger neurological responses — including the release of oxytocin — that create empathy, trust, and motivation in ways that data presentation does not. Employees who understand the why of a change through a compelling narrative are substantially more likely to engage, adopt, and sustain new behaviours than those who receive only factual information about what is changing.
What makes a change story compelling?
A compelling change story has a clear protagonist — ideally the audience themselves — facing a recognisable challenge that is honestly described. It includes a turning point that explains why the status quo is no longer viable, a credible path forward, and a specific, human description of what success will look like. It avoids abstraction in favour of specific detail, and it is honest about difficulty and uncertainty rather than presenting an unrealistically positive picture.
How should leaders use stories differently at different stages of a change programme?
In the early stages of a transformation, the vision story is most important: it establishes why the change is necessary and what the organisation is moving towards. During implementation, progress stories sustain momentum by making small wins visible and demonstrating that the change is working. When difficulties emerge, challenge-and-response stories build trust by showing that leadership is honest about setbacks and responsive to concerns. Each type of story serves a different purpose and should be part of a deliberate communication strategy rather than generated ad hoc.
How do managers contribute to change storytelling?
Managers are the most important storytellers in any change programme because they translate the organisational narrative into the specific daily reality of their team. Their credibility with their team members — built through ongoing relationships — makes their version of the change story far more persuasive than anything delivered centrally. Effective change programmes equip managers with the underlying narrative, the honest context, and the guidance to handle questions authentically, rather than asking them to cascade scripted key messages.
References
by The Change Compass | Change approach, Change Initiatives
Recently, with the relentless pace of work, the changing weather conditions, and inadequate sleep, I had caught a cold. In recovering from the cold I started wondering more about the whole life cycle of sickness and wellness. Could it be that we can leverage from medicine how we improve the health of the organization as we design the change management process? In many ways, organizational health and well-being can be an analogy to how healthy a human being is. If the health of the organization is not great due to various imbalances in the system, it can fall ill and become less effective, thereby not meeting its goals, which is a topic often discussed in various organizational health blogs.
So how may we leverage the clinical approach that medicine adopts to disease treatment and maintenance of health to how we approach change management for positive change? In Medicine, the approach is based on the diagnosis, treatment, and prevention of disease. Let’s use these three phases to further understand what this approach means when applied in a change management context.
Diagnosis
One of the most important parts of being a medical practitioner is the ability to establish rapport with a patient. We have all been to doctors who spend barely 5 minutes with us and quickly subscribe pills before moving on to the next patient. Whilst the ramifications of limited rapport may not be great with a minor ailment, with complex diseases lack of rapport may result in the wrong diagnosis as important detail may have been missed or not prompted.
To effectively diagnose a patient the medical practitioner begins by taking the medical history before commencing on a physical examination. In a similar way, to really understand what is going on in the organization and why it needs to change we need to understand where it has been. Can an organization’s history can tell us why it is in the position that it is in currently? What are external factors? What has worked or has not worked in the past in undergoing change? What best practices have been used? Have there been incidents where change outcome was disastrous? What were the lessons learnt? What leadership style or ways of engagement has worked?
Similar to undertaking a physical examination, it is also important to analyze what conditions the organization is in currently prior to implementing a change. How effective are different levels of leaders is driving and engaging their teams on change initiatives? Is there any ‘signal loss’ in cascading information up and down or across the organization? What have been some of the common stories told about change? What systems are in place to support change initiatives? For example, change champions, communication channels or learning processes.
Diagnostic tools
Physicians leverage diagnostic tools in diagnosing a patient’s illness. This is based on what is presented by the patient and the physician’s overall assessment based on visible or inferred observations. For example, the DSM-5 is the Diagnostic and Statistical Manual of Mental Disorders that is used to diagnose psychological and psychiatric disorders. The physician does not blindly follow the diagnostic tools to formulate an assessment. In the same way in diagnosing the organization we should also seek to understand first and then make the diagnosis based on evidence (inferred or observable). In this way, we should not blindly follow a particular change framework in ‘diagnosing’ the organization as this depends on the organization as well as the chosen change framework.
In change management we do not have just one diagnostic tool, we have several frameworks in which to help our diagnosis. There is no one framework that is applicable in all situations. Different models may be useful in certain situation. The trick is to know which ones to leverage in the right type of situations. There are various models such as the Mckinsey STAR model, systems theory, SWOT analysis, nudge theory, or force field analysis to identify key issues across the organisations. Here, we focus on some of the more ‘change-specific models’.
John Kotter’s theory (8-step model) is great when applied to a significant strategy execution, restructuring or organization-wide change. In these situations, the strategy vision clarity has to be clear, a clear sense of urgency created and understood, and strong leadership coalition to drive through any employee resistance to the change. With this type of significant change leaders need to continuously drive and reinforce the change, and integrate this within the ways of working within the organization.
However, when the organizational change is more of a project such as a technology or process change, then the Prosci ADKAR change management model (Awareness Desire Knowledge Ability Reinforcement) model may be more relevant. This is a process focused model that aims to transition an individual from the current situation to the new state. Key enablers or activities may be executed on to help drive this transition. These include providing the right communications, addressing any employee inputs, training sessions, coaching and recognition for the right behaviors adopted.
When the change involves significant restructuring where there could be redundancies including role changes and people transitions then the Kubler-Ross model may be leveraged. The model outlines an individual’s emotional journey through loss and stages of grief during the change process. The journey starts with shock, denial, then frustration, depression, experimentation and finally decision and integration. As often with significant people transitions and job redundancies emotions are high and these need to be carefully addressed and managed. However, if the change is more focused on a simple process change where there is not a lot of heightened emotional reactions, this model may not be as useful.
The change practitioner is not always engaged or consulted at the beginning of a change initiative. Sometimes it is only when things are not going well and according to plan that the change consultant is engaged to turn things around. Irrespective of whether the change initiative is in the commencement or in the middle of the journey, effective organizational diagnosis is important to understand exactly what change intervention is required to address the situation. You may need to conduct focus groups as a part of employee engagement to get this data, and depending on the measurement model you take a Likert system analysis may be used.
Just as a good medical practitioner will utilize a combination of evidence/data and judgment according to diagnostic frameworks to determine the best course of treatment, the change practitioner should also follow suit. What types of data should be used to not only diagnose but also to subscribe treatment? The following is a summary of key types of data to look for and collect.
What is the change
– Why is the organisational change necessary?
– What does the change benefit? Its customers or its employees?
– What does the end state look like?
What is the impact
– Who is impacted by the change projects?
– What is the extent of the impact?
– What are the impacts on the role/person/organization? How does it affect organizational culture, organisational structures or organizational performance?
– What time period is the impact? In what ways?
– What are the change transition activities proposed?
Readiness for the change
– How ready are the impacted people for the change? What is the organisational diagnosis?
– How is this measured and reported for change management metrics?
– What is the minimum readiness criteria?
A good physician looks at the patient as a whole and not just the particular symptoms he or she is presenting. Based on the the symptoms presented, it could be that there are several disorders and not just one. In a similar way, a change leader needs to understand what the total picture of change in doing an organisational diagnosis is and not just isolate change to one project. Understanding what the totality of changes mean to the impacted stakeholder will go a long way in deriving what change approach or support is required.
To effectively diagnose a change situation the practitioner needs to use a data and evidence-based approach to understand where the organization has been, where it is and where it is going. Again using data, the practitioner needs to effectively frame the problem and diagnose the situation using the appropriate change model/framework(s). The right diagnose is critical to ensure the right change intervention is subscribed. For the same reason that wrongly diagnosing a patient could lead to further illness the same can be said for the wrong diagnosis of the change situation for an organization.
—————
If you enjoyed this article please share this with your contacts.
AI-Assisted Change Diagnostics in 2025
The field of change diagnostics has changed significantly since 2018. The most important development is the availability of AI-powered tools that can process large volumes of organisational data to produce a change diagnostic much faster and with much greater coverage than traditional interview-based or survey-based approaches.
Where a traditional change diagnostic might involve 20-30 stakeholder interviews over four to six weeks, an AI-assisted diagnostic can analyse HR system data, communication patterns, survey history, and project data to identify the highest-risk employee groups, likely resistance sources, and change capacity constraints in a fraction of the time. The qualitative depth of interviews remains valuable for understanding context and building relationships with key stakeholders – but as a complement to data-driven diagnostics, not as the primary method.
The Change Compass platform provides a structured change diagnostic capability that combines change impact data with workforce data to assess change readiness and saturation at the group level – enabling change leaders to make diagnostic decisions based on evidence rather than assumption.
Frequently Asked Questions
What is a change diagnostic in change management? A change diagnostic is a structured assessment conducted before a change programme begins, designed to identify the key risks, resistance sources, and readiness gaps that the change management approach needs to address. It typically covers the scale and nature of the change, the readiness and alignment of key leaders, the change capacity of affected employee groups, and the cultural factors that will influence adoption. A good change diagnostic prevents the change team from applying a generic approach to a specific organisational context.
What are the most common change diagnostic models? Commonly used change diagnostic models include the McKinsey 7-S Framework, the Burke-Litwin Causal Model, Force Field Analysis, and change saturation assessment. The right model depends on the diagnostic question – not all models are equally useful in all contexts.
How long does a change diagnostic take? A basic change diagnostic for a mid-scale initiative can be completed in two to four weeks. A comprehensive diagnostic for a large, complex transformation programme may take six to eight weeks. AI-assisted diagnostics that draw on existing organisational data can significantly compress this timeline while increasing the coverage of the assessment.