Using Change Data to Maximise Business Results Through These 4 Systems Thinking Principles

Using Change Data to Maximise Business Results Through These 4 Systems Thinking Principles

Change management practitioners are often tasked with ensuring that transitions are smooth and successful. However, to truly excel in this role, it’s crucial to embrace a systems thinking approach—an understanding that organisations are complex, interconnected systems where every change can create ripple effects throughout. One of the most potent tools for fostering systems thinking is the use of change data within change portfolio management. Here, we will focus on how change data can build interconnectedness across the organisation, enhance the management of change initiatives, and ultimately improve business results.

Understanding Systems Thinking

The below are some of the core principles in Systems Thinking and how they may be applied to change portfolio management through data and analysis.

Principle 1: Interconnectedness

At the core of systems thinking is the principle of interconnectedness. Organisations are not merely a collection of individual parts; rather, they consist of various components that interact in complex ways. When change is initiated in one area, it can have unintended consequences in another. For instance, a change in the sales strategy might impact customer service processes, employee motivation, and even supply chain operations. By recognising these interconnected relationships, practitioners can make more informed decisions that take the broader organisational context into account.

In fact, change impact assessment is the process of identifying and ascertaining the linkages across the system.  With each change, the various impacts across different processes, people working to support those processes and the systems involved in the processes.

Principle 2: Feedback Loops

Another fundamental aspect of systems thinking is the identification and understanding of feedback loops. These loops can be either reinforcing (positive) or balancing (negative). A reinforcing feedback loop occurs when a change in one part of the system leads to further changes in the same direction, creating a cycle of growth or enhancement. For example, an increase in employee training may lead to improved performance, which in turn boosts morale and reduces turnover, further enhancing overall productivity.

Conversely, balancing feedback loops act to stabilize the system. They can dampen the effects of change, preventing extremes from occurring. Recognising these feedback mechanisms allows practitioners to leverage positive feedback loops to enhance desired outcomes while being vigilant against the negative loops that may emerge, which could undermine the change initiatives.

Here is an example of a feedback loop –

Goal: Prevent stagnation or failure by adjusting strategies based on real-time feedback.

  • Use case: Ensuring that deviations or resistance are managed effectively to keep the change on track.
  • How it works:
    • Collect data from employee surveys, performance metrics, and feedback sessions to understand what’s working or not.
    • Identify points of resistance and take corrective actions (e.g., additional training or clarifying leadership vision).
    • Example: If employees express frustration with new tools, gather input and refine the rollout to address concerns.

What are key benefits of feedback loops?

  • Increased adaptability: Ensures the organisation can react to unforeseen challenges during implementation.
  • Engaged workforce: Employees feel more involved when they see their feedback incorporated into the process.
  • Sustainable change: Continuous feedback ensures that change efforts stay relevant, preventing them from losing momentum or being abandoned.

Principle 3: Causality

Systems thinking also emphasizes understanding causality—how different components of the organisation influence one another. This perspective is vital in change management, as it shifts the focus from merely addressing symptoms of problems to exploring their root causes.  This can be applied throughout the change lifecycle ranging from understanding the impacts across the organisation, through to anticipating resistance and motivation levels to support the change.

Here is an example of applying the principle of causality in systems thinking

Change Initiative: Implementing a New KPI-Based Evaluation System

  • Initial Cause: Leaders decide to replace the existing subjective performance reviews with measurable KPIs to improve accountability.

Direct Effect: Employees shift their focus to achieving their KPIs.

  • This change seems positive—employees now have clear, measurable targets to meet.

Ripple Effects Across the System:

  • Short-term unintended outcome: Employees may begin to focus only on achieving their KPIs, ignoring tasks that are not directly rewarded, such as collaboration or innovation.
  • Behavioural impact: Some employees might feel micromanaged or disengaged if they view the new system as rigid or unfair.
  • Team dynamics: Competitive behaviour between employees could increase, reducing collaboration and creating silos.

Long-term Causal Feedback:

  • Lower collaboration can negatively affect innovation and employee morale, leading to attrition of high performers.
  • balancing feedback loop emerges when HR notices a decline in collaboration scores and recommends revising KPIs to include teamwork-related metrics.

Principle 4: Holistic Perspective

Adopting a holistic perspective is crucial in systems thinking. Instead of viewing the organisation as a set of isolated parts, practitioners should consider the organisation as a dynamic whole. This approach enables better problem-solving and decision-making by considering all relevant factors and their interactions. A holistic view facilitates a deeper understanding of how changes in one area may impact others, ultimately leading to more sustainable and effective change initiatives.

For example, An organisation is running several parallel initiatives under a broader digital transformation effort, including:

  1. CRM System Implementation
  2. Agile Ways of Working Initiative
  3. Cloud Migration for Core IT Systems
  4. Employee Upskilling Program on Digital Tools

Application of Holistic Perspective

  1. Identifying Interdependencies
    • The CRM system needs to integrate with both legacy IT infrastructure and future cloud platforms.
    • The agile transformation affects how teams work, influencing the success of the CRM project and cloud migration by demanding faster collaboration cycles.
    • The upskilling program needs to ensure employees are trained not only in new digital tools but also on agile practices and cloud-based platforms.
  2. Avoiding Initiative Silos
    • Without a holistic view, each project might focus only on its own goals, causing schedule conflicts (e.g., IT resources are overbooked for the cloud migration and CRM deployment).
    • Teams might experience change fatigue if initiatives are rolled out simultaneously without coordination. For example, employees may struggle to participate in the upskilling program while also meeting deadlines for the agile rollout.
  3. Portfolio-Level Governance and Prioritization
    • Using a holistic lens, the portfolio management team can sequence projects logically. For example:
      • First: Migrate critical systems to the cloud to ensure the CRM implementation has a stable foundation.
      • Second: Begin the agile transformation to align working methods before launching cross-functional CRM initiatives.
      • Third: Schedule employee upskilling to ensure readiness before key milestones in the CRM and cloud projects.
  4. Optimizing Resources and Reducing Risks
    • Viewing the portfolio holistically allows management to optimize resource allocation (e.g., sharing skilled IT personnel across cloud and CRM projects efficiently).
    • By aligning initiatives, the company mitigates the risk of conflicting efforts and reduces change fatigue through coordinated communication and engagement plans.

Principle 4: Emergence

Finally, the concept of emergence in systems thinking highlights how complex behaviours can arise from simple interactions among components. The principle of emergence in systems thinking refers to the idea that when individual elements interact, new patterns or behaviours emerge that were not predictable by examining the parts alone. In change portfolio management, this means that the outcomes of managing multiple change initiatives may be different—often more complex or unexpected—than the sum of each individual change project. Emergent behaviours can create both opportunities and risks.

Scenario: Managing a Sustainability Transformation Portfolio

A large organisation launches several interconnected initiatives to become a more sustainable enterprise:

  1. Carbon Reduction Initiative – Shift to renewable energy and reduce emissions.
  2. Sustainable Supply Chain Project – Engage suppliers on environmental standards.
  3. Green Product Innovation Program – Develop eco-friendly products.
  4. Employee Engagement Initiative – Promote green behaviours among employees.

Application of Emergence

  1. Unexpected Synergies Emerge
    • Employees participating in the engagement initiative start identifying operational inefficiencies, such as excess waste, leading to additional cost savings.
    • The green product innovation program creates a culture of experimentation that spills over into other departments, resulting in improved collaboration and faster innovation cycles across the organisation, beyond sustainability-focused efforts.
  2. Emergent Risks and Complex Interactions
    • Suppliers struggling to meet new sustainability requirements may delay the sustainable supply chain project, impacting both product launches and company operations.
    • Employees feel overwhelmed by the number of sustainability programs and resist further change, creating unexpected resistance that spreads to unrelated initiatives, such as digital transformation efforts.
  3. New Opportunities Emerge from Interactions
    • As cross-functional teams work together, new business models emerge. For example, sales and product teams discover that green products appeal to a new customer segment, leading to revenue growth opportunities not originally anticipated in the change portfolio plan.
    • Collaborations with suppliers in the supply chain project uncover the potential for joint ventures focused on sustainable technology.

It may not be possible to forecast or anticipate all types of employee behaviours and reactions to new changes introduced.  However, engaging your stakeholders and involving them in the change process may help you identify these in advance. 

