In this Change Practitioner Q&A series we talk to change managers to ask them how they approach their work. This time we are talking to Fiona Johnson.
Change Compass: Hi Fiona, describe yourself in 3 sentences.
Fiona: I’m a ‘seasoned” change practitioner who has survived many types of workplaces relatively unscathed ! Honestly, I could write a book about it. I always try and see the positive aspects of any workplace and do my best to enhance and support the cultural norms AND keep a sense of humour. I like to collaborate with professional and supportive team members and coach and mentor team members.
Change Compass: What has been the most challenging situation for you as a change practitioner? Tell us what happened and how you fared through it.
Fiona: I’ve had a lot of challenges, but I think the key is getting leaders to lead the change and supporting them.
I had an instance where I had to “sell” the benefits of change management to a very resistant Financial Controller. At the start of the project ( basically an operating model change) , he was totally focussed on the numbers and not the people and lacked the insight that change is always about people.
I had a team made up of business representatives and I set up regular fortnightly meetings to get his attention on issues we needed resolving and keep him up to date. I made the meetings short and sharp and each team members gave an update on the work they were doing to give them visibility. He realised the value of change management once the project delivered as that was when the gaps became evident. I think we were able to prepare him for the implementation but once the project wrapped up it was evident there was a lot of embedment activities not planned for and I think this would have caused more pain.
Although change initiatives are clearer now about the roles and responsibilities of the Sponsor and Business Owner, there is a still a reluctance amongst senior leaders to lead from the front in case it’s a failure and reflects negatively on them. I think this is an education piece and leaders need to trust change managers.
Change Compass: What are the most critical and most useful things to focus on when you first start on a project, and why.
Fiona: These tend to be the questions I focus on … • What are the business drivers? Why? Because this helps form the narrative and links to strategy and then to the frontline – “What’s in it for me?” • Who is the Sponsor and how actively engaged are they? They need to be involved and advocating throughout the project. • How much funding is set aside for Change Management ? I’ve implemented change on a shoestring but its better if there is funding for communication and training as this indicates consideration for the recipients. • What’s the organisations history of managing change – is there a “good” change example and what made it stand out, conversely what was a poor experience and what factors contributed to it ? • What is the culture like ? Take note of employees’ surveys as they provide markers on morale and pain points. • Finally identify a network of strong champions and advocates to help the change and provide them with the tools to do this.
Change Compass: As change practitioners we don’t often get to stick around to see the fruits of our labour, but from your experience what are the top factors in driving full change adoption?
Fiona: For me …. • Understanding the future state and identifying existing organisation metrics that can monitor and measure, or if there are gaps, ensuring these are filled before the change. • Handover to a committed business owner to manage and maintain momentum and who understands their role and responsibilities. • Building governance structures to review and report on the changes to the Executives or using existing forums. • Reporting and tracking are key but also other types of controls such as operating procedures and training. • Involving other areas such as QA, Compliance, HR and Finance in the discussions relating to embedment
Change Compass: You’re known to be great at explaining complex changes to stakeholders. What’s your secret?
Fiona: I have the grandmother test … would your grandmother understand this? Also, use basic communication rules such a targeting your audiences – there’s a difference between communicating to white collar and blue collar. Other tips include … • Use storytelling and personas your audience can relate to • Use your advocates and sponsors to spread the message. • Keep it simple and use a variety of mediums
One of the most feared aspect of change by organisations is its impact on performance. There is a wide variety of change which can determine the potential for performance dips during the change process. However, there is a significant body of research on the phenomenon of performance dip during system implementation. This refers to a temporary decrease in performance or productivity that often occurs when a new system is introduced or a significant change is made to an existing system. In this article we review key research studies on performance dips during change.
What are some of the research studies on performance dips during system implementation? Here are a few research studies that provide some insight into the degree of performance dips during system implementation:
A study published in the Journal of Computer Information Systems in 2019 found that performance dips during ERP implementation projects can range from 10% to 25% on average, with some organizations experiencing dips as high as 40%.
A study published in the Journal of Information Technology Management in 2011 found that performance dips during enterprise system implementation can range from 5% to 50% on average, depending on the organization and the type of system being implemented.
A study published in the International Journal of Information Management in 2016 found that performance dips during electronic health record (EHR) system implementation can range from 5% to 60% on average, depending on the organization and the level of customization required for the EHR system.
What about for transformation programs? What are some of the findings on how much performance could dip during the transformational change process?
Here are some examples of the percentage of performance dips observed in various transformation programs:
A study by McKinsey & Company found that organizations undergoing digital transformations typically experience a 10% to 15% dip in productivity during the implementation phase.
A research report by the Hackett Group found that companies implementing large-scale enterprise resource planning (ERP) systems experience an average performance dip of 5% to 15% during the implementation phase.
A case study of a large Australian bank’s transformation program found that the organization experienced a 10% to 20% dip in productivity during the implementation phase.
A study of 10 organizations that had implemented new supply chain management systems found that they experienced an average productivity dip of 12% during the implementation phase.
The percentage of performance dips
The percentage of performance dip with transformation programs can vary widely depending on a variety of factors, such as the size and complexity of the transformation, the industry, the specific processes and systems being impacted, and the level of planning and support provided during the implementation.
It’s important to note that these percentages are only rough estimates, and the actual performance dip can vary widely depending on the specific context of the transformation program. Organizations can minimize the impact of performance dip by carefully planning and managing the implementation process, providing appropriate training and support to employees, and monitoring performance closely during and after the implementation.
Why causes the performance dip?
One key factor that contributes to performance dip is the learning curve associated with the new system. Users need time to become familiar with the new software or hardware and may initially struggle to complete tasks at the same speed or with the same level of accuracy as they did with the previous system.
Another factor is the disruption to established workflows and processes that can occur during system implementation. When a new system is introduced, it often requires changes to the way work is done, which can lead to confusion and delays until everyone adjusts to the new way of doing things.
Research has found that performance dip tends to be most pronounced in the initial stages of system implementation and can last anywhere from a few days to several months, depending on the complexity of the system and the level of support provided to users during the transition.
Overall, it is largely change management factors that can cause performance dips. For example:
Resistance to change. When employees are asked to change the way they work, they may resist the change, leading to a decline in performance. Resistance can be due to various reasons, including fear of the unknown, lack of understanding of the reasons for the change, and concerns about job security.
Implementation issues: When new processes or technologies are not implemented correctly, they may not work as intended, leading to a decline in performance. Implementation issues can be due to various reasons, including inadequate planning, insufficient resources, and unrealistic timelines.
Communication breakdowns: When communication between stakeholders breaks down, it can lead to confusion and misunderstandings, leading to a decline in performance. Communication breakdowns can be due to various reasons, including inadequate planning, insufficient resources, and unrealistic expectations.
Organizational culture: Organizational culture can also contribute to performance dips during transformation programs. When the organizational culture does not support change, employees may be resistant to it, leading to a decline in performance. Organizational culture can be due to various reasons, including leadership style, history, and values.
What about performance dips when there are multiple changes going on?
Research has shown that implementing multiple changes simultaneously can lead to a higher risk of performance dips. Here are some examples of research studies that have explored this issue:
“The Effects of Multiple Change Initiatives on Perceptions of Organizational Change: Implications for Employee Outcomes” by Michael Tushman and Philip Anderson (2004): This study found that implementing multiple change initiatives at the same time can lead to increased uncertainty and confusion among employees, which can lead to a decline in performance.
“The Effect of Multiple Change Programs on Employee Well-being and Work Outcomes: A Longitudinal Study” by Michal Biron and Yair Bamberger (2012): This study found that implementing multiple change programs simultaneously can lead to increased stress and burnout among employees, which can negatively impact their performance.
“The Impact of Multiple Change Initiatives on Perceived Organizational Performance” by Matthew Davis and Stephen Taylor (2008): This study found that implementing multiple change initiatives simultaneously can lead to a decline in perceived organizational performance, which can impact employee morale and motivation.
“Managing Multiple Organizational Changes: The Role of Prior Change Implementation and Timing of Change Initiatives” by Sebastian Kunert and Christiane Stenger (2019): This study found that implementing multiple changes simultaneously can lead to a higher risk of performance dips, but that prior experience with change implementation and careful timing of change initiatives can help to mitigate this risk.
Overall, these studies suggest that implementing multiple changes simultaneously can lead to a higher risk of performance dips. However, it is not that organisations should simply avoid implementing simultaneous changes. Morever, implementing simultaneous change is a fact of corporate life and continuous development. No modern organisation can survive by implementing only one singular change at a given time.
How to avoid performance dips across the portfolio of change initiatives
“Managing multiple change initiatives: the role of planning, sequencing, and implementation” by Jelena Spanjol and Susan Ashford (2018): This study found that careful planning and sequencing of change initiatives can help to reduce the negative impact of multiple changes on employee performance. The authors suggest that organizations should prioritize changes based on their strategic importance, and implement changes in a way that minimizes disruption to employees.
In particular, the following 3 points have been highlighted.
Prioritization: Organizations should prioritize changes based on their strategic importance, and implement changes in a way that minimizes disruption to employees. This can involve aligning changes with the organization’s overall strategy, and ensuring that employees understand how the changes will benefit the organization.
Timing and sequence: The timing and sequence of changes can have a significant impact on employee performance. Organizations should consider the timing of changes relative to other initiatives, as well as the sequence of changes. For example, changes that are more disruptive to employees may be better implemented after other, less disruptive changes.
Coordination: Effective coordination of multiple change initiatives is crucial to minimize the negative impact on employee performance. Organizations should ensure that there is clear communication and coordination between different departments and teams involved in the changes, and that there is adequate support and resources available to employees to help them adapt to the changes.
In fact similar findings have been concluded across various McKinsey studies as well. Having clear prioritisation and sequencing is absolutely integral to deliver significant value to the organisation across the initiative portfolio. 40% more value. That is correct. Organizations that are focused on prioritizing and sequencing across the initiative portfolio can gain 40% more value than those that do not.
If you’re keen on achieving 40% more value across your change portfolio have a chat to us about how The Change Compass digital solution can help you do just this.
How to avoid performance dip during system implementation change initiatives
Here are some research findings from different articles on how to reduce performance dips during system implementation projects:
1. “Reducing Performance Dip During Implementation of Large-Scale Information Systems” by David Straub and James King (1996): • Encourage and support employee participation in the implementation process. • Provide adequate training and education on the new system. • Communicate effectively with employees about the changes and their impact. • Provide adequate technical support and resources. • Establish clear and specific goals for the implementation process.
2. “Managing multiple change initiatives: the role of planning, sequencing, and implementation” by Jelena Spanjol and Susan Ashford (2018): • Develop a comprehensive change management plan that includes communication, training, and support. • Prioritize and sequence change initiatives to minimize disruption and avoid overload. • Provide clear and consistent communication about the changes and their impact. • Involve employees in the design and implementation process. • Monitor and address resistance to change.
3. “A multi-level model of employee attitudes toward organizational change” by W. Matthew Bowler et al. (2010): • Foster a positive attitude toward change by providing clear and consistent communication, support, and training. • Encourage employee participation and involvement in the change process. • Provide resources and tools to help employees adapt to the change. • Monitor and address resistance to change. • Recognize and reward employee efforts to adapt to the change.
4. “Reducing the Performance Impact of Software Upgrades” by Albert J. Simard and Lionel P. Robert Jr. (2004): • Develop a comprehensive training program that focuses on the most relevant features of the new system. • Provide ample opportunities for practice and feedback. • Establish a clear and specific timeline for the implementation process. • Communicate effectively with employees about the changes and their impact. • Provide technical support and resources to address any issues that arise.
In conclusion, research suggests that organizations that use a combination of these change strategies are more likely to avoid performance dips during transformation programs at a portfolio level. By carefully managing and monitoring the portfolio of initiatives, providing appropriate training and support to employees, and continuously improving performance, organizations can ensure a successful transformation that delivers the desired benefits.
There is no change curve. A single change curve doesn’t exist in most organisations. The concept of a single change curve means you’re always looking at it from the myopic lens of a single project or a single change. If we adopt a humanistic and human-centred view, what we see is that at any one time there are likely multiple change curves happening, to the same person, the same team, the same organisation.
At any one time, an impacted stakeholder maybe undergoing the 3rd iteraction of changes in one project, whilst partially adopting the new behaviours of another project, whilst just learning about the details of yet another project. And it may not even be projects or programs. It could be smaller team-led continuous improvement initiatives.
The concept of Agile methodology has revolutionized the way organizations approach software development and project management. It emphasizes flexibility, adaptability, and continuous improvement. However, the frequent introduction of multiple Agile changes within an organization can lead to multiple ‘S’ curves, which can result in several challenges related to adoption and business performance and capacity.
Multiple S curves refer to the continuous introduction of new Agile changes, each of which leads to a new adoption process and a corresponding performance improvement. This results in a series of S-shaped curves, each representing a different stage of the Agile adoption process.
The S curve is assuming that all of the changes are well implemented with good people experiences. The initial curve shows the slowness of the change adoption in the beginning, followed by a faster change adoption process, and finally capering off.
However, when the change is not well implemented due to various reasons the experience can be more like a V curve, where the experience and performance dips down into the ‘valley of despair’, followed by a ramp-up of improving experiences and change adoption.
The introduction of multiple Agile changes within an organization can lead to several challenges related to adoption and business performance and capacity. Firstly, continuous change can lead to confusion and uncertainty among employees. It can be difficult for employees to keep up with the latest changes and understand how they should adjust their work processes accordingly. This can result in decreased productivity and morale among employees.
Moreover, frequent changes can also result in increased cognitive strain and workload for employees. They may need to continuously learn new processes and techniques, leading to burnout and decreased job satisfaction.
Another challenge of having multiple Agile changes is that it can lead to decreased consistency in processes and outcomes. Each change may result in different outcomes and different ways of working, making it difficult to standardize and measure performance. This can result in a lack of accountability and a decrease in the organization’s overall efficiency.
In addition to the challenges related to adoption and performance, multiple Agile changes can also result in a decreased business capacity. The frequent changes can disrupt established workflows, making it difficult for teams to complete projects in a timely manner. This can lead to decreased project velocity and increased project risk, making it challenging for the organization to meet its goals and objectives.
So, while Agile methodology is a powerful tool for organizations, the frequent introduction of multiple Agile changes can result in several challenges related to adoption, performance, and capacity. To mitigate these challenges, organizations should take a strategic approach to Agile adoption, ensuring that changes are well-planned, communicated effectively, and implemented in a controlled manner. By doing so, organizations can ensure that the benefits of Agile methodology are realized while minimizing the risks associated with multiple changes.
To truly manage the multiple change curves, data is key. Without understanding which change curves are happening at what time it is not possible to manage change holistically. With data, you can easily drill into what is happening when, to whom, to what extent, and in what way. It is only with data that we can effectively orchestrate change across the board.
If you are going on a journey to capture change impacts across the organisation, be aware of how you are capturing the data so that you are truly addressing business issues critical to the organisation. For example:
Ensure that the data captured can be easily formatted and visualised to support a range of business decision-making contexts without too much manual work. The more manual the set up of the data is, the more time and effort it requires to answer the various data cuts that stakeholders may be needing
Balancing critical data points required versus having too many data fields and therefore too Cumberland and difficult to capture the data. The more data you are required to collect, the more complex the process is for those whom you are collecting the data from
Thanks to the nature of agile projects, the data will change constantly. The tracking of constantly changing change data is critical. However, it should also be easy and quick to update the data
Organisations under changes will invariably have changes in organisational structures, teams or roles. Ensure that your data-capturing process makes it easy to update the structure as they change.
Have a chat with us to understand more about how to leverage digital solutions to multiple change impacts across the organisation, and how to leverage AI and automation to make your lives easier in leveraging a data platform to make critical business decisions using change impact data.
So next time you talk about THE change curve, just be aware that you’re likely not adopting a people-centric view of change. You may want to look more holistically at what your impacted stakeholders are undergoing or about to undergo. Adopt a holistic mindset of what impacted stakeholders are going through as you plan out your change approach.
If you’re interested in exploring more about managing agile changes check out the following:
Change is an inevitable part of, not just corporate life, but life in general. It’s a natural occurrence that we all must face at some point. But despite the many benefits that change can bring, many of us are still reluctant to embrace it. After all, for many, it is easier to keep doing the same thing than to do something different and unknown. With the unknown comes risks. Risks that may be scary. Risks that things may be worse than the current scenario.
Often resistance to change can be thought of as an outcome of bad change management. If you don’t effectively manage your stakeholders or have not effectively assessed the impact of change, there is likely going to be change resistance. Resistance may arise from bad change interventions, including ineffective consultation or engagement of stakeholders.
However, sometimes despite everything you’ve done. You’ve ticked every box and followed almost a ‘textbook’ approach to the change process. Despite this, you are still getting change resistance from some stakeholder groups. Why is this happening?
Sometimes there may be very few levers you can pull in preventing the resistance. You’ve gotten your leadership cohorts to reinforce and evangelize the purpose and benefits of the change. You’ve tried all you can to reach the hearts not just the minds of what you think impacted employees want to hear.
Why is this happening? It could be the fear of loss, or loss aversion, that has led to the resistance. This is the research-backed fact that people tend to have a cognitive bias where the pain of losing is much stronger than the pleasure of gaining.
One example of this phenomenon is why people stay in bad marriages. Despite the obvious benefits of leaving an unhappy marriage, many people still choose to stay in it. This is because they fear the loss of familiarity, comfort, and security that their marriage provides. This is despite how unhappy they honestly are in the marriage. They may also be afraid of the unknown or the changes that come with divorce. These same fears and reluctance to change can also be seen in organizations facing change.
For something less dramatic, another example could be changing phones. We are wedded to our phones for a big chunk of how we run our lives. Changing a phone operating system, brand, or even model can be a quite a change that a lot of people are not inclined to go through, until they are pushed to do it.
When organizations decide to implement changes, they often focus on the potential benefits that will come from the change. They may present a logical argument for why the change is necessary and how it will benefit everyone involved. However, even with a clear and logical argument, people may still be reluctant to embrace change. This is because change often means loss, even if it is the loss of something negative or unwanted.
For example, if an organization decides to implement new software, employees may resist the change even if it will make their jobs easier and more efficient. This is because they are comfortable with the current system, and they fear the unknown or the potential loss of skills that they have developed with the current system. They may also fear that the new system will require them to learn new skills or take on new responsibilities. This can be despite your best efforts to create a positive picture of the end state.
There are still lots of examples in organisations where employees prefer to stick to their current manual ways of work using spreadsheets, versus the more efficient and effective digital tools.
They may have created the spreadsheet themselves. They may have spent months building consensus across the organisation to use this process. Changing this process could mean not only a lack of familiarity, but it could also result in a loss of their ‘importance’ of their role. So as a result, people continue to maintain the status quo. Stay within the comfort zone. After all, if they don’t change, they can’t be ‘blamed’ if something goes wrong.
As change practitioners, we cannot just blame those impacted by the change. We may also need to see if this applies to us. For example, a lot of change practitioners still use manual spreadsheets to create a ‘single view of change’ despite the amount of manual work that is required. They may have faced leaders who question the integrity of the rating system or become ‘bored’ with the same heatmap or chart since they can’t use it to make black-and-white business decisions. But, fear of the unfamiliarity dominates.
Organizations need to recognize this fear of loss and work to address it. Here are some practical suggestions for designing change initiatives that can help tackle this barrier:
1. Look at the data about how your target employees have responded to different types of changes in the past. What types of responses were there with a certain type or volume of change? How were these dealt with? What were the outcomes? What types of employees were more ‘resistant’ than others?
2. Communicate Clearly, early and Transparently: Slow change adopters may need more time to prepare for change and what it means for them. Is there another option if they do not like the end state? What if they disagree? Communication should be clear, transparent, and empathetic. It should focus on the benefits of the change, and address any concerns or fears employees may have. It should also focus on what would happen if the changes are not adopted.
3. Involve employees in the Change Process (where it makes sense): Inviting employees to participate in the change process can help them feel more invested in the change and less fearful of losing control. When employees have a voice in the decision-making process, they are more likely to feel valued and respected. This also allows businesses to identify potential challenges and concerns that employees may have, which can be addressed before the change is implemented. This approach may need to be applied carefully, especially when dealing with a highly resistant group of employees. If not carefully managed, the change approach may get out of control.
4. Provide Support: Change can be overwhelming and stressful, especially when employees feel like they are not equipped to handle it. Providing support and training can help employees feel more confident and prepared. It can also help them see the benefits of the change more clearly. This may sound like common sense. But it’s amazing how many change initiatives don’t provide any support to impacted groups, beyond technical support.
5. Celebrate Successes: Change can be a long and difficult process, so it is essential to celebrate successes along the way. Recognizing and acknowledging employee efforts and successes can help maintain momentum and motivation. This is another seemingly ‘no-brainer’. Designing a series of successes help create positivity.
6. Be Patient: Change takes time, and employees need time to adjust. It is essential to be patient and understanding. Rushing the process or ignoring employees’ concerns can lead to resistance and resentment. In your change readiness assessment or baselining phase of the project, if you’ve found that change adoption could be slow and resistance could be expected, ensure you’ve factored in sufficient timing.
Change is difficult, even when it makes logical sense and has many benefits. People are often afraid of losing something, even if it is something negative or unwanted. Organizations need to recognize this fear of loss and work to address it when implementing changes. Recognising this cognitive bias is the first step. By providing support, and resources, and involving employees in the change process, organizations can help reduce the fear of loss and successfully implement change.
A good change adoption dashboard can make or break the full benefit realization of a change initiative. It captures the essence of what stakeholders need to focus on to drive full change adoption. This visual representation of the status and progress of a change initiative provides real-time data and insights into how well-impacted employees are adopting the change and what steps can be taken to improve adoption rates. In this article, we will outline the steps for designing an effective change adoption dashboard.
Change adoption is often only measured toward the end of a change initiative. This is a mistake since the adoption journey can start as early as the project commencement, or when stakeholders start hearing about the initiative. At a minimum, change adoption should be defined and agreed upon before significant change impact happens. If you are implementing a system this will be well before the system go-live.
These are the key steps in building a great change adoption dashboard.
Step 1: Define the Objectives of the Change Initiative
The first step in designing a change adoption dashboard is to clearly define the objectives of the change initiative. This includes understanding what the change is, what it aims to achieve, and what the desired outcomes are. Understanding the objectives of the change initiative is critical to defining the metrics that will be used to measure adoption and success.
If your initiative has a long list of objectives, be careful not to be tempted to start incorporating all of these into your dashboard. Your task is to pin down the most critical change management objectives that must be met in order for the initiative to be successful. If you are really struggling with how many objectives you should focus on, aim for the top three.
Step 2: Identify Key Metrics
Once the objectives of the change initiative have been defined, the next step is to identify the key metrics that will be used to measure adoption and success. These metrics should be directly tied to the objectives of the change initiative and should provide actionable insights into the progress and success of the change.
Some examples of metrics that can be used to measure change adoption include:
Stakeholder engagement levels (depending on your stakeholder impacts these could be customer, employee or partners)
User adoption rates
Process improvement metrics
Time to adoption
Feedback from employees
The key is to locate the few metrics that will form the core of what full change adoption means. As a general rule, this often means a behaviour change of some kind. Here are some examples.
If the goal is changing a business process from A to B. Then you are looking for employees to start following the new process B. Then, identify the core behaviours that mean following process B.
If the goal is to start using a new system, then you would focus on system usage. Also focus on tracking any workarounds that employees may resort to in order not to use the system.
If the goal is to improve customer conversations, then you would focus on the quality of those conversations using key indicators. This may involve call listening or customer satisfaction ratings.
Again, ensure you are not over-extending yourself by picking too many metrics. The more there is, the more work there is. Having too many metrics also lead to attention dilution, and you start to loose stakeholder focus on the more critical metrics compared to less critical ones.
In the group of metrics you’ve chosen, if there is no behaviour measure then it is likely you may have missed the most critical element of change adoption. In most cases, behaviour change metric is essential for any change adoption dashboard.
If your change process involves too many behaviour steps, then focus on ones that are easier to track and report on. In a system implementation project, they could be system usage reports or login frequency.
Examples of target behaviours as a part of behaviour change
Step 3: Choose the Right Visualization Techniques
The next step in designing a change adoption dashboard is to choose the right visualization techniques. The visualizations should be chosen based on the data that needs to be displayed and the insights that need to be gained. Some examples of visualization techniques that can be used include:
Bar graphs: to display changes in metrics over time
Pie charts: to display the distribution of data
Line charts: to display changes in metrics over time
Heat maps: to display the distribution of data on a map
Selection of charts can be technical, and your goal is always to choose the right type of chart to make it easier for the audience to understand and interpret. Minimise on having too many colors since this can be distracting and overwhelming. Use colours carefully and only to show a particular point or to highlight a finding. Choosing the wrong chart can mean more questions than answers for your stakeholders, so choose carefully.
Beyond just having a collection of charts, modern dashboards have a mixture of different types of visuals to aid easy stakeholder understanding. For example, you could have different data ‘tiles’ that show key figures or trends. You may also want to incorporate key text descriptions of findings or trends in your dashboard. Having a mixture of different types of information can help your stakeholders greatly and avoid data saturation.
Example of chart styles from The Change Compass
Step 4: Design the Dashboard
Once the objectives, metrics, and visualization techniques have been defined, the next step is to design the dashboard. The design should be intuitive and user-friendly, with the ability to drill down into the data to gain deeper insights. The dashboard should also be accessible to all stakeholders, including employees, managers, and executives.
Data visualisation is a discipline in itself. For a general overview and key tips on chart design and selection visit our article to learn more about data visualisation techniques.
To reduce manual work in constantly updating and producing the dashboard for your stakeholders think about leveraging technical solutions to do this for you. A common approach is to use excel spreadsheet and PowerBI. This may be feasible for some, but it often involves using a PowerBI expert (which may come at a cost), and any time you want to change the dashboard you need to loop back the expert to do it for you.
The Change Compass has incorporated powerful and intuitive dashboarding and charting features so that you do not need to be an expert to create a dashboard. Reference our templates as examples and create your own dashboard with a few clicks.
An Example of a Change Adoption Dashboard from The Change Compass
Step 5: Test and Refine the Dashboard
The final step in designing a change adoption dashboard is to test and refine it. This includes testing the dashboard with a small group of stakeholders and getting their feedback. Based on their feedback, the dashboard can be refined and improved until it provides the insights and data that stakeholders need to drive change adoption.
A key part of this step is testing any automation process in dashboard generation. Is the data accurate? Is it recent and updated? What operating rhythms do you need to have in place to ensure that the process flows smoothly, and that you get the dashboard produced every week/month/quarter?
Step 6: Continuously Monitor and Update the Dashboard
It is important to continuously monitor the change adoption dashboard and update it regularly. This will help to ensure that the dashboard remains relevant and provides the most up-to-date information on the progress of the change initiative.
The reality is that stakeholders will very likely get bored with the same dashboard time and time again. They will likely suggest changes and amendments from time to time. Anticipate this and proactively improve your dashboard. Does it drive the right stakeholder focus and conversation? If not, tweak it.
Good stakeholder conversations mean that your stakeholders are getting to the roots of why the change is or is not taking place. The data presented prompts the constant focus and avoids diversion in that focus. This is also a journey for your key stakeholders to find meaning in what it takes to lead the change and reinforce the change to get business results.
Summary
Designing an effective change adoption dashboard is a critical step in ensuring the success of change initiatives. By providing real-time data and insights into how well employees are adopting the change, a change adoption dashboard can help key stakeholders make informed decisions and take action to improve adoption rates. Ultimately it is about achieving the full initiative benefits targeted. By following the steps outlined in this article, change managers can design a change adoption dashboard that provides the insights they need to drive change adoption.
Building and executing a change adoption dashboard can be a manually intensive and time consuming exercise. Leverage technology tools that incorporates automation and AI. You will find that this can significantly increase the speed in which you are able to execute on not just the change dashboard, but driving the overall change delivery. For example, you can leverage out-of-the-box features such as forecasting and natural language query to save significant time and effort.
Have a chat to us about what options there are to help you do this.
