When I was a kid, I used to love my Walkman. I’d create mixed tapes of my favorite songs and share them with friends, spending hours discussing our favorite tracks. The rewind button on my Walkman got a lot of use, and I couldn’t imagine anything ever replacing it. But, of course, it did. Several times over. First, Walkman models with higher fidelity came out, followed by slimmer versions, and then tapes gave way to mini-disc players. Eventually, CD players emerged as the new standard. After a few generations of iPods, we now have phones and watches that have made the Walkman nearly obsolete.
Change is inevitable and, in today’s world, business leaders must recognize that it’s happening at an unprecedented pace. Technological advancements, innovation, and globalization are driving this accelerated rate of change. Companies, no matter the industry, must continually adapt to remain competitive. For instance, Apple, once a small player in the mobile phone industry, has now become the world’s largest smartphone manufacturer, displacing giants like Motorola, Nokia, and RIM. Utilities are grappling with changes due to grid modernization, fluctuating commodity prices, and the shift toward renewable energy sources. Financial services companies, including those involved in financial accounting, are dealing with a myriad of challenges, from regulatory changes to the cost of maintaining IT infrastructure and growing competition in the digital banking sphere.
This wave of change isn’t confined to a few industries but extends to telecommunications, certain government departments, and healthcare, among others. Companies across the board are facing an array of transformative initiatives.
In today’s dynamic business environment, change managers must focus on managing multiple successful change management initiatives, particularly at an enterprise-wide scale, as it is a complex challenge. Organizations must ensure that these changes engage the entire team, are well-coordinated, align with overall business goals, and positively impact employee performance and customer experience.
Change initiatives are essentially projects that require employees—and in some cases, customers—to adapt to new processes, tools, or behaviors through a systematic approach as part of the strategic plan for successful change initiatives. Whether it involves adopting a new system interface, understanding a new product, or adhering to a revised company policy, these initiatives necessitate behavioral changes. However, the challenge lies in the fact that these initiatives often cut across multiple departments within an organization.
For instance, a new IT system rollout impacts not only the IT department but also influences how other departments operate. Similarly, a new HR policy affects the entire organization, while changes to a product’s features can impact marketing, sales, and customer support teams. The ripple effect of these changes means that rarely does an initiative impact just one department—it often affects many areas of the organization, sometimes leading to conflicting priorities and confusion.
However, here’s the challenge: these change initiatives often affect multiple departments within an organization. For example, a new IT system rollout impacts the IT department but also influences how other departments work. A new HR policy influences the entire organization, while changes in a product’s features affect the marketing, sales, and customer support teams.
The consequence is that change initiatives rarely affect just one department; they have a ripple effect across the organization. In some cases, an initiative might even contradict another department’s efforts, leading to confusion and inefficiency.
To manage these changes effectively, organizations must gain a holistic view of all ongoing initiatives, including the company culture and corporate culture as well as organizational culture. This means understanding what changes are happening, when they’re happening, and how they’ll impact different employee and customer groups, which will ultimately improve the chances of success.
A Unified View of Change
The challenge for large organizations is to create an integrated view of all change initiatives, particularly during the implementation process, to sustain outcomes for the long term. For smaller companies or industries with relatively stable environments, spreadsheets might suffice. But for larger, more complex organizations, including senior executives, with operations spanning different regions and functions, a more rigorous approach is necessary, as constant transformation has become a top priority.
Sadly, many large organizations still rely on standalone spreadsheets that require extensive manual effort for data collection, verification, analysis, and reporting. These spreadsheets often focus on cost, timeline, and resource data but tend to overlook a crucial piece of the puzzle: change impact data, which reveals how employees and customers are affected by an initiative.
Imagine the sheer volume of changes a sizable financial services company may face in a year. There could be over 10 legislative changes, countless business improvement initiatives, multiple restructuring efforts, numerous technology updates, and various divisional policy changes. And this is just the beginning. The overall list of change initiatives can be overwhelming.
When I talked to colleagues in divisional operations, they often expressed their difficulties in keeping track of changes. They struggled to understand what changes were happening, which department was driving them, which teams were affected, the timing of these changes, the nature of the impact, and the size of the impact.
With each department maintaining separate spreadsheets or, worse, not having any centralized system, the result was continuous disruptions to employee performance and operational efficiency. Imagine a scenario where one department pushes its call center to sell a product, while another department sends out notices stating that the same product is nearing end-of-life. The resulting confusion affects not only employee performance but also the customer experience.
For organizations dealing with a multitude of changes, how can they create an integrated view of all change initiatives, regardless of whether they involve legislative, technological, policy, strategic, or product changes?
Utilizing Technology for Change Management
To effectively manage the complexity of numerous change initiatives, organizations can benefit from an online tool. The tool should help reduce complexity, enhance communication, and improve risk management. Here are the key characteristics such a tool should have:
Ease of Administration: The tool should be simple for both those driving change and key stakeholders receiving it. It should efficiently capture essential data related to people’s change impacts, including key performance indicators relevant to the project’s success.
Focused on Impact Data: While the tool should cover essential project and business data, its primary focus should be on collecting key impact data. This data complements existing data, enhancing the overall change management strategy.
Effective Reporting Tools: The tool should offer effective and flexible reporting tools. These help operational managers, project management offices (PMOs), and senior managers plan for people’s readiness for change initiatives.
Analysis Capabilities: The tool should include analysis features to identify change risks. These analyses could include change loading and timing issues, which might necessitate reprioritization of initiatives.
Customization: Each organization is unique in terms of its departments, types of changes, and reporting requirements. The tool should be adaptable to accommodate these differences.
However, the effectiveness of any tool depends on how well people use it. An effective tool for presenting a sequence of changes the company is undertaking should be complemented by two crucial aspects:
1. Establishing Processes and Governance to Embed the Tool
Successfully embedding a portfolio management tool across an organization requires establishing a clear operating rhythm and consistent processes for its use. Each division should have defined roles and responsibilities to ensure that the tool is effectively utilized and that data is accurately entered and maintained.
For instance, in the digital marketing department, specific roles should be designated to coordinate product changes, ensuring that every relevant update is promptly entered into the tool. These roles might also include responsibilities for analyzing the data provided by the tool to optimize product launch strategies, aligning them with other ongoing initiatives, and avoiding conflicts.
As organizations adopt an integrated view of change initiatives, it becomes increasingly important to establish an enterprise-level governance body or committee. This governance body should oversee the ongoing development, deployment, and usage of the tool, ensuring it continues to meet the evolving needs of the organization.
The committee should be composed of representatives from various departments, including IT, marketing, HR, and operations, to address the diverse needs of stakeholders across the organization. This body would regularly review the strategic implications of the tool’s data, discuss risks associated with change delivery, and prioritize initiatives based on their potential impact.
By maintaining this operating rhythm, organizations can ensure that the tool becomes an integral part of their change management processes and the company’s culture, driving better coordination, reducing risks, and enhancing decision-making at both the strategic and operational levels.
Once an organization has established an integrated view of its change initiatives through a robust portfolio management tool, the focus shifts to leveraging this data to inform critical business decisions. The data generated by the tool can be instrumental in guiding decisions related to various aspects of change management, such as enhancing the organization’s competitive advantage.
Employee Capacity Management: The tool provides visibility into the number and scale of ongoing initiatives, enabling leaders to assess whether employees have the capacity to absorb additional changes without experiencing burnout or a decline in productivity. By understanding the cumulative impact of these initiatives, the organization can plan and stagger changes to ensure sustainable workload levels.
Resource Allocation: With a comprehensive view of all change initiatives, organizations can make more informed decisions about how to allocate resources effectively in their organizational leadership. The tool allows leaders to prioritize initiatives that align with strategic goals and allocate resources to those with the greatest potential impact.
Customer Experience Management: The data can also help anticipate the potential effects of various initiatives on customer experience. By identifying and mitigating risks early, organizations can ensure that changes do not negatively impact customer satisfaction or loyalty.
Timing and Sequencing of Initiatives: The tool enables organizations to analyze the timing and sequencing of change initiatives to minimize disruptions and conflicts. This strategic approach ensures that initiatives are rolled out in a manner that optimizes their impact while minimizing operational risks.
Strategic Alignment: By providing real-time insights into how ongoing initiatives align with the overall business strategy, the tool supports decision-making that engages team members and ensures every change initiative contributes to the organization’s long-term objectives.
Moreover, the tool’s ability to capture and analyze historical data is invaluable. By examining past initiatives, organizations can gain insights into optimal change capacity and identify patterns or trends that inform future decision-making. This historical perspective enables organizations to predict and plan for change more effectively.
Implementing an enterprise-level change management tool not only provides a comprehensive view of all change initiatives but also significantly enhances the organization’s overall change management capability. As processes and internal processes are refined to support the tool, the organization becomes more agile, resilient, and capable of managing change effectively, ultimately driving better business outcomes.
In this article, we’ve emphasized the importance of understanding what is changing and having an integrated view of initiatives. To experience the transformative power of The Change Compass, join our Weekly Demo every Tuesday to enhance your business performance.
Change management methodologies are designed to facilitate the process of implementing organizational changes effectively. However, a lot of traditional change management approaches tend to be too rigid and waterfall-like, hindering organizations from embracing agility and adapting to a required change. Despite the fact that most organisations are using agile methodology to implement change, methodologies have not kept up to date.
Waterfall vs. Agile: The Need for Change
The waterfall model, characterized by a sequential and linear approach to project management, has long been the dominant framework for managing change in organizations. It follows a structured path, where each phase is completed before moving on to the next. While this approach has its merits, it often falls short when it comes to change management, which requires flexibility and adaptability.
Agile methodologies, on the other hand, emphasize a strategic approach to iterative and incremental development, promoting collaboration, continuous improvement, and rapid response to change. Agile has gained significant popularity in software development, but its principles can be applied to change management as well. By embracing agility, organizations can navigate the complexities of change more effectively, fostering innovation and resilience.
Most change management methodologies, despite the need for agility and adaptability, often retain a waterfall-like structure. Let’s delve into each phase to understand how this traditional approach persists.
Scoping: In the scoping phase, the change management team typically focuses on defining the scope of the change initiative. However, this phase tends to follow a waterfall approach, where the scope is predetermined and set at the beginning of the project. There is limited room for flexibility or adjustments based on evolving requirements or stakeholder feedback.
Stakeholder analysis: In traditional change management methodologies, stakeholder analysis is often conducted early on in the process. However, this analysis is frequently treated as a one-time activity, with limited opportunities for ongoing engagement and collaboration with stakeholders. This lack of continuous involvement hampers the ability to incorporate diverse perspectives and adapt the change strategy accordingly.
Impact analysis: Impact analysis aims to assess the potential consequences of the proposed change on various aspects of the organization. While this phase acknowledges the need to consider impacts, it often relies on linear and predictable assumptions. The waterfall nature of impact analysis fails to account for the dynamic nature of change and the potential for unforeseen effects or emergent patterns.
Change planning: Change planning in traditional methodologies tends to be highly detailed and extensive, often resulting in voluminous documentation. These plans are typically developed early in the process and are expected to remain static throughout the execution phase. This rigidity can be problematic, as change initiatives require adaptability and the ability to respond to emerging challenges and opportunities.
Execution: The execution phase in waterfall-like change management methodologies is often characterized by a linear sequence of tasks and activities. This sequential approach assumes that each step can be completed before moving on to the next. However, in reality, change initiatives can encounter unexpected roadblocks or require course corrections, rendering this rigid execution process inadequate for effectively managing change in dynamic environments.
Overall, these traditional phases demonstrate how most change management methodologies are still designed with a waterfall mindset, focusing on sequential processes, rigid planning, and limited opportunities for flexibility and adaptation. To truly embrace agility in change management, organizations must shift towards iterative and collaborative approaches that prioritize stakeholder engagement, continuous learning, and the ability to adjust course based on evolving needs and circumstances.
Paying lip service to ‘agile-fy’
To pay lip service to make the methodology more ‘agile friendly’ a lot of proponents of change management methodologies have come up with ways to do this.
Matching the phases to agile work phases
Some have matched the change management methodology to agile work phases to try and make it more agile. This includes matching the planning activities done by change managers to those done by the rest of the agile team, and matching the change management approach to agile delivery phases.
Mapping a waterfall style change management methodology to an agile project does not make your approach agile. Your project change activities may be in synch with the rest of the team, but it does not mean that your approach is more agile.
2. Over-focus on agile ‘capability’
Agile project approaches are about the mindset and a way of operating. Yes, ideally we want to be able to educate and improve the agile mindset and capabilities of everyone across the organisation. However, we know that in reality we may be lucky if a pocketful of stakeholders understand agile ways of working.
The same also applies to change management capability. We can invest heavily on change management capability and try and uplift this across several years. However, the most critical parts of learning is learning through ‘doing’. Learning agile ways of implementing initiatives is best through being involved.
Your stakeholders will related to the experience of being in agile initiatives and remember this a lot more than any training sessions that they go on.
3. Doing more
Some have taken the approach that with agile, there are certain activities we need to do more of, and that doing more of these activities will somehow help us to be more agile in our approach.
More communication about agile approaches. More training. More sponsor alignment. More reinforcement of agile outcomes and phases.
Doing more of these activities may be somewhat beneficial depending on your organisation, again it does not make your change approach more agile. This approach is focused on providing ‘support’ for the organisation. It is also you acting as a side-party from the rest of the agile project team, helping the organisation to accept agile. In some situations this may be needed, but again it detracts from what makes your methodology and approach more agile.
How to change your change methodology to be more agile
The “Get One Piece Done” principle from the book ‘Shape Up’ by Ryan Singer is an excellent concept that describes one of the core practices of agile. If there is one core agile principle in which to remember to get the biggest impact, this is it. It offers several advantages over traditional waterfall-like approaches:
Focus on outcomes: Instead of getting stuck in lengthy planning and documentation phases, this principle encourages organizations to focus on delivering tangible results. By setting a clear goal for each bet, teams can align their efforts toward achieving specific outcomes.
Embrace flexibility: Change is unpredictable, and rigid plans can quickly become outdated. By working in short cycles, organizations can adapt to evolving circumstances more effectively. If circumstances change, teams can adjust their course and priorities accordingly during the subsequent bets.
Foster collaboration and autonomy: The “Get One Piece Done” principle promotes collaboration and empowers teams to take ownership of their work. Teams have the autonomy to decide how to approach and complete their bets, fostering creativity and engagement.
Learn and iterate: Agile approaches emphasize learning and continuous improvement. After completing a bet, teams reflect on their experience and incorporate feedback into subsequent bets. This iterative process allows for rapid adaptation and refinement of change initiatives.
The following diagram (adapted from the book) illustrates how to use the ‘Get one piece done’ principle in ‘shipping’ change work. In agile software development, the term ‘ship’ means to deliver an output to the customer. This does not include any work internal to the project team such as planning, testing, and technical development. It is only when a piece of software is ready to be shown with working functions, that it is said to be ‘shipped’.
Change practitioners should also adopt the same agile approach in their work. Rather than relying on a series of project work phases and only ‘ship’ at the end of the project, is much more ‘waterfall’ in approach than agile. Agile teams ‘ship’ solutions throughout the project. Likewise, change practitioners can also ‘ship’ a range of change outcomes throughout the project.
Don’t wait until we have more clarity. The solution is evolving so the ‘clarity’ will also continue to evolve.
Continue to pulse and experiment as the solution continues to evolve. Just like how the agile team is showcasing features continuously as the solution is being developed, change managers should also showcase the change approach and findings through experiments.
For change management, this means testing different pieces of the change approach throughout the project.
Testing engagement channels/medium
Testing messages
Testing training content
Testing town hall design
Testing team briefing design
Testing impact assessment
Testing implementation loading/capacity
Testing speed of adoption
Testing level of engagement
Testing continuation of adoption
What key features should each test incorporate?
Each test should be small enough to be released quickly without too much work, buy-in and time.
Ideally each test should also be ‘new’ and not have been tested before. Note that even if it had been tested by another project, the context could be different.
The number one focus for each experiment is to learn something that will help you form the overall change approach.
So unlike most methodologies where the tracking, measurement and adaptation of the change approach happens at the end after the release, in an agile approach it should happen as early as possible. The eventual change management approach should be an aggregation of a series of tests and small ‘change releases’ that result in the eventual change approach.
The Importance of Change Models
Change models play a critical role in the change management framework as they provide structured methodologies to navigate the complexities of change projects and organizational change. By employing a change model, organizations can streamline the change implementation process, ensuring that everyone is on the same page and that potential pitfalls are addressed proactively. Change models not only guide leaders in formulating a strategic vision but also help in managing the emotional and psychological aspects of change, which are often overlooked. This structured approach is essential in minimizing resistance and fostering acceptance among stakeholders, ultimately leading to a more successful transition.
Understanding the fundamental principles of various change models equips organizations with the tools necessary to tailor their change management strategies effectively. The right change model can serve as a compass, guiding teams through the intricacies of change while promoting alignment across different levels of the organization. As businesses increasingly recognize the need for agility, embracing these models becomes crucial in cultivating a resilient organizational culture that can thrive in the face of continuous change.
Several organizational change management models stand out for their effectiveness in guiding change initiatives. The ADKAR model focuses on individual level transitions, ensuring that each level of resistance is addressed. Lewin’s change management model emphasizes unfreezing, transitioning, and refreezing to ensure lasting change. Kotter’s theory provides a structured eight-step approach, crucial for fostering a culture that embraces change. Lastly, the Burke-Litwin model integrates both hard and soft elements, highlighting the importance of alignment with the company’s structure for successful change implementation.
Lewin’s Change Management Model (from Blog Outline 1 & 2)
Adapting the Burke-Litwin Change Model fosters a deeper understanding of organizational dynamics. This model emphasizes the interplay between hard elements, such as structures and systems, and soft elements, like culture and leadership. By effectively addressing these layers, change managers can identify levers for meaningful transformation. Utilizing tools like the ADKAR model alongside Burke-Litwin enhances communication and minimizes resistance during transitions. Overall, a strategic approach ensures that change initiatives are aligned with the company’s hard elements and structure, facilitating a smoother progression towards successful implementation.
McKinsey 7-S Model (from Blog Outline 1 & 2)
Integrating the Burke-Litwin Change Model can significantly enhance adaptability within organizations. This framework emphasizes the interplay between soft elements, such as company culture and motivation, alongside hard elements like organizational structure. By identifying key drivers behind change initiatives, leaders can effectively navigate the transition model. The Burke-Litwin model guides change managers through the complexities of change management processes, ensuring alignment with overall strategic objectives. Utilizing this approach enables a deeper understanding of resistance levels and fosters successful change implementation.
The Burke-Litwin Change Model
The Burke-Litwin Change Model is a comprehensive framework that examines the intricate relationships between various organizational elements during change initiatives. This model identifies 12 interconnected factors, such as external environment, leadership, and detailed change management plan, which influence how change is perceived and implemented. By recognizing these interdependencies, organizations can better anticipate levels of resistance and tailor their change strategies accordingly.
A key aspect of this model is its focus on the distinction between transformational and transactional changes. Transformational changes often require shifts in organizational culture and values, while transactional changes may involve adjustments to processes or systems. By understanding these levels of change, leaders can apply Kotter’s Theory for change management to address resistance effectively, ensuring that employees are supported throughout the transition. This holistic approach empowers organizations to create sustainable change that is aligned with their strategic goals while minimizing disruption and resistance in the process.
Measurement
Measurement plays a crucial role in agile change management experiments, enabling organizations to assess the effectiveness and impact of their initiatives. Here are a few key reasons why measurement is essential in the context of agile change management:
Assessing Progress: Measurement allows organizations to track the progress and outcomes of their change management experiments. By establishing clear metrics, including change management metrics and key performance indicators (KPIs), teams can objectively assess how well they are progressing towards their goals. This provides visibility into the effectiveness of different strategies and helps identify areas that require adjustments or improvements.
Data-Driven Decision Making: Agile change management emphasizes making decisions based on empirical evidence rather than assumptions or guesswork. Measurement provides valuable data and insights that inform decision-making processes. By collecting and analyzing relevant data, organizations can apply nudge theory to make informed choices about adjusting their approaches, reallocating resources, or prioritizing specific actions.
Learning and Continuous Improvement: Measurement is instrumental in facilitating learning and continuous improvement. Through regular measurement and evaluation, organizations gain insights into what works and what doesn’t. By analyzing the data, teams can identify patterns, uncover root causes of challenges, and discover opportunities for optimization. This iterative process enables organizations to adapt their strategies, refine their approaches, and enhance the effectiveness of future change management experiments.
Demonstrating Value: Measurement helps organizations demonstrate the value and impact of their change management initiatives. By quantifying the outcomes and benefits achieved through the experiments, organizations can communicate the success and value of their efforts to stakeholders, leadership, and other teams. This not only fosters transparency but also builds credibility and support for future change initiatives.
Alignment with Strategic Objectives: Measurement allows organizations to align their change management experiments with strategic objectives and desired outcomes. By establishing relevant metrics and aligning them with organizational goals, teams can ensure that their efforts are contributing to the overall strategic direction. Measurement provides a means to assess whether the experiments are moving the organization closer to its desired state and achieving the intended benefits.
Accountability and Transparency: Measurement promotes accountability and transparency within change management initiatives. By setting measurable targets and regularly reporting on progress, teams can ensure that they are accountable for the outcomes of their experiments. This transparency also enables stakeholders and leadership to understand the impact of the change initiatives and make informed decisions based on the results.
In conclusion, while many change management methodologies still adhere to a rigid waterfall approach, there is a growing recognition of the need for agility in navigating change. By embracing the power of change management experiments, organizations can transform their change approach into a more agile and adaptive one, similar to the Deming Wheel.
Change management experiments provide a structured and iterative framework for testing and refining different strategies, interventions, and processes. They enable organizations to learn from real-world experiences, gather empirical data, and make evidence-based decisions.
By treating change as an ongoing series of experiments, organizations can continuously adapt and improve their approach, leveraging the power of agility to navigate the complexities and uncertainties of the ever-evolving business landscape, including the implementation of new processes. With a mindset rooted in experimentation and a commitment to measurement and learning, organizations can truly transform their change management practices and achieve more successful and sustainable outcomes.
To read up more about agile change management, visit our Agile Knowledge section for a range of articles on managing agile changes.
Agile methodology is fast becoming the ‘norm’ when it comes to project methodology. There are strong benefits promised of faster development time, the ability to morph with changing requirements, less time required to implement the solution, and a better ability to meet project objectives through continuous improvement. There aren’t too many organisations that do not use some form of agile project methodology in how they manage initiatives.
What started out as a way of developing software has evolved into the accepted methodology for managing projects. A scan of literature available on the internet shows a significant outline of the various roles, including the product owner and the development team, and their importance to stakeholders, including end users, in the agile project methodology process. Most roles are clearly outlined and accounted for. There are clear roles established for the business owner, the project manager, the scrum master, developers, testing and quality, product manager, architect, human-centred designer, and even IT operations.
However, there is a glaring gap. What about the role of the change manager?
A review of literature available through project management organisations such as APM (Association of Project Management) and PMI (Project Management Institute) showed glaring omission of the role of the change manager or change management practitioners from agile methodology. The same is also true for Scaled Agile Frameworks where there is a brief mention of the importance of change management in the agile approach, but no mention of the role of the change manager/practitioner.
Is it that there are less projects requiring change managers?
The evidence is against this hypothesis. Jobs in change management are plentiful, with data on ‘Indeed’ online employment portals pulling up over 38,000 job postings. On top of this, there is an increasing number of jobs posted. According to the U.S. Bureau of Labor Statistics, “management analytics” which includes change management, is projected to have a 14% growth rate between 2018 and 2028. In Australia, the ‘Seek’ employment platform projected change management job growth to be at 15% growth in the next 5 years.
Is it that agile methodology is more for technical projects and therefore the omission of change managers?
The agile approach and agile manifesto can be used for a range of different projects, but not all projects. There is certainly evidence of agile project methodology used by software developers in a wide range of industries from financial services, government, non-profit, pharmaceuticals, utilities, and retail industries. The agile methodology is commonly cited for being better for projects where the outcome is not clearly known and where the end change has a level of uniqueness. There are times, though, when waterfall methodology is more appropriate, depending on the situation.
However, it is not true that agile methodology is only used for more technical projects. Even for projects where the focus is not on technical development, agile approaches are used widely. Agile changes have been used for re-organisation exercises. Here is an example from the Business Agility Institute. Executive teams also use agile means to manage various strategic initiatives that are not technical. Agile approaches are even applied to managing church initiatives.
What is the likely reason for the clear omission of change management in the agile methodology?
Organisations in charge of documenting agile methodology are mainly focused on project management and software development. If we take the examples of PMI and APMG, both are project management associations, and both are focused on the project management perspectives of agile, particularly in complex environments. The portion on organizational change management is a specialism of project management. It could be that these organisations have not sufficiently developed agile change management methodology to integrate with agile project management.
Organisations in charge of documenting agile methodology are mainly focused on project management and software development, and not include the agile change management process. If we take the examples of PMI and APMG, both are project management associations, and both are focused on the project management perspectives of agile. The portion on organizational change management is a specialism of project management. It could be that these organisations have not sufficiently developed agile change management methodology to integrate with agile project management.
Even at Scaled Agile, which is about applying agile across the organisation, the omission of the role of change managers is still the case. Frameworks from Scaled Agile are quite detailed and rigorous. All aspects of the roles of various organisational members, including scrum teams, are clearly outlined. Even the role of IT departments in DevOps are clearly spelled out to support agile. But not the role of change managers. Again, this could be due to those at Scaled Agile not having a change management background, and therefore not being able to articulate the various role detail.
However, there are some very critical roles that change practitioners play not only at project level, but at program, epic, and organisational levels. Without the right change management support the following are key risks when organisations are working at SaFe (scaled agile) level:
Change sequencing to maximise adoption across the change portfolio
Packaging change to achieve optimal change adoption, e.g. in terms of integrating communications and learning interventions across projects
Establishing business unit based change champions that can support multiple projects and can help piece together different changes for impacted employees
There are some attempts at closing the gap to document agile change management approaches as a part of the change management process. However, most are conceptual, high level, and not sufficiently detailed to provide clear guidance and practical application for the change practitioner. On the other hand, the work of change management in agile projects should not only be clear for the change practitioner but also be clear for the project manager and other project members.
What’s the problem of omitting the role of change managers from agile methodologies?
1. The role of change management could easily be omitted. Particularly for less experienced project managers who are starting out in agile. The risk could be that change management is omitted from the project altogether since it is not called out as a clear role
2. Change practitioners and agile practitioners are not clear with the roles they play and therefore are not sufficiently involved in driving and supporting the project in the right way. Since there is not a clear set of guidelines and agile principles methodology for change practitioners, it is common to see varying approaches in how change managers support agile projects within the current business environment, with some still using a similar approach as to supporting traditional change management and waterfall projects which may not be appropriate.
3. Agile projects are not successful because change management work is not sufficiently incorporated into agile processes, particularly in the context of digital transformation. With change management roles not spelt out, the project executes the change without critical change management foundations, and therefore, by embracing agile thinking, it is at the risk of not achieving the adoption, adaptation, and benefit realisation targeted.
What should we do about this?
1. Encourage change management associations such as CMI and ACMP to invest in detailing agile change management methodology in a way that sets standards and guidelines for change management skills practitioners to follow.
2. Influence and work with APMG, PMI and Scaled Agile to include explicitly the role of change managers and agile change management methodology.
Change management is emerging to be a strong discipline that executives are starting to recognise as critical to successful change. The role of change practitioners should be stated explicitly and recognised clearly. Change managers should not have to tip-toe in maneuvering their place in supporting agile change projects, nor should they need to convince other project team members of their place throughout various agile routines and methodology phases. It is now time for the change community to drive this and achieve the recognition that it deserves.
Managing a set of change initiatives through a systematic approach in the project intake process and portfolio management process, often outlined in a table of contents, is relatively new for some organizations. This strategic approach is drawn from the portfolio project management method by dividing a set of initiatives into different teams and viewing various project ideas and initiatives in unison. By doing this, organizations can make more informed decisions, allowing things to become more manageable from the perspective of planning how to organize the strategic objectives and business goals of the planning and sequencing of these changes.
Project portfolio managers are focused on investment funding, program management, governance, project execution, project selection, and resource allocation, including selecting the best individual projects related to the best projects and those related projects endeavors. For portfolio change managers, there are similar focus areas such as change program management, change initiative execution, resource management, and quality assurance. However, there are also several marked differences, including a focus on business change governance, business change capability, change leadership, and change tools and methodology.
In practice, there is often a wide range of practices in the service delivery and model of portfolio change management. Some focus purely on supporting project delivery and provide valuable insights, and in the process fail to uplift business change capability. Others tend to focus on general change capability through training and development and very little on change governance and supporting strategy implementation.
So, what are some of the best practices in strategic portfolio management that align with strategic organizational goals and change portfolio management by coordinating with individual project managers in achieving a strategic portfolio of projects that support strategic goals and overall business strategy? How does the change portfolio management function position itself to be strategic, value-adding, and seen as a driver of business results? Here are 10 best practices.
1. Use hard data.
A lot of change professionals often shy away from data. We prefer to focus on behavior, leadership, mindsets, norms, and culture. Whilst the ‘soft’ things may matter we need to be comfortable in working with data. Peter Drucker’s famous saying goes ‘What gets measured gets done’.
Disciplines with a strong focus on data usually have a strong seat at the business table. For example, Finance, Operations, and Sales. Even Marketing is not just about creative ideas and concepts, but there is a strong focus on cost, revenue forecast, and customer responses. Armed with data that drives business decisions you get a strong seat at the decision-making table.
What types of data should portfolio change managers focus on? The standard change measures include training attendance, stakeholder ratings, and arbitrary business readiness ratings. To really demonstrate value, portfolio change managers need to turn change management into a science and be able to quantify change to inform investment decisions effectively. Change Impacts is one great example. By quantifying change impacts into discrete units one can start to measure and understand what changes are and how they move over time and across different parts of the business.
2. Link change practices with business outcomes
Continuing from the previous point – armed with quantitative change impact data, the portfolio change manager is able to analyze the data to find any correlations between change impact data and business performance data. This can become a very powerful picture to take to the senior management team – drawing out the impact of changes on business performance.
Based on data from The Change Compass. An organization has been able to draw significant correlations between change impacts and customer satisfaction levels. This has since raised meaningful discussions regarding the approach of implementing changes and how to mitigate any potential negative impacts on the customer experience. It does not necessarily mean minimize on change impacts on the customer. Instead, it challenges the group to think through how to better engage and prepare for the customer to transition through changes. This is a great example of demonstrating the importance of linking change impacts with business outcomes.
3. Focus on building change capability more than just execution
A lot of organizations treat change management as only discrete pieces of work that need to be carried out as a part of a project. With this approach, these organizations have hired mainly contractors with some permanent change managers purely focused on project execution. Whilst this work is absolutely required to successfully land initiatives, these resources come and go and in the end, the organization is often no better off in managing change.
Instead, there needs to be a continual focus on developing business change capability. This may be carried out in different ways. With each project implementation, the change manager may focus on uplifting change management capabilities in the business within its leaders. Effective engagement and learning channels can be established to better aid the deployment of change initiatives. These include self-paced training systems, know-how regarding establishing and measuring various learning interventions, and different types of employee engagement channels, both face-to-face and digital.
As change portfolio managers, a concerted focus on embedding business change capability can ensure that the business becomes more mature at undergoing change. A strategic plan can be developed that includes different ways of targeting capability uplift and change maturity. This requires business sponsorship and focus. It is also a critical part of effective operational management.
4. Design and manage change governance
Establishing effective change governance does not mean complicated multi-level governance with lots of documentation, policies, and procedures and lots of headcounts to manage the processes. Change governance means having the right processes to ensure there is sufficient oversight and visibility on what changes are going to happen and the effectiveness of change delivery.
Different organizations will establish different governance processes to suit the particular cultural and business environment. However, at the most basic level, there should be a regular cadence where managers can see and visualize the changes that are going to happen, and discuss any risks and issues with the picture they are seeing. At the same cadence, there should also be a review of the previous changes and how they’ve been rolled out, with a view to identifying opportunities for improvement.
There should also be different levels of change governance for larger organizations. For a business unit, there should be a change governance focusing on changes within the business unit. There should also be an enterprise-level change governance focused on changes across the organization. At the enterprise level, the discussion will be on strategic initiatives that run across the company. There should also be discussions on any risks and issues with business readiness and the progress of the change.
A standard meeting agenda for change governance would include the following:
Review the previous month’s changes including callouts of highlights, challenges, employee engagement, results, and overall progress
Examining metrics around the amount of change and to what extent the level of changes can be digested by the business appropriately
Identifying potential contentions of concurrent changes within the plan. If concurrent changes are being released into the business, discussions should zoom in on the quantum and nature of change contention, rationale as to why the business may not be able to handle the volume of changes, and implications if the releases were to proceed
Examining the data to ensure that all changes are captured and there is nothing missing. Change data should contain key projects being implemented, BAU changes, and other corporate programs from groups such as IT or HR
Examining the overall upcoming change slate and identify upcoming risks and opportunities as a part of risk management. Opportunities may include potential gaps where there is very little change, and where there may be opportunities for initiatives to land
5. Leverage digital tools
Change portfolio managers manage the slate of projects using a structured process of funding, prioritization, analysis, and review based on data, ensuring strategic alignment with business objectives and maximizing business value. In a similar vein, so should change portfolio managers, particularly when considering insights from project proposals and a project management office. The power that change managers have is not around cost or schedule data; it is on change impact and change readiness as discrete data points, including the crucial role of the contributions of team members. The challenge is how to collect, analyze, present, and leverage the power of these data.
The Change Compass is a change portfolio management software that quantifies and packages change impacts into data that can be easily analyzed and presented in various visual formats to decision-makers in real time, as a part of effective portfolio management. Visuals are specifically designed to make people change decisions, and are not just simple headlamps or Gantt charts. Initiative owners who own the source of the information update change impact data. Up-to-date change impact project data can be accessed at any time with reporting generated automatically. The portfolio change manager can easily dissect, drill down, and cut data to find out the change health of the portfolio:
Is there too much change?
How is our staffing resource impacted by change activities (especially for resource-sensitive areas such as call centres)
What’s the change tolerance level for the business?
How are various stakeholder groups impacted by the changes?
How are initiatives under particular strategic themes impacting the business?
How are customers and their respective experiences impacted by our initiatives?
6. Examine customer impacts
At a portfolio level, it is not sufficient to just focus on internal employee and stakeholder impacts. The change portfolio management team manager also needs to place focus on how are customers impacted by the planned changes. This drives at the core of the focus of a lot of the organizations on the customer.
One large financial services organization that was focused on customer experiences started analyzing data on customer change impacts across initiatives. Through this, there was a significant realization that the same group of customers was impacted by 6 significant initiatives at the same time. Across each of these initiatives, there was no coordination and the silo approach meant that poor synchronization and coordination could lead to a very poor customer experience. Subsequently, new roles and remits were created to manage this customer experience through facilitating a coordinated approach to planning and implementing initiative rollout.
7. Iterative planning
Iterative planning is a core of agile ways of working. At the core of iterative planning is the belief that we don’t always know the solution that we are striving for at the beginning of the change initiative. It is when we start testing and getting feedback from users that we are able to refine our proposal and be able to come up with a solution that suits the organization.
To truly support agile ways of working, change management needs to be able to develop prototypes of the change approach, and be able to morph or tweak the approach as required based on feedback. For example, a change approach can be tested on a particular team, the change champion group, or a selected trial group. Communication and engagement approaches as well as learning approaches can be tested in these groups.
Want to learn more about managing change portfolios?
If you’re ready to start to manage a portfolio of change initiatives using data and insights, have a chat to us about how to leverage The Change Compass capabilities to help you pinpoint key risks and opportunities in managing across initiatives. To book a demo click here.
Enterprise change management reporting is changing. In today’s dynamic business environment, it no longer consists of general updates on organisational change management efforts, change leaders, streams of project progress, or updates on various change capability training session volumes and satisfaction rates. Executives are demanding more value from enterprise change functions that incorporate change management practices and digital transformation, leveraging new tools. The pace of change since Covid has not slowed down. For many, it has increased in pace and volume. To gain better insight into how the change management function is supporting the success of organisations, reports and dashboards have often become a visible linchpin of what value enterprise change management delivers.
What is enterprise change management and why is it important?
Enterprise change management refers to the structured approach organizations use to manage the people side of change in organizational change management, including the types of organizational change in processes, systems, and personnel across an entire organization, while integrating risk management principles. It’s crucial for minimizing disruption, ensuring smooth transitions, and enhancing employee engagement. Effective change management fosters resilience, boosts productivity, and aligns teams with organizational goals for sustained success.
What is enterprise change management and why is it important?
Enterprise change management refers to the structured approach organizations use to manage changes in processes, technologies, and organizational structures, including various type of change efforts that relate to the levels of change management. It’s crucial for minimizing resistance and ensuring smooth transitions. Effective change management enhances employee engagement, drives project success, and fosters a culture of adaptability within the organization.
Having the right content and format for your enterprise reports can make or break your reputation in the realm of information technology. Do it right and you could start a ripple of high-impact and strategic conversations across senior stakeholders that drive focus on improving change. You can be in the spotlight in influencing change leadership and the achievement of change and transformation goals. Do it wrong and you may never have another opportunity to have the room to talk about change management to senior leaders. You may be associated with not providing much value and too ‘operational’.
At its core, enterprise change management reporting goes beyond merely tracking progress. It encompasses a holistic approach that considers various factors crucial to the success of organizational initiatives. While monitoring progress, readiness, and the amount of work done may be interesting components, true impact comes from focusing on impacts, adoption and predictors for benefit realization.
Executives and stakeholders are not just interested in receiving progress updates; they seek insights into the likelihood of initiative success and the potential risks that may impede desired outcomes. These risks extend beyond project timelines and budget constraints to encompass broader business implications such as performance impacts, capacity constraints, prioritization effectiveness, and the sustainability of behavioural change.
Impacts of change:
Quantifying and visualising impacts are not new to change practitioners. The key is how the data is presented over time. A lot of change practitioners would settle with a standard heatmap based on personal ratings. This does not deliver much value as the data cannot be easily substantiated by evidence (since it is more of a finger in the air estimation). Standard heatmaps also are too high level and does not really support key decision making.
Decision making requires specific data points such as:
Change saturation or change tolerance levels (these levels need to be substantiated based on business indicator reference to justify the levels, and not be someone’s personal opinion)
What division, team, role and which week the saturation points are forecasted
Corresponding data on what initiatives, and their respective impact activities that contribute to the saturation risk, and therefore proposed options
A key part of representing change impacts should not just be at an operational level, which is more concerned about capacity and bandwidth. Impact should also be tied to strategic levers, portfolio types, benefit types and readiness.
Predictive Indicators for Success:
To create impactful change management reports, organizations must incorporate predictive indicators that go beyond change volume and risk assessment. These indicators should provide insights into business performance, strategy achievement, and the realization of intended benefits.
These are some of the ways you can incorporate predictive indicators:
Forecast lines. With sufficient data you can forecast such as impact or capacity levels (which may be seasonal), or even readiness levels across the initiative lifecycle historically across initiatives.
The types of factors that can be included as predictive indicators can include readiness. It could be that readiness levels only get lifted just before go live or at go live. Adoption levels can also be forecasted if you have trend data across initiatives
Change tolerance levels across different parts of the business can also be seen as a predictive way of forecasting how much capacity there is for change beyond which saturation may be a key risk
Adoption and Behaviour Tracking:
Central to successful change management is the adoption and sustained implementation of new processes or technologies. Tracking adoption rates, user engagement, and behavioural changes are crucial indicators of initiative success. However, it’s essential to strike a balance between capturing relevant metrics and overwhelming stakeholders with unnecessary data.
Capturing behaviour change data can be key for larger initiatives or transformations. Behavioural change can be central in a range of changes such as customer centricity, efficiency, team collaboration or effectiveness. Measuring key behaviour changes that drive the initiative outcome the most is critical. For example, having effective conversations with customers to improve customer experience is a behaviour that can be rated, tracked and reported. Depending on the change, there may also be system features that can aid the tracking of these behaviours.
Effective change management goes hand in hand with strategic alignment, strategic goals, and necessary resources for strategic objectives. Reports should assess how initiatives contribute to overarching business objectives and whether they align with the rest of the organization’s strategic direction in the first place. Business leaders can utilize metrics related to revenue growth, cost savings, customer satisfaction, and employee productivity to provide valuable insights into the impact of change initiatives on business performance.
You can also link your change impacts to each strategic lever. In this way you can visually show the size of the impact per strategic lever. This will give your executives a way to examine whether the right level of impacts in the right areas of business are planned as a part of the course of each strategic lever.
The other angle is to visually show the pace of change against the strategic levers. Are certain key initiatives being driven at the right pace at the right time? Will the velocity of change exceed the ability of the business to absorb the changes? Or is the velocity not sufficiently meeting leadership expectations?
Benefit Realization:
Ultimately, the success of change initiatives is measured by their ability to deliver tangible benefits and assess the impact of the change. Change management reports should include key performance indicators (KPIs) and metrics that track the progress of change initiatives and the realization of expected benefits, whether they are financial gains, process efficiencies, or competitive advantages. By monitoring benefit realization, organizations can course-correct as needed and ensure that investments in change deliver the intended outcomes.
A key responsibility for change is to focus on those foreward looking measures that predict eventual benefit realisation, including readiness, adoption, engagement and behaviour change. Be sure to link these specifically to high benefit initiatives to provide strategic oversight.
Balancing Complexity and Clarity:
While incorporating a diverse range of metrics is essential for comprehensive reporting, it’s equally important to maintain clarity and focus. Reports should be structured in a way that highlights key insights and trends without overwhelming stakeholders with excessive detail. Visualizations such as charts, graphs, and dashboards can help distill complex data into actionable insights, facilitating informed decision-making at all levels of the organization.
All aspects of chart and dashboard designs are critical. These range from colour scheme chosen, number of charts, commentary, titles, legends, sequencing of charts, and type of charts chosen all act to either contribute to simplicity and clarity or complexity and confusion. Your narrative as you talk through the charts also plays a key role in building the story-line, and simplifying the key messages and actions you would like to impart to the audience.
Charts and dashboards tell a story and in presenting them you should always incorporate any actions required from the audience. If this is not done then it will always remain a FYI. FYI content will be deemed lower in the value curve over time and your stakeholders will lose interest. Instead, you should work on crafting a continual story that ebbs and flows. The following are key questions you should be asking when crafting you ongoing charts and dashboards:
Is there an emerging risk or opportunity that warrants specific focus for this month?
How are we tracking the effectiveness of stakeholder actions through data? This feedback loop is critical and gives your stakeholders a reference point for their own effectiveness
Is your data-based story uni-dimensional? Are there other dimensions beyond what you have been presenting that stakeholder should be aware of?
Are you giving stakeholders what they are most interested in? Whether it be strategic success progress, or benefit realisation?
Are you presenting change data in a holistic way in terms of how the business is run? Vs. just focused on standard change management function-specific metrics such as training sessions, or number of workshops completed?
Enterprise change management reporting is a critical tool for navigating the complexities of organizational change. By focusing on predictive indicators, including adoption and behavior tracking, business performance alignment, and benefit realization, organizations can unlock the full potential of their change management initiatives. However, achieving impactful reporting requires a careful balance between complexity and clarity, ensuring that stakeholders receive actionable insights without being inundated with unnecessary information. Ultimately, by harnessing the power of enterprise change management reporting, organizations can drive successful outcomes and thrive in an ever-evolving business landscape.
To find out more about enterprise change management reporting leveraging digital automation and analytics chat to us here.