The Role of Change Data in Building Systems-Thinking Within Change Portfolio Management

Change portfolio management involves overseeing a collection of change initiatives and ensuring that they align with the organisation’s strategic objectives. The integration of change data into this process can significantly enhance systems thinking capabilities.

Creating a Data-Driven Culture

One of the first steps in leveraging change data is to establish a data-driven culture. Practitioners should promote the importance of data in decision-making processes across the organisation. By providing visibility of the changes that are upcoming, they can empower employees at all levels to utilize change data in their daily work. This cultural shift fosters an environment where data becomes a common language, allowing for clearer communication about changes and their potential impacts.  However, do note that different type of employees may require different type of data.

Mapping Change Initiatives

Using change data, organisations can create visual maps of their change initiatives. These maps can illustrate how different initiatives are interconnected and highlight the dependencies between them. For example, a visual representation can show how a new software implementation relies on training programs or how changes in one department may impact others. By visualizing these relationships, practitioners can better assess the potential ripple effects of changes and make more informed decisions.

Monitoring and Analysing Feedback Loops

By actively monitoring change data, organisations can identify and analyse feedback loops in real-time. This ongoing analysis allows practitioners to quickly respond to emerging trends or unintended consequences. For instance, if data shows a decline in employee productivity following a process change, practitioners can investigate and implement corrective actions before the situation worsens. By understanding these feedback loops, organisations can not only react to changes but also proactively shape their outcomes.

Causal Analysis

Incorporating change data into causal analysis enables organisations to identify the root causes of issues. Practitioners can use data analytics to explore the relationships between different components of the organisation, leading to a clearer understanding of how changes impact various outcomes. This data-driven approach allows for more targeted interventions, ensuring that efforts are directed towards addressing the underlying issues rather than merely treating surface-level symptoms.

Holistic Change Portfolio Assessment

When practitioners evaluate their change portfolio, they should adopt a holistic approach that considers the interplay between various initiatives. By analysing change data in aggregate, organisations can identify patterns and trends that may not be visible when examining initiatives in isolation. This holistic assessment allows practitioners to prioritise initiatives that align with broader organisational goals, ultimately leading to more effective change management.

Fostering Collaborative Environments

Change data can also be a catalyst for fostering collaborative environments. By sharing insights and findings from change initiatives, organisations can create a culture of collaboration where teams learn from one another’s experiences. This exchange of information can lead to emergent solutions that drive innovation and improve change outcomes. Additionally, collaborative tools and platforms can be leveraged to facilitate communication and knowledge sharing across departments.

Building Connectedness Across the Organisation

The integration of change data into change portfolio management fosters interconnectedness within the organisation. By emphasising the importance of data and encouraging collaboration, practitioners can create a more cohesive organisational culture that embraces change.

Enhancing Communication

Clear communication is essential for effective change management. Change data provides a foundation for transparent communication about initiatives and their impacts. Practitioners can use data visualizations and reports to communicate progress, challenges, and successes, fostering a sense of shared understanding across the organisation.

Breaking Down Silos

Change data can also help break down silos within the organisation. By sharing data and insights across departments, practitioners can encourage collaboration and foster a sense of unity. This interconnectedness enhances problem-solving capabilities, as diverse teams bring different perspectives to the table, leading to more innovative solutions.  Issues may be pre-empted if stakeholders can pick up on impacts that may be missed for example.

Aligning Goals and Objectives

When change initiatives are informed by change data, it becomes easier to align goals and objectives across the organisation. Practitioners can use data to ensure that all initiatives are working towards the same strategic objectives, reducing the likelihood of conflicting priorities. This alignment creates a more focused approach to change management, ultimately leading to improved business results.

Improving Business Results Through Systems Thinking

The application of systems thinking through change data in change portfolio management can lead to substantial improvements in business results. By fostering interconnectedness, enhancing communication, and breaking down silos, organisations can create a more agile and responsive environment.

Increased Agility

Organisations that embrace systems thinking and utilize change data are better equipped to respond to changes in the external environment. By understanding the interconnectedness of their initiatives, practitioners can pivot quickly in response to emerging trends or challenges. This agility is essential in today’s fast-paced business landscape.

Enhanced Employee Engagement

When employees see their work as part of a larger, interconnected system, they are more likely to feel engaged and motivated. By involving employees in the change process and using data to demonstrate the impact of their contributions, organisations can foster a sense of ownership and commitment to change initiatives.

Improved Decision-Making

Systems thinking promotes better decision-making by encouraging practitioners to consider the broader context of their actions. When decisions are informed by change data, organisations can identify potential consequences and make choices that align with their strategic goals. This improved decision-making ultimately leads to more successful change outcomes.

Sustainable Change Initiatives

Finally, the application of systems thinking and change data can lead to more sustainable change initiatives. By focusing on root causes, leveraging feedback loops, and fostering collaboration, organisations can implement changes that are not only effective in the short term but also sustainable over time. This sustainability is crucial for long-term business success.

Change data is a powerful lever that change management practitioners can use to foster systems thinking within their organisations. By recognising the interconnectedness of change initiatives, understanding feedback loops, exploring causality, adopting a holistic perspective, and nurturing environments for emergence, organisations can improve their approach to change management. Through these efforts, practitioners can build connectedness across the organisation, ultimately enhancing how change is managed and driving improved business results. Embracing systems thinking in change portfolio management is not just a best practice; it’s a necessity for organisations seeking to thrive in an ever-evolving business landscape.

The One Under-Emphasized Skill for Successful Change Managers

The One Under-Emphasized Skill for Successful Change Managers

Change managers are not just facilitators of change transition; they are strategic partners who must understand and navigate complex organisational landscapes. One key skill that is often under-emphasised in this role is analytical capability. By adopting a strategic consultant’s mindset and employing robust analytical skills, change managers can significantly enhance their effectiveness throughout the project lifecycle. Let’s explore how change managers can leverage analytical skills at each phase of the project lifecycle, emphasising frameworks like MECE and TOSCA to drive successful change initiatives.

The Importance of an Analytical Lens

Change management involves facilitating transitions while ensuring that stakeholders are engaged and informed. However, to do this effectively, change managers must analyse complex data sets, identify patterns, and make informed decisions based on evidence. This analytical lens can be applied through every stage of the project lifecycle: commencement, planning, execution, monitoring, and closure.

Gone are the days when change practitioners are making recommendations ‘from experience’ or based on stakeholder input or feedback.  For complex transformation, stakeholders now (especially senior stakeholders) demand a more rigorous, data-driven approach to drive toward solid change outcomes.

1. Project Commencement Phase

At the project commencement phase, the groundwork is laid for the entire change initiative. Change managers need to scan the organizational environment through the lens of impacted stakeholders, gathering relevant information and data.

Example: Consider a company planning to implement a new customer relationship management (CRM) system. The change manager should begin by analysing the existing state of customer interactions, assessing how the change will impact various departments such as sales, marketing, and customer service. This involves conducting stakeholder interviews, reviewing existing performance metrics, and gathering feedback from employees.

Using a MECE (Mutually Exclusive, Collectively Exhaustive) framework, the change manager can categorize stakeholder concerns into distinct groups—such as operational efficiency, user experience, and integration with existing systems—ensuring that all relevant factors are considered. By identifying these categories, the change manager can articulate a clear vision and define the desired end state that resonates with all stakeholders.

The above is from Caseinterview.com

Hypothesis: Sales Team Will Resist the New CRM System Due to Lack of Training and User-Friendliness

Step 1: Identify the Hypothesis

Hypothesis: The sales team will resist the new CRM system because they believe it is not user-friendly and they fear insufficient training.

Step 2: Break Down the Hypothesis into MECE Categories

To validate this hypothesis, we’ll break it down into specific categories that are mutually exclusive and collectively exhaustive. We’ll analyse the reasons behind the resistance in detail.

Categories:

  1. User Experience Issues
    • Complexity of the Interface
    • Navigation Difficulties
    • Feature Overload
  2. Training and Support Concerns
    • Insufficient Training Programs
    • Lack of Resources for Ongoing Support
    • Variability in Learning Styles
  3. Change Management Resistance
    • Fear of Change in Workflow
    • Previous Negative Experiences with Technology
    • Concerns About Impact on Performance Metrics

Step 3: Gather Data for Each Category

Next, we need to collect data for each category to understand the underlying reasons and validate or refute our hypothesis.

