The role of change managers has been left out of the various agile methodologies. This is even though most fully acknowledge the importance of change management in the success of initiatives. Does this mean that the agile teams should and can take on the role of change managers? While most of you reading this article may have change practitioners in the organisations, there are plenty of organisations that run agile teams without change managers in the team.
Is it that in agile environments, change management responsibilities are distributed across team members rather than centralised in a single role? After all the agile team is self-organising and has shared accountability?
For organisations that do not have change managers in agile teams, they are still able to deliver valuable and continuous changes. The difference is in how effective the agile team is in delivering a solution where:
A range of stakeholders are continuously engaged effectively and therefore have high levels of readiness
Stakeholders’ readiness for the pace and design of agile is taken into account and various education/engagement sessions are designed as required
They’re able to identify the various behavioural changes required in fully adopting the change
Stakeholders continuously track and reinforce adoption
The team is aware of the change landscape of impacted stakeholders and can work with them respectively to design and deliver in a way that maximises adoption in a targeted way
It is quite difficult for a small agile team to have all these skillsets. You can equally place the same argument for Business Analysts. Even if the team does not have this role, they could equally undertake a lot of the tasks that a Business Analyst would typically undertake in an agile project, however, maybe not at the same level of professionalism and rigor.
In a small agile team of cross-functional specialists, by design each member is a specialist in his/her functional domain, whether it is testing, software development, operations, etc. It would be rare for a domain specialist to have such a breadth of skillsets to include a range of change management skills. Of course, this is not impossible, but difficult for a team to possess.
An agile team is by design focused on delivering. By design, the agile team is laser-focused on its iteration work and delivering to the schedule at the right quality. It does not have a lot of capacity to devote itself to working with a wide range of stakeholders as a result. The change manager, on the other hand, is by design focused on the world of the stakeholders as well as what the agile team is delivering and designing a series of steps for the changes to take place or a people and organisational perspective.
Moreover, beyond project change management skills, organisations that have a myriad of self-organising agile teams require greater air-traffic control at a portfolio and enterprise level. Whilst this may be fulfilled from a portfolio management perspective, attention should also be paid to change portfolio management. Within a fast-paced change environment, the capacity stakeholders across the organisation have for the changes, and the overall prioritisation and sequencing for these changes are paramount.
Without this, changes may fall off the radar, superseded by other competing changes delivered by other agile teams. Alternatively, change saturation fatigue may be a result. In fact, there is increasing evidence that this is prevalent across organisations. Stakeholders’ capacity for change is limited and must be managed effectively to ensure the right changes are adopted.
If change management so critical to agile changes let’s delve into the essential role that change managers play within agile teams, breaking down their contributions across the four typical phases of an agile initiative: Define, Build, Test, and Deploy.
Define Phase
During the Define phase, agile teams lay the groundwork for the project by identifying objectives, scope, and initial requirements. For change managers, this phase is critical for assessing the scope and complexity of the change and determining the necessary resources and support structures.
Key Activities for Change Managers in the Define Phase:
1. Assessing Change Size and Complexity: Change managers evaluate the magnitude of the change and its potential impact on various parts of the organization. This assessment helps in tailoring change management strategies to address specific needs.
2. Resource Planning: Identifying the required business and change support resources is essential. This includes assembling a team of change champions, communication specialists, and trainers who will help facilitate the change.
3. Strategic Planning: Developing a comprehensive plan that outlines key activities and tactics to engage stakeholders and drive successful change. This plan acts as a roadmap for the entire change management process.
Build Phase
In the Build phase, agile teams start developing the solution. Change managers intensify their efforts to understand the potential impacts of the change and begin engaging stakeholders.
Key Activities for Change Managers in the Build Phase:
1. Detailed Stakeholder Assessments: Conducting thorough assessments to identify how different stakeholders will be affected by the change. Understanding these impacts is crucial for tailoring communication and training efforts.
2. Initiating Stakeholder Engagement: Early engagement with stakeholders to communicate the vision, goals, and expected outcomes of the change. This engagement helps in building awareness and buy-in from the outset.
3. Scenario Planning: Since the exact nature of the change may not be fully defined, change managers work with various scenarios to anticipate potential challenges and opportunities. This flexibility allows for adaptive communication and engagement strategies.
Test Phase
The Test phase is where agile teams validate the solution through testing and feedback. For change managers, this phase is pivotal for ensuring stakeholders are prepared for the upcoming changes.
Key Activities for Change Managers in the Test Phase:
1. Collaborating on Testing Processes: Working closely with agile teams to determine how stakeholders can be involved in testing. This may include business testers, change champions, or end-users who provide valuable feedback.
2. Designing Communication Content and Learning Interventions: Developing and rolling out communication materials and training programs to prepare stakeholders for the change. These interventions are tailored based on feedback from testing.
3. Engaging Stakeholders Through Various Channels: Utilizing demos, team briefings, and other engagement channels to keep stakeholders informed and involved throughout the testing process.
Deploy Phase
The Deploy phase marks the transition of the solution into the live environment. Change managers play a crucial role in ensuring a smooth transition and full adoption of the change.
Key Activities for Change Managers in the Deploy Phase:
1. Ensuring Readiness: Before deployment, change managers gather evidence that stakeholders are ready for the change. This involves assessing training completion, communication effectiveness, and overall preparedness.
2. Executing Engagement Strategies: During deployment, change managers leverage various engagement channels to support the transition. This includes continued communication, support hotlines, and face-to-face interactions to address any concerns.
3. Monitoring and Feedback: Establishing performance metrics to monitor the adoption and effectiveness of the change. Feedback is collected and analyzed to make necessary adjustments and integrate the change into business-as-usual operations.
Key Differences in Change Management for Agile Teams
While the core principles of change management remain consistent, their application within agile teams introduces unique challenges and opportunities. Here are some key differences:
Proactive Integration in Cross-Functional Teams
Change managers actively contribute to the progress of agile teams by embedding themselves within the cross-functional team structure. This close collaboration ensures that change management activities are aligned with the development process, allowing for more effective and timely interventions.
Flexibility and Adaptation
In agile environments, the content and nature of changes may evolve throughout the project lifecycle. Change managers must remain flexible, working with scenarios and adaptable communication strategies to respond to shifting requirements and stakeholder needs.
Continuous Feedback and Engagement
Ongoing stakeholder engagement and continuous feedback are cornerstones of effective change management in agile teams. Regular check-ins, feedback loops, and open communication channels help to identify and address concerns early, ensuring smoother transitions and higher adoption rates.
Iterative Planning and Adjustment
The iterative nature of agile projects necessitates continuous review and adjustment of change management plans. Change managers must be prepared to tweak strategies, update communication materials, and refine training programs based on real-time feedback and evolving project dynamics.
Practical Tips for Change Managers in Agile Teams
1. Embed Yourself in the Team: Become an integral part of the agile team to gain a deeper understanding of the project dynamics and build strong relationships with team members.
2. Embrace Flexibility: Be prepared to pivot and adapt your change management strategies as the project evolves. Flexibility is key to staying relevant and effective. Come up with scenarios such as communication materials and engagement tactics as needed.
3. Drive Proactive Open Communication: Create an environment where stakeholders feel comfortable sharing feedback and concerns. This openness will help you address issues promptly and maintain trust. Note that stakeholders may need learning interventions to truly understand and adjust to agile ways of working.
4. Leverage Data and Metrics: Use data and performance metrics to monitor the effectiveness of your change management efforts. Data does not just apply to the rest of the agile team. Change management data is no less valuable. This will help you make informed decisions and demonstrate the value of your work. To read more about how to measure change check out our practical guide here.
5. Continuous Stakeholder Engagement: Engage with stakeholders early and often. Building strong relationships and maintaining regular communication will increase the likelihood of successful change adoption.
6. Understand the Change Landscape: Since the change manager’s role is to adopt a people lens, it is critical to see from the impacted stakeholder’s perspective the range of changes they are or will be going through. Change that is designed in a vacuum will not be successful.
Change managers play a pivotal role in the success of agile teams, ensuring that changes are effectively adopted and integrated into the organization. By understanding the unique dynamics of agile projects and adopting flexible, proactive, and iterative approaches, change managers can significantly enhance the readiness and adoption of changes. Their efforts not only support the agile team but also drive the overall success of the organization in navigating an increasingly intense landscape of changes.
As the global landscape continues to evolve, so too does the field of change management. The year 2024 promises a shift in the way organizations approach change, driven by a combination of economic factors, continued technological advancements, and the ever-increasing need for adaptability. In this article, we explore the background factors influencing the upcoming changes, and delve into seven key predictions that are set to reshape the realm of change management in the coming year.
Background
Inflation Continue to Drop: A Ray of Economic Hope
One of the pivotal factors shaping the economic landscape in 2024 is the anticipated drop in inflation. After grappling with economic uncertainties, organizations can breathe a sigh of relief as the pressure from rising costs eases. This economic respite paves the way for strategic investments and initiatives, creating a conducive environment for change.
Avoiding Recession: Building Resilience Through Change
The specter of recession has loomed large in recent years, casting a shadow on organizational stability. However, as we step into 2024, the concerted efforts to avoid recession is forecasted to have paid off. Organizations have become more resilient, honing their ability to weather economic storms through strategic change initiatives. This backdrop sets the stage for a transformative year in change management.
Key Predictions
Agile Change as Business as Usual
In 2024, the concept of Agile Change is no longer a mere ‘work in progress’ but rather an integral part of Business as Usual (BAU). Organizations have recognized the need for agility in the face of rapid change, and Agile change methodologies have transitioned from experimental to foundational. This shift represents a change in mindset, emphasizing iterative processes, collaboration, and responsiveness to evolving circumstances. After more than 10 years of agile project methodology in the market place, agile change practices are starting to become ‘the norm’.
The Rise of Adaptive/Hybrid Change Models
Building on the previous point, agility applies beyond at an ‘intra-methodology’ perspective, but also how change approaches and methodologies need to be mixed and matched to work.
The increasing pace of change demands a more flexible approach from change practitioners. The dichotomy between structure and flexibility, innovation and process-focused strategies, gives rise to adaptive and hybrid change models. The emergence of terms like “wagile” (a fusion of waterfall and agile) underscores the need for a balanced approach that combines the best of both worlds. Organizations must strike a delicate balance between structure and flexibility to navigate the complexity of modern change initiatives.
For example, in regulated business functions there may need to be quite rigid planning of exactly when the changes must take place as well as the level of consultation and engagement required. However, the actual design of different engagement, positioning and employee involvement strategies may be tested in an iterative way.
Expanding Skill Sets for Change Practitioners
To meet business needs change practitioners will need to have a broader range of skills beyond ‘people skills’. In 2024, the demand for change professionals with a broader skill set encompassing strategic thinking, digital/data literacy, and business acumen will continue to be on the rise. As change initiatives become more complex, practitioners must equip themselves with multifaceted skills to address the diverse challenges that emerge during the change process.
For example, stakeholders are increasingly looking for data for reporting purposes to get a clearer sense of how changes are tracking. Beyond sentiments and opinions, stakeholders are looking for adoption indicators as well as precise indications of the nature of impacts across the employee population.
The Ascendance of Change Portfolio Management
Change portfolio management will continue to gain increasing visibility and importance in 2024. Organizations are recognizing the need to manage change initiatives collectively, aligning them with strategic objectives. The holistic oversight provided by change portfolio management enables organizations to prioritize, monitor, and evaluate change initiatives in a comprehensive manner, ensuring that resources are optimally allocated for maximum impact.
Whilst stakeholders may not be clear of the differences between transformation, portfolio management and change portfolio management, they are clearer of the benefits required in managing people impacts, against the need to maximise business performance and change adoption.
Leveraging Change Data for Informed Decision-Making
In the evolving landscape of change management, data is no longer just a nice-to-have; it’s a necessity. In 2024, the norm becomes leveraging change data to make informed decisions. Organizations recognize the value of data analytics in understanding the impact of change, identifying patterns, and proactively addressing challenges. This data-driven approach enhances the efficacy of change initiatives and provides a foundation for continuous improvement.
It is no longer that the expectation for data-led decision making rests in project functions such as technical development, business analysis, testing and user-experience. Change management teams are also expected to demonstrate the impact of their work through data.
Increasing Use of Software in Change Implementation
The leverage of software in change implementation should see an uptick in 2024, along with general increase in software usage rates in organisations. Organizations are leveraging technology to streamline and enhance various aspects of the change management process. From change project management tools, change measurement platforms, as well as change portfolio management tools the role of software can accelerate the pace of change initiatives and supports the realisation of benefits.
AI for Change: From Wait-and-See to Full Adoption
Artificial Intelligence (AI) for change management is no longer a ‘wait-and-see’ proposition; it’s a reality in 2024. In 2023 a lot of users have sat on the fence as others argue about the risks in using AI and data security. The launch of Microsoft Co-pilot and the continued adoption of Chat GPT 4 signal a paradigm shift in how organizations approach AI. Users will over time be used to asking a chat bot, using prompts to form analysis and other AI features to augment their work. Advanced AI change tools can also assist in decision-making, predictive analytics, and even virtual facilitation, revolutionizing the efficiency and effectiveness of change processes.
In addition, there will be significant interest in change management tools that have incorporated AI features, from data and trend analysis, risk analysis to recommendations on change approaches.
As organizations navigate the complexities of 2024, change management emerges as a critical linchpin for success. The predictions outlined in this article reflect an emerging shift in the approach to managing change, from the integration of Agile methodologies to the widespread adoption of AI. Change practitioners must equip themselves with a versatile skill set to thrive in this dynamic environment, where strategic thinking, digital literacy, and adaptability are paramount. As we stand on the cusp of a transformative year, organizations that embrace these predictions are poised not only to weather the winds of change but to harness them for sustained success.
Delivering constant changes is a requirement in implementing agile change management. With each iteration, a change is being designed and released as a part of ongoing agile development and project implementation. However, there is little mention in change management literature of how to go about delivering change constantly and be able to achieve optimum change adoption.
Continuous delivery pipeline
The concept of a ‘continuous delivery pipeline’ is a core part of the agile methodology. It refers to having a structured pipeline of continuous changes being released as required by the organisation. The pipeline contains a set of features and changes to be worked on, and the resulting prioritised changes are released when and as needed.
The three components of a continuous delivery pipeline that forms an agile release train include:
Continuous exploration – This is about defining and scoping what needs to be built using human centred design approaches to design the problem that needs to be solved from the user perspective
Continuous integration – This step involves taking those prioritised features from the backlog and investigating further to understand what development work is required to turn them into solutions for the user.
Continuous deployment – This is about turning the completed changes from the staging environment into production, meaning the live product that is ready to be used by the user. After the technical part of the solution is ready to be released, the business then determines when is a good time for this release to go ahead.
The ‘technical side’ of the agile team is fairly well defined in terms of the roles and responsibilities of each member, including project manager, developer, QA/testing, business analyst, business owner, etc. However, the role of the change manager is much less defined and black and white. This does not mean that there is no role for the change manager though. It just means that the agile literature has not well defined the details for the role of the change manager in an agile team. ‘Agile change management’ still has some work to do to make itself better known to other agile team members.
So how does the change manager get ready to deliver a series of constant changes?
Delivering a series of constant changes is no easy feat. The main issue is that most businesses are not designed to face multiple changes, and nor are they designed to face a series of continual changes either.
Change approaches are primarily written for working on one change at a time, and not in a setting where there are continual releases of changes going on. On the other hand, how many organisations do you know that are only facing one change? Or that only deals with one change within a month? This type of stable change environment may have been the norm years ago when the business environment was much more predictable and stable. Hence, using a waterfall project approach was appropriate at the time. Fast-forwarding to the 2020s most organisations are juggling with constant and multiple changes as the norm.
1. Derive a picture of the changes within the continuous delivery pipeline.
Deriving a clear picture of what changes look like within a project is critical. Without this, you will not be able to clearly communicate to your stakeholders what changes are coming down the pipeline.
To create this picture, use a human-centred approach and illustrate what the user will go through throughout the change journey. This is similar to a user journey map. However, a change-focused picture goes beyond just what the user will be going through. It also includes not just person-based changes, but also process, policy, system, governance, reporting and other changes. Outlining these changes will complete the whole picture of what each change release may look like.
A key problem in creating a picture of the changes early on is that the project team may not even know what the solution looks like. And without particular details of every change release and solution design, it may be hard to create this picture.
The recommended approach is to focus on what the outcome could look like versus focusing on various technical or process solutions. This means you may even need to make particular assumptions in defining what these changes look like. For example:
Release 1: Ability to turn recorded customer conversations into text. With this feature, there will be new risk and privacy processes and governance be put in place in the monitoring and storage of customer data.
Release 2: Ability to search for customer conversation history and flag follow up actions required. Specialist roles may be required to audit customer conversation text. Behaviour shifts in proactively checking on customer history and knowing what to look for in trends is critical.
Release 3: Ability to use analytics to predict customer turnover and use this to minimise customer turnover. Significant capability uplift is required to ensure that consultants are able to know how to use analytics to help minimise customer turnover. Analytics capability uplift is also required at operations management, supervisor and team leader levels.
2. Map holistic stakeholder impacts.
In order to implement constant ongoing changes, it is critical to understand holistically what the stakeholders are undergoing across all types of changes and other BAU impacts. Without taking these into account it is not possible to truly understand the capacity of stakeholders and when changes will best ‘stick’ when released.
Some of the items that should be inventoried and mapped include:
Impacts from the current project that you are working on
Other project impacts that affect the stakeholder at the same time as your project, including any benefit realization periods post project implementation
BAU-led initiatives that could include business improvement or quality, and may not classified as ‘funded projects’ per se
Key high work volume periods such as end of financial year, holiday season, etc.
Audits, planning or reviews where additional work volumes are forecasted
It does take investment and effort to collect all these types of data and most change managers do not bother to do this. However, it is not possible to implement a successful change when you do not understand what other changes or work priorities your stakeholders are undergoing during the change process.
It is also important to note that this type of impact data can change constantly and once the data is collected it needs to be verified on a timely basis with any changes and updates reflected over time. Doing this activity manually can be quite cumbersome so we advise using digital tools such as The Change Compass.
The collected data on what stakeholders are undergoing can be significantly valuable. Often stakeholders themselves have not undertaken this exercise to truly understand the change journeys and work priorities added together holistically. They may be surprised by the picture you are presenting to them. At the minimum, they will value this since it shows that you have a deep understanding of what they will be going through and therefore create more stakeholder confidence.
Examples of data visualisation from The Change Compass
3. Sizing and categorising the impacts of changes
After getting a clear picture of holistic change environment that the stakeholders will be undergoing the next step is to analyse the impacts from your project. In analysing the change impacts you should be ascertaining the nature of these change impacts including:
Size of the impact
How long the impacts will last
How much time these impacts translate to
Types of these impacts (e.g. people, process, system, customer, etc.)
To whom the impacts will be on
Quantitatively sizing your impacts makes them concrete and easily understood. Armed with this information you are able to examine to what extent the planned releases are the right ‘size’ for the impacted stakeholder groups. This is another critical part of agile change management. In determining this, the following stakeholder factors are critical:
Capacity bandwidth
Potential overlaps across various impacts either within the same or with other projects or initiatives
Change maturity level and experience with similar changes in the past
Leadership support and other change reinforcement mechanisms
Overall change readiness
Engagement level with the particular change initiative
When you have considered all of these factors you are ready to engage with your project manager, the PMO, and business representatives to assess to what extent the roadmap laid out is effective and will work to maximise the targeted initiative benefits.
4. Business operations routines
Now you understand clearly the change environment of your impacted stakeholders, various changes within yours’ and other initiatives, and the categories of the various change impacts. The next step is to clarify to what extent your impacted business units have the right operational process to receive ongoing changes. This is often a neglected part of agile change management.
More change mature business units have over time developed the right routines and processes to absorb changes, especially ongoing ones. What are some of these?
Effective engagement processes. Engagement processes are not just one-way communication channels. Having effective communications channels such as newsletters and town halls are a minimum for employees to hear about what is coming down the pipeline. Engagement processes include such as effectively choreographed Yammer channels, skip-level meetings (where managers meet with employees 2 levels down), focus group sessions with a small group of select employees, and effective team meetings where information is passed both up and down the chain of command
Effective learning processes. Effective learning processes at a business unit level includes business operations routines whereby employees have individual development plans (from which training plans can be incorporated), ongoing monitoring of development tracking against targets (e.g. completion rates), virtual learning processes (e.g. employee familiarity with virtual ways of self-initiated learning)
Change champion network. Most change champion networks are project-based and therefore have a limited shelf-life. This means that business change champions have a limited time to learn and develop as effective change champions. They also have limited time to practice and experience what it is like to lead and support change. A better design for business units undergoing ongoing changes is to have business unit based change champions that can support a myriad of changes across the board. This flexes their capability. Also, with constant exposure to changes over time, they are able to continuously develop and become better change champions. Organisations that have done this well, have positioned this as a ‘talent pool’ for frontline employees seeking to grow into other challenging roles.
Benefit realisation processes. Tracking and reinforcing benefit realisation is one of the most critical ingredients for success in the impacted business unit. Usually a month after go-live, the project would have already wrapped up and the business is left to continue the rest of the change journey and achieve the targeted benefits. To do this the business unit needs to have clear benefit realisation tracking and reinforcing mechanisms, involving Finance and business leaders. There needs to be constant oversight of how the benefit tracking is trending and leader discussions on resolving any obstacles and providing adequate managerial support to drive the benefit realisation process.
If your impacted business unit lacks one or more of these ingredients, it is critical that you work on this upfront. Highlight to business leaders the risk of not having these ingredients in place within the business. These processes may take significant time and investment to build up. Therefore, factor in the time required to develop these. Often, within the challenges of agile changes, these are left until the end, by which time it is too late to try and establish quickly to support the identified project changes.
The increasing pressure to change and evolve continues to challenge the very existence and design of every organisation. After waves of change and disruption from industry competition, technology evolvements, customer preferences, surge in commodity prices, and Covid, change is, more than ever, a constant. To meet with this rapid and increased intensity of change, organisations are resorting to agile ways of implementing change management to keep up.
Agile ways of implementing change often times mean that the outcome may be reached faster by team members, and sometimes with fewer resources than previously. With these promises, there are very few organisations that are not jumping along the agile bandwagon.
So what are the challenges of using agile change management?
1. Agile change may not suit every change scenario
Agile ways of change management may be great when we are developing a new product, a technical solution, a new process or a new way of working. However, not every change scenario. If the change setting requires strict adherence to complex regulations and standards, significant documentation, testing and quality assurance, full agile may not be the most suitable. Pharmaceutical companies would not use a pure agile approach in developing new drugs simply due to the level of regulatory and industry standards required to be met in the process.
However, this does not mean aspects of agile practices may not be incorporated alongside traditional approaches. For example, pharmaceutical companies have been incorporating practices of involving customers in product design, customer collaboration, and marketing communication to enhance customer satisfaction. The trick is to balance those agile aspects which would benefit the overall solution and outcome, versus others that may be less applicable due to organisational and industry challenges.
On the other hand, if the project is concerned with developing changes to meet a new government regulatory requirement for customer product disclosure, an agile change approach may be more suitable. Change iterations can be designed to form the solution required to both meet regulatory requirements and not negatively impact customer experience.
2. There are significant capability requirements in implementing agile changes
Implementing agile changes does not just mean using agile frameworks and techniques in the project team. Every team involved needs to ensure effective communication and transparent communication, including regular team interactions, to build up agile capabilities. This includes not just the technical teams, quality and testing teams, but also business stakeholders, and depending on the change, customer advisory teams as well.
Project teams may be used to agile methods and techniques after several projects. However, these may be foreign for business stakeholders, especially those accustomed to traditional project management environments. Sufficient education and capability building to tackle common challenges may be required in impacted businesses to undergo the change process. This is because without this experience, the impacted businesses may not sufficiently buy-in to how the change was designed and implemented. Moreover, without adopting agile practices, the impacted business teams may not be able to adopt the changes at the rate expected in agile environments, which could hinder a smooth transition to effective agile methodologies.
3. The agile methodology has not clearly specified change management elements
Agile project management methodology clearly lays out the roles of the various members of the agile team, including the project manager, business owner, quality and testing, developer, etc. However, a big hole exists for effective change management, emphasizing the crucial role that change managers need to play. The clear role for change management has been left out. For example, methodology and training providers such as Scaled Agile. In a seemingly detailed and comprehensive treatment of all parts of agile methodology, the specific details of the role for change managers are not mentioned anywhere.
To tackle this big gap, there are various attempts to try and close this gap such as Jason Little’s Agile Change Management approach that is possibly less comprehensive than those best practices detailed by the Scaled Agile Framework for the enterprise level.
Why is it that the role of the change manager is clearly omitted? It is not that the role of change manager is becoming obsolete. The increasing popularity of agile is matched by the increasing demand for change management professionals. There has been a consistent growth in the recruitment for change professionals year after year. It could only be that perhaps those in charge of documenting agile methodology don’t have a background in change management and subsequently have not ventured to detail any requirements within the methodology.
Imagine a world where change professionals won’t need to tip-toe and educate others about how their roles fit within an agile setting. Given the importance of change management is it not a gap that cannot continue forward? Perhaps we can garner the change community to drive this through in the 2020s?
4. Oversight of multiple agile changes is more critical than ever
One of the key challenges of using an agile approach is that often the end change outcome or the solution of the change is not clearly known at the commencement. With each iterative development, agile changes become more and more defined, and the project objectives may also evolve. Or at times, the solution may continue to evolve and pilot as required according to project requirements.
What this means is that at any one-time business stakeholders are dealing with multiple projects and their project progress that are constantly evolving. The impact of those projects may or may not be known depending on the development of the specific agile iterations. This could make it a nightmare to plan and get ready for multiple changes from a business unit perspective.
The solution is to develop oversight of the entire group of change initiatives. With constant oversight, the business is much more capable of preparing for change overall. And with the shifting iterations of agile across initiatives, the picture continues to evolve so that the business can keep a pulse on the changing nature of change. This includes not just the volume of impacts, but types of changes, role impacts, timing, change pace, readiness, and fostering a culture of continuous improvement, including regular feedback loops, etc. Utilise digital change management solutions to support your stakeholders as they continue down the agile change journey.
How will you support your business stakeholders as they charter through the ever-increasing environment of change and disruption? What digital tools are you adopting within this digital world to get ready for increasingly agile changes? Just like the agile principle of including and integrating multiple disciplines to promote collaboration, leveraging digital tools to aid change readiness and collaboration is key to future change outcome success.
To read more about agile change management articles visit our Knowledge Centre where we have articles such as:
Change management has transformed dramatically over decades, evolving from reactive crisis responses to sophisticated, data-driven strategies that predict and shape organizational transformation. Understanding this evolution equips practitioners with insights to navigate modern complexities like digital acceleration, regulatory pressures, and workforce expectations.
This guide traces key milestones in change management development, examines the shift toward strategic data integration, and explores emerging AI-driven capabilities that redefine practitioner roles. Practitioners gain practical frameworks to apply these insights in today’s fast-paced environments.
How Has Change Management Evolved Over Time?
Change management began as structured responses to organizational disruption but matured into proactive disciplines leveraging data and technology. Early approaches focused on resistance management; modern practices emphasize prediction, measurement, and continuous adaptation.
Key evolutionary phases include:
1950s-1970s: Foundations in Behavioural Science Kurt Lewin’s three-stage model (unfreeze-change-refreeze) established foundational principles. Focus remained on human psychology and overcoming resistance through communication.
1980s-1990s: Structured Frameworks Emerge John Kotter’s 8-step process and Prosci’s ADKAR model provided systematic approaches. Emphasis shifted to leadership alignment and stakeholder engagement.
2000s: Enterprise Integration Change management embedded within project management methodologies like PMI and Agile. Organizations recognized change as a distinct discipline requiring dedicated resources.
2010s-Present: Data and Analytics Integration Rise of change portfolio management and adoption metrics tracking. Practitioners began measuring outcomes beyond activities, using dashboards for real-time insights.
This progression reflects growing recognition that successful change requires both human-centered approaches and rigorous measurement.
What Drove the Shift to Strategic Change Management?
Several forces accelerated change management’s maturation:
Digital Transformation Pressures
Rapid technology adoption created simultaneous change waves across organizations. Traditional sequential change approaches proved inadequate for multi-project environments.
Regulatory and Compliance Demands
Increasing scrutiny required demonstrable evidence of change adoption and risk mitigation, pushing practitioners toward measurable outcomes.
Workforce Expectations
Millennial and Gen Z entrants demanded transparency, purpose alignment, and visible progress tracking in change initiatives.
Portfolio Complexity
Organizations managing 10+ concurrent changes needed centralized oversight, leading to change portfolio management practices.
Measurement Maturity
Advancements in HR analytics and adoption metrics enabled practitioners to demonstrate ROI and secure executive support.
These pressures transformed change management from a support function to a strategic capability directly influencing business outcomes.
The Rise of Data-Driven Change Management
Modern change management integrates operational data, adoption metrics, and predictive analytics to guide decision-making.
Strategic Change Data Management
Organizations now maintain centralized repositories tracking change saturation, adoption rates, and portfolio capacity. This enables executives to balance change demands against organizational readiness.
Data reveals change overlaps, capacity constraints, and high-risk initiatives. Practitioners allocate resources strategically rather than reactively.
Predictive Capacity Planning
Analytics forecast change bandwidth by department and role, preventing saturation and burnout during transformation waves.
This data foundation positions change management as a value-creating function rather than cost centre.
Implementation Frameworks and Best Practices in Modern Change Management
With the evolution of change management into a data-driven discipline, implementation frameworks have also advanced to incorporate strategic alignment, measurement, and agility.
Established Frameworks Adapted for Today’s Environment
Kotter’s 8-Step Process
This enduring framework continues to provide a roadmap for leading change, emphasising urgency creation, coalition building, vision communication, and consolidation of gains. Modern adaptations integrate data points at each step to monitor engagement and effectiveness.
Prosci ADKAR Model
The ADKAR model—Awareness, Desire, Knowledge, Ability, Reinforcement—remains influential for individual change adoption. Data from assessments aligned to each dimension now inform targeted interventions.
Agile Change Management
Agile methodologies bring iterative feedback loops and rapid adaptation, suited for fluid business environments. Incorporating continuous data collection and analytics allows agile teams to pivot change strategies responsively.
Emerging Best Practices
Integrate Change Management Early in Project Lifecycles: Position change activities alongside project planning for seamless alignment and impact maximisation.
Embed Data Streams for Real-Time Insights: Utilise adoption metrics, sentiment analysis, and feedback channels to guide decision-making dynamically.
Foster Cross-Functional Collaboration: Engage stakeholders and change agents across departments to build collective ownership.
Leverage Technology for Automation: Automate repetitive change management tasks such as communications, survey distribution, and reporting, freeing capacity for strategic priorities.
Prioritise Employee Experience: Tailor change approaches to diverse workforce needs, using data-driven personas and segmentation.
The Role of AI and Automation in Advancing Change Management
Artificial intelligence and automation are set to redefine how change practitioners operate, transforming strategic decision-making, engagement, and measurement.
AI-Powered Predictive Analytics
By analysing historic change data combined with organisational variables, AI models predict likely resistance points, adoption rates, and saturation thresholds. These insights enable pre-emptive strategies designed to smooth transitions.
Automated Change Interventions
Chatbots and virtual assistants can deliver personalised communications, FAQs, and training modules at scale, maintaining consistent messaging and freeing practitioners’ time for higher-value activities.
Natural Language Processing (NLP) for Sentiment and Feedback Analysis
AI-driven sentiment analysis of employee feedback, surveys, and collaboration platforms identifies emerging issues and morale trends faster than traditional methods.
Intelligent Dashboarding
AI enhances dashboards by correlating disparate data, highlighting risks, and recommending intervention actions. Customisable alerts notify change leaders of critical deviations in real time.
Augmented Decision Support
Machine learning integrates diverse inputs—financial, operational, human factors—to support scenario planning and optimise change portfolios, particularly in complex environments.
Preparing Change Practitioners for the Future
The evolving change landscape requires practitioners to blend traditional soft skills with digital and analytical capabilities. Key skill enhancements include:
Continuous learning mindsets to adapt as technologies evolve.
Institutions and organisations should invest in upskilling programs and knowledge hubs supporting these competencies.
Key Takeaways for Change Practitioners
The evolution of change management offers clear guidance for practitioners navigating today’s complex landscape:
Embrace Data as a Strategic Asset
Shift from activity tracking to outcome measurement. Implement real-time adoption dashboards that correlate behaviours with business results, enabling proactive interventions.
Master Portfolio Management Discipline
Treat change as a finite resource. Establish governance processes to assess saturation, prioritise initiatives, and sequence delivery for maximum organisational capacity.
Build Cross-Functional Change Capabilities
Move beyond siloed project support. Embed change expertise within strategy, digital transformation, and HR functions for integrated execution.
Cultivate Continuous Learning Cultures
Position change practitioners as organisational learning facilitators. Use post-initiative reviews and trend analysis to build institutional knowledge.
Emerging Capabilities for Practitioners
AI-Augmented Decision Making
Leverage predictive models to forecast adoption risks and capacity constraints. Use sentiment analysis across communication channels to detect resistance patterns early.
Automation of Change Operations
Streamline repetitive tasks—status reporting, stakeholder mapping, communication scheduling—freeing capacity for strategic advisory roles.
Advanced Measurement Frameworks
Combine traditional metrics with micro-behaviour tracking and network analysis to understand influence patterns and adoption cascades.
Implementation Roadmap for Practitioners
Phase 1: Assessment and Foundation (0-3 Months)
Conduct change maturity assessment across frameworks and capabilities
Establish baseline adoption metrics for current portfolio
Map organisational change capacity by department and role
Build cross-functional change governance council
Phase 2: Data Integration and Optimisation (3-6 Months)
Deploy centralised change portfolio tracking system
Implement real-time dashboards with automated alerts
Launch pilot AI sentiment analysis on feedback channels
Standardise post-change review processes
Phase 3: Strategic Evolution (6-12 Months)
Embed predictive capacity planning in annual cycles
Scale successful automation across enterprise initiatives
Develop practitioner upskilling academy
Establish external benchmarking partnerships
Frequently Asked Questions (FAQ)
How has change management fundamentally evolved? From reactive resistance management to proactive, data-driven portfolio disciplines that predict capacity and measure sustainable adoption.
What are the most important data capabilities for change practitioners? Real-time adoption tracking, portfolio saturation analysis, predictive capacity modelling, and cross-initiative impact correlation.
How should organisations structure change governance? Cross-functional councils with executive sponsorship, portfolio prioritisation processes, and dedicated measurement functions.
What skills will define future change practitioners? Data analytics proficiency, AI tool fluency, portfolio strategy, systems thinking, and continuous learning facilitation.
Why is change portfolio management mission-critical now? Concurrent digital, regulatory, and cultural transformations overwhelm traditional approaches. Portfolio discipline prevents saturation and maximises ROI.
How do AI capabilities enhance change effectiveness? Predictive risk modelling, automated stakeholder engagement, real-time sentiment tracking, and intelligent resource allocation recommendations.