Category 1: User Experience Issues

  • Data Collection:
    • Conduct usability testing sessions with sales team members.
    • Administer a survey focusing on user interface preferences and pain points.
  • Expected Findings:
    • High rates of confusion navigating the new interface.
    • Feedback indicating that certain features are not intuitive.

Category 2: Training and Support Concerns

  • Data Collection:
    • Survey the sales team about their current training needs and preferences.
    • Review existing training materials and resources provided.
  • Expected Findings:
    • Many team members express a need for more hands-on training sessions.
    • A lack of available resources for ongoing support after the initial rollout.

Category 3: Change Management Resistance

  • Data Collection:
    • Conduct focus groups to discuss fears and concerns regarding the new system.
    • Analyse historical data on previous technology implementations and employee feedback.
  • Expected Findings:
    • Employees voice concerns about how the CRM will change their current workflows.
    • Negative sentiments stemming from past technology rollouts that were poorly managed.

Step 4: Analyse Data Within Each Category

Now that we have gathered the data, let’s analyse the findings within each MECE category.

Analysis of Findings:

User Experience Issues:

  • Complexity of the Interface: Usability tests reveal that 70% of sales team members struggle to complete certain tasks in the CRM.
  • Navigation Difficulties: Survey responses show that 80% find one step of the navigation counterintuitive, leading to frustration.

Training and Support Concerns:

  • Insufficient Training Programs: Surveys indicate that only 40% of employees feel adequately trained to use this part of the new system.
  • Lack of Resources for Ongoing Support: Focus groups reveal that team members are unsure where to seek help after the initial training.

Change Management Resistance:

  • Fear of Change in Workflow: Focus group discussions highlight that 60% of participants fear their productivity will decrease with the new system, at least during the post Go Live period.
  • Previous Negative Experiences: Historical data shows that past technology rollouts had mediocre adoption rates due to insufficient support, reinforcing current fears.

Step 5: Develop Actionable Recommendations

Based on the analysis of each category, we can create targeted recommendations to address the concerns raised.

Recommendations:

User Experience Issues:

  • Conduct additional usability testing with iterative feedback loops to refine the CRM interface before full rollout.
  • Simplify the navigation structure based on user feedback, focusing on the most frequently used features.

Training and Support Concerns:

  • Develop a comprehensive training program that includes hands-on workshops, tutorials, and easy-to-access online resources.
  • Establish a dedicated support team to provide ongoing assistance, ensuring team members know whom to contact with questions.

Change Management Resistance:

  • Implement a change management strategy that includes regular communication about the benefits of the new system, addressing fears and expectations.
  • Share success stories from pilot programs or early adopters to demonstrate positive outcomes from using the CRM.

By following this detailed step-by-step analysis using the MECE framework, the change manager can thoroughly investigate the hypothesis regarding the sales team’s resistance to the new CRM system. This structured approach ensures that all relevant factors are considered, enabling the development of targeted strategies that address the specific concerns of stakeholders. Ultimately, this increases the likelihood of successful change adoption and enhances overall organizational effectiveness.

Data-Driven Decision Making:

At this stage, change managers should work closely with the project sponsor and project manager to determine effective positioning. A data-driven approach allows the change manager to form a hypothesis about how the change will impact stakeholders. For instance, if data suggests that the sales team is particularly resistant to change, the manager might hypothesize that this resistance stems from a lack of understanding about how the new CRM will enhance their workflow.

2. Planning Phase

Once the project is initiated, the planning phase requires detailed strategy development. Here, analytical skills are essential for conducting stakeholder analysis and impact assessments.

Example: In our CRM implementation scenario, the change manager must analyse the data collected during the commencement phase to identify the specific impacts on different departments. This involves grouping and sorting the data to prioritize which departments require more extensive support during the transition.

Using the TOSCA (Target, Objectives, Strategy, Constraints, Actions) framework provides a structured approach to guide the change management process for the CRM implementation. This framework helps clarify the overall vision and specific steps needed to achieve successful adoption. Below is a detailed exploration of each component:

1. Target

Definition: The target is the overarching goal of the change initiative, articulating the desired end state that the organization aims to achieve.

Application in CRM Implementation:

  • Target: Improve customer satisfaction and sales efficiency.

This target encapsulates the broader vision for the CRM system. By focusing on enhancing customer satisfaction, the organization aims to create better experiences for clients, which is crucial for retention and loyalty. Improving sales efficiency implies streamlining processes that enable sales teams to work more effectively, allowing them to close deals faster and serve customers better.

2. Objectives

Definition: Objectives are specific, measurable outcomes that the organization intends to achieve within a defined timeframe.

Application in CRM Implementation:

  • Objectives: Increase customer retention by 20% within a year.

This objective provides a clear metric for success, enabling the organization to track progress over time. By setting a 20% increase in customer retention as a target, the change manager can align training, support, engagement and system adoption with this goal. This objective also allows for measurable evaluation of the CRM’s impact on customer relationships and retention efforts.

3. Strategy

Definition: The strategy outlines the high-level approach the organization will take to achieve the objectives. It serves as a roadmap for implementation.

Application in CRM Implementation:

  • Strategy: Implement phased training sessions for each department, with tailored support based on the unique impacts identified.

This strategy emphasizes a thoughtful and structured approach to training, recognizing that different departments may face distinct challenges and needs when adapting to the new CRM. By rolling out training in phases, the organization can focus on one department at a time, ensuring that each team receives the specific support they require. Tailoring the training content based on the unique impacts identified earlier in the MECE analysis helps maximize engagement and effectiveness, addressing concerns about usability and fostering greater adoption of the CRM.

4. Constraints

Definition: Constraints are the limitations or challenges that may impact the successful implementation of the strategy. Recognizing these upfront allows for better planning and risk management.

Application in CRM Implementation:

  • Constraints: Limited budget and time restrictions.

Acknowledging these constraints is critical for the change manager. A limited budget may affect the types of training resources that can be utilized, such as hiring external trainers or investing in advanced learning technologies. Time restrictions might necessitate a more rapid rollout of the CRM system, which could impact the depth of training provided. By recognizing these constraints, the change manager can plan more effectively and prioritize key areas that will deliver the most value within the available resources.

5. Actions

Definition: Actions are the specific steps that will be taken to implement the strategy and achieve the objectives.

Application in CRM Implementation:

  • Actions: Develop a communication plan that includes regular updates and feedback mechanisms.

This action focuses on the importance of communication throughout the change process. A well-structured communication plan ensures that all stakeholders, particularly the sales team, are kept informed about the implementation timeline, training opportunities, and how their feedback will be incorporated into the process. Regular updates foster transparency and help build trust, while feedback mechanisms (such as surveys or suggestion boxes) allow team members to voice concerns and share their experiences. This two-way communication is essential for addressing issues promptly and reinforcing a culture of collaboration and continuous improvement.

By applying these frameworks, change managers can make informed recommendations that align with organizational objectives. This structured approach helps ensure that all relevant factors are accounted for and that stakeholders feel included in the planning process.

 

3. Execution Phase

As the project moves into the execution phase, the change manager must remain agile, continually collecting organizational data to confirm or reject the hypotheses formed during the planning stage.

Example: In an agile setting, where iterative processes are key, the change manager should implement mechanisms for ongoing feedback. For instance, after each sprint of CRM implementation, the manager can gather data from users to assess how well the system is being received. Surveys, usage analytics, and focus groups can provide rich insights into user experiences and pain points.

This ongoing data collection allows change managers to adjust their strategies in real-time. If feedback indicates that certain features of the CRM are causing confusion, the change manager can pivot to provide additional training or resources targeted specifically at those areas. This iterative feedback loop is akin to the work of strategic consultants, who continuously assess and refine their approaches based on empirical evidence.

Example in Practice: Imagine a situation where the sales team reports difficulties with the new CRM interface, leading to decreased productivity. The change manager can analyse usage data and user feedback to pinpoint specific issues. This data-driven insight can guide the development of targeted training sessions focusing on the problematic features, thus addressing concerns proactively and fostering user adoption.

 

4. Monitoring Phase

Monitoring the change initiative is crucial for ensuring long-term success. Change managers need to analyse performance metrics to evaluate the effectiveness of the implementation and its impact on the organization.

Example: For the CRM project, key performance indicators (KPIs) such as sales conversion rates, customer satisfaction scores, and employee engagement levels should be monitored. By employing data visualization tools, change managers can easily communicate these metrics to stakeholders, making it clear how the change initiative is progressing.

A fact-based approach to analysing these metrics helps in making informed decisions about any necessary adjustments. If, for instance, customer satisfaction scores are declining despite an increase in sales, the change manager may need to investigate further. This might involve conducting interviews with customers or analysing customer feedback to identify specific areas for improvement.

Suppose the organization observes a drop in customer satisfaction scores following the CRM implementation. The change manager could work with other stakeholders to conduct a root cause analysis using customer feedback and service interaction data to identify patterns, such as longer response times or unresolved issues. By addressing these specific problems, the change manager can refine the CRM processes and enhance overall service quality.

 5. Closure Phase

The closure phase involves reflecting on the outcomes of the change initiative and drawing lessons for future projects. This is where the analytical skills of change managers can shine in assessing the overall impact of the change.

Example: After the CRM system has been fully implemented, the change manager should conduct a comprehensive review of the project along with the project team (retro). This involves analysing both qualitative and quantitative data to evaluate whether the initial objectives were met. Surveys can be distributed to employees to gather feedback on their experiences, while sales data can be analysed to determine the financial impact of the new system.

Using frameworks like MECE can help in categorizing the lessons learned. For instance, feedback could be sorted into categories such as user experience, operational efficiency, and overall satisfaction, allowing the change manager to develop clear recommendations for future initiatives.

Lessons Learned: If the analysis shows that certain departments adapted more successfully than others, the change manager could investigate the factors contributing to this variance. For example, departments that received more personalized support and training may have demonstrated higher adoption rates. This insight can inform strategies for future change initiatives, emphasizing the importance of tailored support based on departmental needs.

 

Building Relationships with Senior Leaders

In addition to the technical aspects of change management, the ability to communicate effectively with senior leaders is crucial. Seasoned change managers must clearly understand organizational objectives and be able to articulate how the change initiative contributes to these goals.

Example: During discussions with senior leadership, a change manager along with the rest of the project team can present data showing how the CRM system has improved customer retention rates and increased sales. By positioning this information in an easily understandable and rigorous manner, the change manager demonstrates the value of the initiative and its alignment with broader organizational objectives.

Effective communication ensures that leaders remain engaged and supportive throughout the change process, increasing the likelihood of success. By continuously linking the change initiative to organizational goals, change managers can build trust and credibility with stakeholders at all levels.

Leveraging Analytical Frameworks

Throughout the project lifecycle, incorporating structured analytical frameworks can enhance the decision-making process. Here are two key frameworks that change managers can leverage:

MECE Framework

MECE (Mutually Exclusive, Collectively Exhaustive) helps in breaking down complex information into manageable parts without overlap. By ensuring that all categories are covered without redundancy, change managers can identify all relevant factors affecting the change initiative.

TOSCA Framework

TOSCA (Target, Objectives, Strategy, Constraints, Actions) provides a comprehensive roadmap for change initiatives. By clearly defining each component, change managers can develop coherent strategies that align with organizational goals.  This framework not only clarifies the change strategy but also ensures that all team members understand their roles in achieving the objectives.

Continuous Learning and Adaptation

Change management is not a static process; it requires continuous learning and adaptation. As organizations evolve, change managers must stay attuned to emerging trends and best practices in the field. This involves seeking feedback, conducting post-project evaluations, and staying updated on analytical tools and methodologies.

Change managers can attend workshops, participate in industry conferences, and engage with professional networks to enhance their analytical skills and learn from peers. By sharing experiences and insights, change managers can refine their approaches and incorporate new strategies that drive successful change.

The Transformative Power of Analytical Skills

The role of a change manager is multifaceted and requires a broad range of skills. However, one skill that stands out as particularly critical is the ability to think analytically. By adopting a strategic consultant’s mindset and applying analytical skills at each phase of the project lifecycle, change managers can significantly enhance their effectiveness.

From project commencement to closure, employing frameworks like MECE and TOSCA allows change managers to approach challenges in a structured way, making informed decisions that drive successful change. Continuous data collection, stakeholder engagement, and effective communication with senior leaders are essential components of this analytical approach.

In an era where organizations must adapt quickly to change, the ability to analyse complex data sets and derive actionable insights will distinguish successful change managers from the rest. Emphasizing this critical skill not only positions change managers as strategic partners within their organizations but also ensures that change initiatives lead to lasting, positive transformations.

As change practitioners, let us elevate our analytical capabilities and drive impactful change with confidence and clarity. By embracing this essential skill, we can navigate the complexities of organizational change and lead our teams toward a successful future.

How to measure change adoption

How to measure change adoption

Measuring change adoption is one of the most important parts of the work of change practitioners.  It is the ultimate ‘proof’ of whether the change interventions have been successful or not in achieving the initiative objectives.  It is also an important way in which the progress of change management can clearly be shown to the project team as well as to various stakeholder groups. The ability to show clearly the progress of change outcome is critical to focus your stakeholders’ actions on the right areas. It is one of the key ways to ‘prove your worth’ as a change practitioner.

Measurement takes time, focus and effort.  It may not be something that is a quick exercise.  There needs to be precise data measurement design, a reliable way of collecting data, and data visualisation that is easily understood by stakeholders.

With the right measurements of change adoption, you can influence the direction of the initiative, create impetus amongst senior stakeholders, and steer the organisation toward a common goal to realise the change objectives.  Such is the power of measuring change adoption.

The myth of the change management curve

One of the most popular graphs in change management and often referred as the ‘change curve’ is the Kubler-Ross model.  The model was specifically designed by psychiatrist Elisabeth Kubler-Ross to refer to terminally ill patients as a part of the book ‘On Death and Dying’.  For whatever reason, it has somehow gained popularity and application in change management. Therefore, be very careful when using applying this model in a change context.

There is little research evidence to back this up even in psychological research.  When applied in change management there is no known research that supports this at all. So be careful when you come across models such as this one that is simple and seem intuitively ‘correct’.  On the other hand, there is ample research by McKinsey that for effectively managed initiatives and transformations, stakeholders do not go through this ‘valley of death’ journey at all.

Diagram by chaucer.com

The ‘S’ curve of change adoption

If the ‘change curve’ is not the correct chart to follow with regard to change adoption, then what is the right one to refer to? Good question.

The ‘S’ curve of change adoption is one that can be referenced.  It is well backed in terms of research from technology and new product adoption.  It begins with a typically slow start followed by a significant climb in adoption followed by a flattened level at the end. Most users typically do not uptake the change until later on.  

Here is an example of key technologies and the speed of adoption in U.S. households since the 1900s.

Source: HBR.org

With the different types of change contexts, the shape of the S curve will be expected to differ as a result.  For example, you are working on a fairly minor process change where there is not a big leap in going from the current process to the new process.  In this case, the curve would be expected to be a lot more gentle since the complexity of the change is significantly less than adopting a complex, new technology.

On the other hand, if you are working on many iterative agile changes, each iteration that impacts users may be a small S curve in themselves. Ideally, each iteration work together towards a greater piece of overarching change.

Going beyond what is typically measured

Most change practitioners are focused on measuring the easier and more obvious measures such as stakeholder perceptions, change readiness, and training completion.  Whilst these are of value, they in themselves are only measuring certain aspects of the change.  They can be viewed as forward-looking indications of the progress that supports moving toward eventual change adoption, versus the eventual change adoption.

Also, be aware of ‘vanity metrics’. These are metrics that do not connect to business outcomes, though they may ‘look good’ and easy to understand. To read more about vanity metrics check out this article.

To really address head-on the topic of measuring adoption, it is critical to go beyond these initial measures toward those elements that indicate the actual change in the organisation.  Depending on the type of change this could be system usage, behaviour change, following a new process or achieving cost savings targets.

Project Benefit realization

It goes without saying that to really measure change adoption the change practitioner must work closely with the project manager to understand in detail the benefits targeted, and how the prescribed benefits will be measured.  The project manager could utilise a range of ways to articulate the benefits of the project.  Common benefit categories include:

  • Business success factors such as financial targets on revenue or cost
  • Product integration measures such as usage rate
  • Market objectives such as revenue target, user base, etc.

These categories above are objectives that are easier to measure and tangible to quantify.  However, there could also be less tangible targets such as:

  • Competitive positioning
  • Employee relations
  • Employee experience
  • Product or solution leadership
  • Employee capability
  • Customer experience

There could be various economic methods of determining the targeted benefit objectives.  These include payback time or the length of time from project initiation until the cumulative cash flow becomes positive, or net present value, or internal rate of return.

The critical aspect for change practitioners is to understand what the benefit objectives are, how benefit tracking will be measured and to interpret what steps are required to get there.  These steps include any change management steps required to get from the current state to the future state.

Here is an example of a mapping of change management steps required in different benefit targets:

Project benefits targetedLikely change management steps requiredChange management measures
Increased customer satisfaction and improved productivity through implementing a new system.Users able to operate the new system.
Users able to improve customer conversations leveraging new system features.
Users proactively use the new system features to drive improved customer conversations.
Managers coaching and provide feedback to usersBenefit tracking and communications.
Customer communication about improved system and processes
Decreased customer call waiting time .
% of users passed training test.
System feature usage rate.
Customer issue resolution time.
User feedback on manager coaching.
Monthly benefit tracking shared and discussed in team meetings.
Customer satisfaction rate. Customer call volume handling capacity.

Measuring behavioural change

For most change initiatives, there is an element of behaviour change, especially for more complex changes.  Whether the change involves a system implementation, changing a process or launching a new product, behaviour change is involved.  In a system implementation context, the behaviour may be different ways of operating the system in performing their roles.  For a process change, there may be different operating steps which need to take place that defers from the previous steps.  The focus on behaviour change aims to zoom in on core behaviours that need to change to lead to the initiative outcome being achieved.

How do we identify these behaviours in a meaningful way so that they can be identified, described, modelled, and measured?

The following are tips for identifying the right behaviours to measure:

  • Behaviours should be observable.  They are not thoughts or attitudes, so behaviours need to be observable by others
  • Aim to target the right level of behaviour.  Behaviours should not be so minute that they are too tedious to measure, e.g. click a button in a system.  They also should not be so broad that it is hard to measure them overall, e.g. proactively understand customer concerns vs. what is more tangible such as asked questions about customer needs in XXX areas during customer interactions.
  • Behaviours are usually exhibited after some kind of ‘trigger’, for example, when the customer agent hear certain words such as ‘not happy’ or ‘would like to report’ from the customer that they may need to treat this as a customer complaint by following the new customer complaint process.  Identifying these triggers will help you measure those behaviours.
  • Achieve a balance by not measuring too many behaviours since this will create additional work for the project team.  However, ensure a sufficient number of behaviours are measured to assess benefit realisation

Measuring micro-behaviours

Behaviour change can seem over-encompassing and elusive.  However, it may not need to be this.  Rather than focusing on a wide set of behaviours that may take a significant period of time to sift, focusing on ‘micro-behaviours’ can be more practical and measurable.  Micro-behaviours are simply small observable behaviours that are small step-stone behaviours vs a cluster of behaviours.

For example, a typical behaviour change for customer service reps may be to improve customer experience or to establish customer rapport.  However, breaking these broad behaviours down into small specific behaviours may be much easier to target and achieve results.

For example, micro-behaviours to improve customer rapport may include:

  • User the customer’s name, “Is it OK if I call you Michelle?”
  • Build initial rapport, “How has your day been?”
  • Reflect on the customer’s feeling, “I’m hearing that it must have been frustrating”
  • Agree on next steps, “would it help if I escalate this issue for you?”

Each of these micro-behaviours may be measured using call-listening ratings and may either be a yes/no or a rating based assessment.

To read more about measuring and driving behaviour change, check out our Ultimate Guide to Behaviour Change.

Establishing reporting process and routines

After having designed the right measurement to measure your change adoption, the next step would be to design the right reporting process.  Key considerations in planning and executing on the reporting process includes:

  • Ease of reporting, you should aim to automate where possible to reduce the overhead burden and manual work involved.  Whenever feasible leverage automation tools to move fast and not be bogged down by tedious work
  • Build expectations on contribution to measurement.  Rally your stakeholder support so that it is clear the data contribution required to measure and track change adoption
  • Design eye-catching and easy to understand dashboard of change adoption metrics.  
  • Design reinforcing mechanisms.  If your measurement requires people’s input, ensure you design the right reinforcing mechanisms to ensure you get the data you are seeking for.  Human nature is so that whenever possible, people would err on the side of not contributing to a survey unless there are explicit consequences of not filling out the survey. 
  • Recipients of change adoption measurement.  Think about the distribution list of those who should receive the measurement tracking.  This includes not just those who are in charge of realising the benefits (i.e. business leaders), but also those who contribute to the adoption process, e.g. middle or first-line managers.  

Example of change adoption dashboard from Change Automator

Measuring Adoption Across Initiatives

You may be driving multiple initiatives as a part of a large program or a portfolio of initiatives. The key challenge here is to establish common adoption measures that are apple-to-apple metrics comparisons across initiatives. Yes, each initiatives will most likely have different sets of what constitutes adoption. However, there are still common ways to report on adoption across initiatives such as overall percentage of adoption of identified adoption elements, or percentage of the number of milestones reached. You can also utilise manager reports of behaviours adopted, as well as system records of utilisation of certain features for example.

Check out examples of change management adoption metrics here.

Check out our Comprehensive Guide to Change Adoption Metrics here.

To read more about change analytics and measurement visit our Knowledge Centre.

Understanding change adoption is not only helpful to understand what works for one initiative, it can also be a linchpin to help you scale change adoption across change initiatives across your whole portfolio. Talk to us to find out more about how The Change Compass can help you understand what change interventions leads to higher change adoption rates, through data. Using a data-led approach in deciphering what drives change adoption can truly drive successful change outcomes.

Feeling a bit lost and would like to have a chat about how to measure adoption by utilising digital solutions? Contact us here.

The Danger of Using Go Lives to Report on Change Management Impacts

The Danger of Using Go Lives to Report on Change Management Impacts

In the world of change management, Go Lives are often seen as significant milestones. For many project teams, these events represent the culmination of months or even years of hard work, signaling that a new system, process, or initiative is officially being launched. It’s common for stakeholders to view Go Lives as a key indicator of the success of a change initiative. However, while Go Lives are undeniably important, relying on them as the primary measure of change impact can be misleading and potentially harmful to the overall change effort.

Go Lives are just one piece of the puzzle. Focusing too heavily on these milestones can lead to an incomplete understanding of the change process, neglecting crucial activities that occur both before and after Go Live. Let’s outline the risks associated with using Go Lives to report on change management impacts and offers best practices for a more holistic approach.

Go Lives: A Double-Edged Sword

Go Lives are naturally a focal point for project teams. They represent a clear, tangible goal, and the success of a Go Live can boost morale, validate the efforts of the team, and provide a sense of accomplishment. From a project delivery perspective, Go Lives are critical. They signal that the project has reached a level of maturity where it is ready to be released to the broader organization. In terms of resourcing and business readiness, Go Lives ensure that everything is in place for the new system or process to function as intended.

However, the very attributes that make Go Lives attractive can also make them problematic as indicators of change impact. The simplicity and clarity of a Go Live event can lead stakeholders to overestimate its significance, from a impacted business perspective. The focus on Go Lives can overshadow the complex and often subtle changes that occur before and after the event. While a successful Go Live is necessary for change, it is not sufficient to guarantee that the change will be successful in the long term.

The Pre-Go Live Journey: Laying the Foundation for Change

A significant portion of the change management journey occurs long before the Go Live date. During this pre-Go Live phase, various engagement and readiness activities take place that are critical to shaping the overall impact of the change. These activities include town hall meetings, where leaders communicate the vision and rationale behind the change, and briefing sessions that provide detailed information about what the change will entail.

Training and learning sessions are also a crucial component of the pre-Go Live phase. These sessions help employees acquire the necessary skills and knowledge to adapt to the new system or process. Discussions, feedback loops, and iterative improvements based on stakeholder input further refine the change initiative, ensuring it is better aligned with the needs of the organization.

These pre-Go Live activities are where much of the groundwork for successful change is laid. They build awareness, generate buy-in, and prepare employees for what is to come. Without these efforts, the Go Live event would likely be met with confusion, resistance, or outright failure. Therefore, it is essential to recognize that the impact of change is already being felt during this phase, even if it is not yet fully visible.

Post-Go Live Reality: The Real Work Begins

While the Go Live event marks a significant milestone, it is by no means the end of the change journey. In fact, for many employees, Go Live is just the beginning. It is in the post-Go Live phase that the true impact of the change becomes apparent. This is when employees start using the new system or process in their daily work, and the real test of the change’s effectiveness begins.

During this phase, the focus shifts from preparation to adoption. Employees must not only apply what they have learned but also adapt to any unforeseen challenges that arise. This period can be fraught with difficulties, as initial enthusiasm can give way to frustration if the change does not meet expectations or if adequate support is not provided.

Moreover, the post-Go Live phase is when the long-term sustainability of the change is determined. Continuous reinforcement, feedback, and support are needed to ensure that the change sticks and becomes embedded in the organization’s culture. Without these ongoing efforts, the change initiative may falter, even if the Go Live event was deemed a success.

The Risk of Misleading Stakeholders

One of the most significant dangers of focusing too heavily on Go Lives is the risk of misleading stakeholders. When stakeholders are led to believe that the Go Live event is the primary indicator of change impact, they may not fully appreciate the importance of the activities that occur before and after this milestone. This narrow focus can lead to a number of issues.

Firstly, stakeholders may prioritize the Go Live date to the exclusion of other critical activities. This can result in insufficient attention being paid to pre-Go Live engagement and readiness efforts or to post-Go Live adoption and support. As a consequence, the overall change initiative may suffer, as the necessary foundations for successful change have not been properly established.

Secondly, stakeholders may develop unrealistic expectations about the impact of the change. If they believe that the Go Live event will immediately deliver all the promised benefits, they may be disappointed when these benefits take longer to materialize. This can erode confidence in the change initiative and reduce support for future changes.

Finally, a narrow focus on Go Lives can create a false sense of security. If the Go Live event is successful, stakeholders may assume that the change is fully implemented and no further action is required. This can lead to complacency and a lack of ongoing support, which are essential for ensuring the long-term success of the change.

Best Practices for Reporting Change Management Impact

To avoid the pitfalls associated with relying on Go Lives as indicators of change impact, change management practitioners should adopt a more holistic approach to reporting. This involves considering the full scope of the change journey, from the earliest engagement activities to the ongoing support provided after Go Live. Here are some best practices for reporting on change management impact:

  1. Integrate Pre-Go Live Metrics:
    • Track and report on engagement activities, such as attendance at town hall meetings, participation in training sessions, and feedback from employees.
    • Monitor changes in employee sentiment and readiness levels throughout the pre-Go Live phase.
    • Report on aggregate pan-initiative change initiative impost on business units, pre-Go Live
  2. Emphasize Post-Go Live Support:
    • Develop metrics to measure the effectiveness of post-Go Live support, such as the number of help desk inquiries, employee satisfaction with the new system, and the rate of adoption.
    • Highlight the importance of continuous feedback loops to identify and address any issues that arise after Go Live.
    • Communicate the need for ongoing reinforcement and support to stakeholders, emphasizing that change is an ongoing process
    • Report on post-Go Live adoption time impost expected across initiatives
  3. Provide a Balanced View of Change Impact:
    • Ensure that stakeholders understand that Go Live is just one part of the change journey and that significant impacts occur both before and after this event.
    • Use a combination of quantitative and qualitative data to provide a comprehensive view of change impact.
    • Regularly update stakeholders on progress throughout the entire change journey, not just at the time of Go Live.
  4. Manage Expectations:
    • Clearly communicate to stakeholders that the full impact of the change may not be immediately visible at the time of Go Live.
    • Set realistic expectations about the timeline for realizing the benefits of the change.
    • Prepare stakeholders for potential challenges in the post-Go Live phase and emphasize the importance of ongoing support.

While Go Lives are important milestones in the change management process, they should not be used as the sole indicator of change impact. The journey to successful change is complex, involving critical activities before, during, and after the Go Live event. By adopting a more holistic approach to reporting on change management impact, practitioners can provide stakeholders with a more accurate understanding of the change journey, manage expectations more effectively, and ensure the long-term success of the change initiative.

The key takeaway is that change management is not just about delivering a project; it’s about guiding an organization through a journey of transformation. Go Lives are just one step in this journey, and it is the responsibility of leaders to ensure that every step is given the attention it deserves.

The ultimate guide to measuring change

The ultimate guide to measuring change

Updated 26 January 2025

 

A lot of change practitioners are extremely comfortable with saying that change management is about attitudes, behaviours, and feelings and therefore we cannot measure them.  After all, a big chunk of change folks are more interested in people than numbers. This metaphor that change management is ‘soft’ extends into areas such as leadership and employee engagement whereby it may not be easy to measure and track things. However, is it really that because something is harder to measure and less black and white that there is less merit in measuring these?

“If you can’t measure it you can’t improve it” Peter Drucker”

In today’s fast-paced business environment, measuring change is no longer about static reports or manual tracking. With advancements in AI and automation, organisations can now leverage real-time data analytics, predictive tools, and automated insights to manage change effectively. This guide explores how these technologies are reshaping the way we measure and manage change.

The ‘why’ behind a lot of industry changes in our day and age come from the fact that data is now dominating our world. Data is a central part of everything that is changing in our world. Since we are now more reliant on the internet for information, the data that can be collected through our digital interactions around our lives are now driving change.

Data and measurement is all around us.  In fact our world would not exist without them.  Without data and measurement our phones would not work, our home security features would not work, TV stations would not function, the internet would not be on, lifts would not work and even traffic lights would not work.

At the workplace, most corporate work functions and departments rely on data to run and manage the business.  HR, Finance, Operations, Manufacturing, Risk, Procurement, IT, etc.  The list goes on.  In each of these departments data is an essential part of the day to day running of the function, without which the function cannot be run effectively.  They would not know if the performance is hitting targets.

Now with AI, companies are focused on data at an even greater level more than ever.  Without data, AI cannot work nor add value to organisations.  The backbone of AI is the ability to access vast amounts of data so that this can be used to automate and help us with our lives.

So if our world is surrounded by data, why are we not measuring it in managing change? To answer this question let’s look at what we are or are not measuring.

 

 

 

 

Starting at a project level, these are some of the common ways in which change is often measured:

 

1. Change readiness surveys

Change readiness surveys are usually online surveys sent by a project owner to understand how stakeholder groups are feeling about the change at different points in time throughout the project. It can be in the form of a Likert scale or free text. Most results are summarized into a quantitative scale of the degree in which the group is ready for change. A simple SurveyMonkey or Microsoft Form could be set up to measure stakeholder readiness for change.

It used to be that change readiness surveys were quite long and wordy.  Nowadays, a lot of change practitioners prefer to have shorter ‘pulse’ surveys as a way to regularly check on the stakeholder sentiments for readiness.  However, shorter surveys could mean a lack of depth in the feedback you are receiving and limited data to use to pivot as necessary to address any concerns. So, you may find out if your stakeholders are ready for change, but not why.  Ensure you balance ease and speed with insight and outcome.

The purpose of using change readiness surveys is to assess the stakeholders’ readiness for change.  The results from the survey will definitely inform the levels of readiness.  However, the survey itself may not be sufficient to conduct the assessment.  Simply asking what stakeholders feel may not be a holistic way of assessing their readiness.  To read more about conducting change readiness assessment strategically check out our article Beyond the Survey: A Strategic Lens on Change Readiness Assessment.

 

2. Training evaluation surveys

These evaluations are normally based on participant satisfaction across various categories such as content, instructor effectiveness, usefulness, etc. In a face-to-face training format, these surveys are normally paper-based so as to increase the completion rate. For online or virtual training, ratings may be completed by the user at the conclusion or after the session.

Considering that most organisations use virtual training formats, it is good practice to incorporate training evaluation at the conclusion of the session before the participants leave (after which it is almost impossible to get the satisfactory level of participant responses).

With the range of digital/AI-enabled tools on offer now, you can design training sessions in a way that requires much less and effort and gives you better results (to read more check out this link from Forbes).  Some of these features include:

– gamifying training content to make it more engaging, interesting and fun

– easily creating micro-courses with little instructional design expertise

– incorporate a range of media such as videos and pictures with little effort

– using avatars as instructors to host the content

– easily create quizzes and assessments (check out Change Automator feature to conduct assessments)

 

3. Communications metrics

One way in which communications may be measured is the ‘hit rate’ or the number of users/audience that views the article/material/page. This may be easily tracked using Google Analytics which not only tracks the number of views per page but also viewership by the time of day/week as well as audience demographic information as such gender and geographical locations.

There is also a range of digital tools on offer to track the effectiveness of communication efforts.  With Microsoft applications such as Yammer and Teams, there is already rich analytics capabilities on offer.  These include user/group activity, device type usage, etc.  Speak to your IT counterpart to access Microsoft Viva Engage which help you measure your community’s reach and engagement. You can find out more about the people, conversations, and questions & answers that make up your targeted communities.

There are also ways to A/B Test your communications message, whereby you have 2 different messages and test this with a smaller group fo audience to see which ones resonate or lead to more action.  You can also create 2 different versions of the same intranet page and test messaging this way.  When you have concluded the test you can then select the ‘winning’ version to the broader set of audience.  Speak to your corporate communications colleague to get their help to implement this.

 

4. Employee sentiments/culture surveys

There are some organizations that measure employee sentiments or culture over the year and often there are questions that are linked to change. These surveys tend to be short and based on a Likert scale with fewer open-ended questions for qualitative feedback. Since these surveys are often sent across the entire organization they are a ‘catch-all’ yardstick and may not be specific to particular initiatives.

There is now a range of AI tools to do text and sentiment analysis if your survey contains text items.  AI-powered tools now enable organisations to measure change through advanced metrics such as predictive capacity analysis to forecast resource strain, sentiment analysis to gauge stakeholder emotions in real time, and automated risk assessments that identify potential bottlenecks before they occur  All the major technology providers such as Microsoft, Amazon and IBM already provide these tools (some are even free).

These are some of the ways you can use AI tools right now:

– detect a range of emotions such as anxiety, anger, and disgust and based on response statistics through sentiment analysis

– cluster topics based on key response themes

– identify any data anomalies that you may want to exclude

– identify and label tone of voice of the responses, and classification such as positive, neutral, negative

– analyse trends over time

Data analysis and reporting can also be easily leveraged with the range of digital tools on offer.  Data analysis tools using AI can automated generate charts and dashboards for you with little effort.  Change Automator contains rich survey features that do exactly this, including:

– Easily selecting chart type with one click

– Leverage from AI-suggested data insights

– Generate predictive trends based on existing data

– Easily share charts and dashboards using different ways, including using a URL link

 

5. Change heatmaps

Some organizations devise change heatmaps on excel spreadsheets to try and map out the extent to which different business units are impacted by change. This artifact speaks to the amount of change and often leads to discussions concerning the capacity that the business has to ‘handle/digest’ change. The problem with most heatmaps is that they are usually categorised and rated by the creator of the artifact (or a limited number of people making judgments), and therefore subject to bias. Data that is based on 1 person’s opinions also tend not to have as much weight in a decision-making forum.

In fact, we highly recommend that you don’t use change heat maps as the only way to track change volume.  Instead, there is a range of other visuals such as bar charts, and timeline charts that are just as easy to interpret and are more insightful from a decision-making perspective.

Heatmaps are also by design categorical and not particularly precise.  It may be useful at a high level for understanding hot spots, but not one to use to make specific decisions concerning business capacity levels and corresponding challenges.

The following is an example of a Change heatmap that uses the standard red, amber green traffic light coding scheme.  This may play into the psychological bias of your audience interpreting red as bad and only focus on ‘alleviating’ the red.

 

6. Change initiative benefit tracking

In addition to typical change management measures, there are various initiatives-specific measures that focus on the actual outcome and benefit of the change with the goal of determining to what extent the change has taken place. Some examples of this include:

  • System usage rates

  • Cost reduction

  • Revenue increase

  • Transaction speed

  • Process efficiency

  • Speed of decision-making

  • Customer satisfaction rate

  • Employee productivity rate

  • Incidents of process violation

Non-initiative based change management measures

There are two other measures that are used within an organizational vs. initiative-specific context, change leadership assessment and change maturity assessment. In the next section, we will discuss these two areas.

 

Change leadership assessment

David Miller from Changefirst wrote about 3 types of change leaders.:

1. The sponsor whose role is to drive the initiative to success from the beginning to the end. This involves possessing competencies in rallying and motivating people, building a strong network of sponsors, and communicating clearly to various stakeholder groups.

 

2. The influencer whose role is to leverage their network and influence to market and garner the traction required to make the initiative successful. Four types of influencers as identified by Changefirst includes:

a) Advocates who are great at promoting and advocating the benefits of the change

b) Connectors who are able to link and leverage people across a part of the organization to support the change

c) Controllers who have control over access to information and people and these could include administrators and operations staff

d) Experts who are viewed by others in the organization as being technically credible

 

3. The change agent is someone who is tasked with supporting the overall change in various ways, including any promotional activities, gaging different parts of the organization on the change and be able to influence, up, down and sideways across the organization to drive a successful change outcome.  Some call this the ‘change champion’.  They can be your key to influencing across the organisation.

Whilst there isn’t one industry standard tool for assessing change leadership competencies and capabilities. There are various change leadership assessment tools offered by Changefirst as well as other various smaller consulting firms. Some of the ways in which you can assess change leadership may include categories such as Goal Attainment, Flexibility, Decision Making, and Relationship Building.

Some of the key competencies critical in change leadership have been called out by Pagon & Banutal (2008), and include:

  • Goal attainment

  • Assessing organizational culture and climate

  • Change implementation

  • Motivating and influencing others

  • Adaptability

  • Stakeholder management

  • Collaboration

  • Build organizational capacity and capability for change

  • Maneuvering around organizational politics

There is a range of change leadership assessment offerings from various consulting firms.  Whichever one you choose, ensure that it is not overly simplistic and not ‘tested’ and therefore not reliable.  Assessments will only be useful if they have gone through the rigour of being tested, with the results showing that they are reliable can be trusted.  Anyone can ‘invent’ a simple survey with various leadership categories, but this does not mean they are actually valid.  Afterall, if you are asking your leaders to spend time to fill in an assessment survey, you want to be confident that the outcome of the assessment will provide sufficient insight.

Change maturity assessment

Organisations are increasingly realising that managing change initiative by initiative is no longer going to cut it as it does not enable organizational learning and growth. Initiatives come and go and those who rely on contractor change managers often find that their ability to manage change as an organization does not mature much across initiatives, especially across time.

Change maturity assessment is focused on building change capability across the organization across different dimensions, whether it be project change management, operational change or change leadership. The goal of conducting a change maturity assessment is to identify areas in which there may be a capability gap and therefore enable structured planning to close this gap.  The meaning of ‘capability’ does not just refer to people skills, but also to process and system capabilities.

Change maturity assessment results may prompt focus and action to improve change management capabilities if used in the right channels to influence the leadership and the business.

There are 2 major change maturity assessment models available in the market. The first is by Prosci and the second is by the Change Management Institute (CMI).  Read up more about CMI’s Organisational Change Maturity Model here.  To read more about change maturity assessment read out article A New Guide for Improving Change Management Maturity, where we outline how to improve change maturity throughout different business units across the organization.

A comprehensive model of Change Management Measures

In this diagram various change management measures are represented along two axes, one being the different phases of the initiative lifecycle, and the other being different organizational levels of project, business and enterprise in which change management measures fall into.

In the broad initiative phases of Plan, Execute and Realise there are various change measurements and assessments that may be applicable.  At the Business and Enterprise levels, these measurements and assessments are not so much split according to initiative phases.  Instead, they may be conducted periodically, for example change capacity and impost tracking may be done on a monthly basis, with change maturity assessment conducted at an annual basis.

Project level measures

1. ‘Plan’ phase

In this phase of the project, the team is discovering and scoping what the project involves and what the change is. As a result, the details are not known clearly at the commencement of the phase. Later in the phase the scope becomes much clearer and the team starts to plan what activities are required to implement the change.

  • The change complexity assessment evaluates how complex the project is. It looks at how many people could be impacted, what the size of the impact could be, how many business units are impacted, whether multiple systems and processes are impacted, etc.

  • Change resourcing costing. At the planning phase of the project cost required for the change management stream of the work is required. This includes such as any contractors, communication campaigns, learning cost, travel, and administration cost, just to name a few.

  • Change readiness assessment is usually conducted prior to the change and during the change. Usually, the same set of questions is asked of various stakeholder groups to assess their readiness for change.

2. ‘Execute’ phase

The execute phase is one of the most critical parts of the project. Activities are in full flight and the project is busy iterating and re-iterating changes to ensure successful execution to achieve project goals.

  • Communication and engagement tracking. Effective engagement of stakeholders in the change is absolutely critical. Stakeholder interviews, surveys, communication readership rates are all ways in which engagement may be tracked.

  • Learning tracking. Measuring learning is critical since it tracks to what extent the new competencies and skills have been acquired through learning interventions. Typical measurements include course tests or quizzes in addition to course evaluations. On the job performance may also be used to track learning outcomes and to what extent learning has been applied in the work setting.

  • Change readiness assessment continues to be critical to track during the execution phase of the project

3. ‘Realise’ phase

In this phase of the project the change has ‘gone live’ and most project activities have been completed. It is anticipated in this phase that the ‘change’ occurs and that the benefits can then be tracked and measured.

  • Change benefit tracking measures and tracks the extent to which the targeted benefits and outcomes have been achieved. Some of these measures may be ‘hard’ quantitative measures whilst others may be ‘soft’ measures that are more behavioural.

 

Business level measures

Business level measures are those that measure to what extent the business has the right ability, capacity, and readiness for the change.

  • Change heatmaps can help to visualize which part of the business is most impacted by 1 project or multiple projects. The power of the change heatmap is in visualizing which part of the business is the most impacted, and to compare the relative impacts across businesses. As the number of change initiatives increase so would the complexity of the change. When facing this situation organisations need to graduate from relying on excel spreadsheets to using more sophisticated data visualization tools to aid data-based decision making. To read more about change heatmaps and why this is not the only way to understand business change impact, go to The Death of the Change Heatmap.

  • Sponsor readiness/capability assessment can be a critical tool to help identify any capability gaps in the sponsor so that effort may be taken to support the sponsor. A strong and effective sponsor can make or break a change initiative. Early engagement and support of the sponsor are critical. Both Prosci, as well as Changefirst, have sponsor competency assessment offerings.

  • Change champion capability assessment. Change champion or change agent are critical ‘nodes’ in which to drive and support change within the organizational network. A lot of change champions are appointed only for one particular initiative. Having a business-focus change champion network means that their capability can be developed over time, and they can support multiple initiatives and not just one. Assessing and supporting change champion capability would also directly translate to better change outcomes.

  • Change leadership and change maturity assessment – refer to the previous section

  • Change capacity assessment.

In an environment where there is significant change happening concurrently, careful planning and sequencing of change in balance with existing capacity are critical. There are several aspects of change capacity that should be called out in the measurement process:

1. Different parts of the business can have different capacity for change. Those parts of the business with better change capability, and perhaps with better change leadership, are often able to receive and digest more changes than other businesses that do not possess the same level of capability.

2. Some businesses are much more time-sensitive and therefore their change capacity needs to be measured with more granularity. For example, call centre staff capacity is often measured in terms of minutes. Therefore, to effectively plan for their change capacity, the impacts of change needs to be quantified and articulated in a precise, time-bound context so that effective resourcing can be planned in advance.

3. The change tolerance or change saturation level for business needs careful measurement in combination with operational feedback to determine. For example, it could be that last month a part of the business experienced significant change impact across several initiatives happening at the same time. The operational indicators were that there was some impact on customer satisfaction, productivity, and there were negative sentiments reported by staff that there was too much change to handle. This could mean that the change tolerance level may have been exceeded. With the right measurement of change impact levels for that part of the business, next time this level of change is seen, previous lessons may be utilized to plan for this volume of change. Utilise measurement and data visualization tools such as the Change Compass to track change capacity.

AI-driven systems such as Change Compass can now detect change saturation hotspots across teams or departments by analysing workload data in real time. These systems also provide actionable recommendations on how to sequence or prioritise initiatives to minimise disruption while maximising performance outcomes.

Enterprise level change measures

At an enterprise level, many of the business unit level measures are still applicable. However, the focus is comparing across different business units to sense-make what each part of the business is going through and if the overall picture is aligned with the intentions and the strategic direction of the organization. For example, typical questions include:

  • Is it surprising that one part of the business is undergoing significant change whilst another is not?

  • Is there a reason that one business unit is focused on a few very large changes whilst for other business units there is a larger set of changes each with smaller impacts?

  • Is the overall pace of change optimum according to strategic intent? Does it need to speed up or slow down?

  • What is the process to govern, report and make decisions on enterprise level change, prioritization, sequencing and benefit realization?

  • Is there one business unit that is able to manage change more effectively, faster with greater outcomes? How can other business units leverage any internal best practices?

As mentioned in the Change Management Measures diagram, some enterprise level change measures include:

  • Change capacity assessment – Does one business unit’s change capacity limits mean that we are not able to execute on a critical strategy within the allocated time? How do we create more capacity?   Ways in which to create more capacity could include more resources such as staff, or initiative funding, more time is given, or more talent to lead initiatives

  • Change maturity assessment – At an enterprise level, the concern is with the overall change maturity of the organization. How do we implement enterprise level interventions to build change maturity through programs, networks, and exchanges, such as:

    • Enterprise change capability programs

    • Enterprise change analytics and measurement tools

    • Enterprise change methodology

    • Enterprise network of change champions

  • Strategy impact map – Change management need not be focused only on project execution or business unit capability. It can also demonstrate value at an enterprise level by focusing on strategy execution (which by definition is change). The way in which different strategies exert impact on various business units may be visualized to help stakeholder understand which initiatives within which strategic intent impact which business units.  To illustrate this please refer to the below diagram which is an example of a strategy impact map. In this diagram, each of the organisation’s strategy is displayed with different initiatives branching out of each strategy. The width of each initiative correlates with the level of impact that the initiative has on the business over a pre-determined period of time. Therefore, the width of each strategy also indicates the overall relative impact on the business.

Enterprise change management dashboard

 

This data visualization artifact can be valuable for business leaders and strategic planning functions as it depicts visually how the implementation of various strategies is impacting business units.   This helps planners to better understand strategy implementation impacts, potential risks and opportunities, and balancing change pace with strategy goals at various points in time.

  • Predictive indicators on business performance – We started this article talking about how data is all around us and we also need to better manage change using data. With quantitative data on change impact, it is possible to ascertain any correlations with operational business indicators such as customer satisfaction, service availability, etc. For those business indicators where there is a significant correlation, it is possible to hence use predictive reporting to forecast performance indicator trends, given planned change impacts.

In the below graph you can see an example of this whereby using historical data it is possible to establish correlations and therefore forecast future impact on business indicators. This example is focused on the customer contact centre (CCC) and key business indicator of average handling time (AHT) is utilized as an illustration.

This type of predictive performance forecasting is extremely valuable for organisations undergoing significant change and would like to understand how change may impact their business performance. By demonstrating the impact on business indicators, this puts the importance of managing change at the front and centre of the decision-making table. At The Change Compass, we are developing this type of measurement and reporting function. This is the frontier for change management – to be established as a key business-driving function (versus a standard back-office function).

With AI-powered platforms, stakeholders can now ask natural language questions like ‘What is the current adoption rate of Initiative X?’ or ‘Which teams are at risk of exceeding their capacity?’ Platforms such as Change Compass provide instant answers backed by real-time data analysis, saving time and enhancing decision-making accuracy.

Change can be measured and this article has outlined various operational and strategic ways in which change measurement can demonstrate significant value. Most corporate functions cannot exist without data and analytics. For example, Human Resources relies on people and pay data. Marketing cannot function without measurement of channel and campaign effectiveness. For Information Technology, pretty much everything is measured from system usage, to cost, to efficiency. It is time we start utilizing data to better visualize change to better plan and make business decisions.

 

Have a chat with us if you are looking for ways to streamline how you capture, visualise data for decisions, and leverage AI to easily generate insights.  This includes the ability to easily do forecasting, ask data questions using natural language and get instant answers.

 

And If you’re ready to start implementing your change metrics check out the Part 2 of The Ultimate Guide to Measuring Change.

 

 

References:

Miller, David (2011) Successful Change. How to implement change through people. Changefirst Ltd.

Pagon & Banutal (2008) Leadership Competencies for Successful Change Management. Study Report. University of Maribor.