Rethinking Change Champions Beyond the Project Lens
For decades, the change champion has been a familiar figure in large-scale transformation projects – the trusted liaison between the change team and the business, responsible for rallying colleagues, answering questions, and providing on-the-ground feedback.
But in most organisations, they are treated as short-term, disposable resources: assembled for a single initiative, tasked with helping during deployment, and then disbanded as soon as the project reaches steady state.
This project-by-project approach misses a critical opportunity.
Increasingly, forward-thinking organisations are moving towards an enterprise change champion model and treating these roles not as temporary assignments, but as a strategic, cross-project capability that sits at the heart of building a more change-resilient workforce.
Why the Traditional Change Champion Model Falls Short
The conventional change champion construct has obvious strengths:
Champions are close to the ground, embedded in business units, and understand local challenges.
They can translate change plans into the everyday realities of their teams.
They give the project team early warning signs about resistance or readiness issues.
However, the limitations are equally apparent:
Short-Term Focus – Once a deployment is complete, project change champions are often released without retaining the capability they’ve built.
Loss of Internal Expertise – Any lessons learned, trust built, and skills acquired fade quickly when champions return to their ‘day jobs’ without a broader mandate.
Fragmentation – Each project recruits, trains, and manages its own champions independently, leading to inconsistent standards and duplicated engagement with the same stakeholders.
Missed Development Opportunities – Some of the most promising leaders remain untapped between projects.
When organisations experience continuous transformation with multiple overlapping initiatives, with varying scopes and impacts, this ad-hoc model leads to change fatigue and diluted influence.
A Step Change: The Enterprise-Wide Change Champion Network
What It Is
Instead of recruiting champions per project, the enterprise model creates a standing network of empowered, skilled employees and first-line managers who are trained, nurtured, and deployed to support any change in any part of the organisation.
They operate at two primary levels:
Employee-level champions – embedded in day-to-day operations, they bring peer credibility and act as the first touchpoint for change comms and readiness checks.
First-line manager champions – supervisory-level influencers who bridge the gap between leadership and frontline teams, actively managing the people side of change.
In addition, division-level representatives coordinate champion activity across their area and connect with the enterprise portfolio of changes. Some may sit in operational planning, HR, or directly in an enterprise change team, depending on organisational structure.
The Case for a Longer Term Champion Network
Change execution is not just about effective rollout – it’s about repeatable, scalable ability to change. The enterprise champion model delivers three key benefits that move the needle:
Sustainable Capability – Skills in influencing without authority, creative engagement, and grassroots communication are retained in the organisation.
Faster Time-to-Adoption – Champions already know the frameworks, templates, and rhythms of engagement, so each new change ramps up quickly.
Talent Pipeline – Champions gain visibility, influencing opportunities, and leadership exposure, making them prime candidates for promotion into leadership, project, or change roles. Many organisations using this model have inadvertently built a ‘leadership incubator’ in the process.
Selecting the Right Champions: Intake Principles
Not every employee is suited to being a champion. The selection criteria are critical to ensuring the network is both high-performing and credible:
Motivation – Champions must see value in playing the role, both intrinsically (desire to help the organisation evolve) and extrinsically (career growth, recognition).
Communication Skills – Ability to translate technical or abstract change messages into plain language for peers.
Coordination and Influence – Capable of corralling colleagues, keeping engagement high, and working across both formal reporting lines and informal networks.
The intake process should feel purposeful. This is not “volunteering” in the casual sense – it’s joining a professional network with enterprise significance.
Beyond Cheerleading: Shaping Change from the Ground Up
Traditional change champions too often become just “posters and cupcakes” – the enthusiastic promoters of a change, but with little voice in how it is planned or measured.
In the enterprise model, champions:
Raise Awareness – in ways that are relevant to their teams and culture, rather than relying on corporate one-size-fits-all messaging.
Sense-Check Readiness – gathering feedback and sentiment before key milestones, providing accurate insight back to project and leadership teams.
Design Local Engagement – creating tailored activities that make the change tangible and exciting.
Co-Own Measurement – participating in tracking adoption and readiness, and linking these to operational performance where relevant.
This measurement element is powerful. If champions see what is changing, when, and how much across the enterprise, they can better pace local adoption and avoid overwhelming their teams.
Now we turn to the how: the design, governance, and development practices that make an enterprise-wide change champion network a strategic business capability — trusted by leaders, respected by peers, and seen as a genuine driver of change adoption and organisational learning.
1. Designing the Enterprise Change Champion Model
A well-performing network of champions doesn’t rely on goodwill alone. It’s a deliberate, resourced capability with defined structure, integration points, and a clear operating rhythm.
a. Network Tiers
The most effective enterprise models feature three interconnected levels:
Local Champions (Employee Level)
Embedded within everyday operations.
Directly influence peers through trust and credibility.
Ensure changes are contextualised for their specific work environment.
First-Line Manager Champions
Serve as change role models for their teams.
Help translate strategic initiatives into operational priorities.
Manage workload balance between BAU and transformation demands.
Divisional / Functional Representatives
Coordinate local champions within their function or geography.
Interface with enterprise-level change, HR, or operational planning teams.
Escalate systemic adoption risks or barriers.
b. Integration with the Enterprise Operating Rhythm
Champions must be integrated into core business cycles, not treated as an “extra thing they do in their spare time”:
Quarterly Business Reviews – Include updates on change readiness and adoption.
Operational Meetings – Reserve time for upcoming change briefings.
Annual Planning – Involve champions in pipeline awareness so they can pace change delivery for their teams.
This ensures the network’s role is embedded, not bolted on.
2. Governance: Balancing Structure with Flexibility
A champion network requires governance to maintain credibility, but too much rigidity can limit creativity and ownership. Senior practitioners should consider:
a. Clear Mandate
Document the network’s remit:
To build and sustain readiness for change across the enterprise.
To surface ground-level issues early.
To contribute to measuring change adoption.
This clarity prevents champions from being used as “free event organisers” rather than strategic enablers.
b. Sponsorship
High-performing networks have active executive sponsorship, ideally within the executive team, ensuring:
Visibility at the top table.
Authority to escalate blockers.
Access to resources.
c. Role Tenure and Rotation
Typical tenure: 18–30 months, with renewal based on performance and availability.
Regular rotation broadens exposure for more employees, refreshes energy in the network, and reduces burnout from continuous change advocacy.
An enterprise network will only be as strong as its learning and development program. Champions need more than “change updates” – they need targeted skill-building.
a. Core Skills Curriculum
Influencing Without Authority – Building informal power and trust networks.
Change Fundamentals – Understanding models, frameworks, and adoption levers.
Storytelling for Change – Shaping narratives that inspire action.
Sentiment Analysis – Gathering and interpreting feedback on readiness and concerns.
Metrics Literacy – Understanding change dashboards and linking people data with performance outcomes.
b. Experiential Development
Shadowing Project Teams – To understand the “engine room” of change delivery.
Rotations Across Divisions – Cross-pollination of experience and approaches.
Facilitating Workshops – Hands-on leadership of engagement activities.
c. Recognition and Career Pathways
If you want the best people to step forward as champions, you need to position it as a career accelerator:
Formal credits in performance reviews.
Priority consideration for emerging leadership or project roles.
Public recognition in forums or internal comms.
4. Linking Champions to Change Metrics: Data as an Engagement Tool
One of the most powerful enablers of an enterprise champion network is visibility of change data– not just for executives, but for the champions themselves.
When champions can see:
The enterprise change portfolio – what’s coming, when, and where.
Impact heatmaps – the degree of change affecting each function.
Adoption trends – progress metrics by region, team, or process.
…they can better inform their local teams, manage change saturation, and proactively address pockets of resistance.
Champion-Led Reporting Loops
Champions provide local sentiment and engagement data back to the change and leadership teams.
This creates two-way measurement, balancing top-down project metrics with authentic ground-level insight.
5. Sustaining Momentum Over Time
Even the most enthusiastic champion cohorts can lose energy without deliberate momentum-building mechanisms. Senior leaders can embed sustainability by:
Regular Cohort Events – Quarterly summits to refresh skills, share success stories, and align on upcoming priorities.
Recognition Rituals – Spotlighting champions who have made significant local impact.
Knowledge Hubs – Digital platforms to share templates, tools, and peer insights.
Graduation Paths – Allowing champions to “graduate” to advanced roles (e.g., mentoring new champions or stepping into change leadership roles).
Proving Impact, Embedding Talent Pipelines, and Cultivating a Change-Agile Culture
Previously we explored the rationale for shifting to an enterprise-wide change champion model and how to design, govern, and develop a high-performing network. Now we close the loop by focusing on how to demonstrate return on investment (ROI), embed the champion network into talent and leadership pipelines, and drive a culture where agility and change readiness are organisational norms.
1. Demonstrating the Strategic Impact and ROI of the Champion Network
Transformation leaders need to show tangible value to maintain investment in the champion model. This requires defining and tracking the right measures across multiple dimensions:
a. Change Adoption Metrics
Speed to Adoption: Time taken for teams to reach defined levels of new process or tool usage.
Adoption Volume: Percentage of the workforce actively using or complying with the change.
Resistance Incidence: Frequency and severity of resistance signals identified via champions.
b. Employee Engagement and Sentiment
Regular pulse surveys co-designed with champions to gauge readiness, concerns, and morale.
Qualitative feedback from champions about barriers and enablers on the ground.
c. Talent Development Outcomes
Promotion and role progression rates of change champions.
Retention of champions compared to peer groups.
Champion participation rates in subsequent change initiatives.
d. Business Performance Linkage
Where possible, correlate change adoption rates with key performance indicators affected by the transformation (e.g., productivity improvement, customer satisfaction, error reduction).
The narrative around these metrics should highlight how the champion network reduces risk, accelerates change, and strengthens leadership pipelines—making it easier to secure ongoing support and resources.
2. Embedding the Champion Network into Talent and Leadership Pipelines
One of the most powerful aspects of an enterprise change champion model is its ability to develop future leaders through hands-on, cross-functional change experience:
a. Career Pathway Integration
Define clear career pathways linking champion roles to leadership, project management, and change leadership positions.
Include champion experience as a valued skill in performance appraisals and promotion criteria.
b. Succession and Rotation Planning
Rotate champions through different business units and change projects to broaden their exposure.
Use the network as a talent pipeline, actively identifying high-potential employees for targeted development.
c. Leadership Sponsorship and Mentorship
Engage senior leaders as sponsors for champions, providing mentorship and visibility on strategic initiatives.
Create mentorship programs pairing seasoned change professionals with champions to accelerate learning.
When treated seriously as a talent development program, the champion network becomes a leadership incubator that benefits the organisation far beyond the immediate change portfolio.
3. Cultivating a Change-Agile Culture through the Champion Model
Beyond skills and metrics, the enterprise champion model shapes an organisation’s cultural DNA by embedding change agility as a norm:
a. Peer Influence and Grassroots Advocacy
Champions serve as trusted peers who normalize change discussions, reducing fear and uncertainty.
Their ongoing active involvement signals to employees that change is continuous and manageable.
b. Building Collective Ownership
Shared responsibility for success is fostered as champions co-own change outcomes with leadership and project teams.
This prevents change being viewed as “something done to us” and instead as “something we drive together.”
c. Transparent Communication and Feedback Loops
Regular updates from champions create a two-way dialogue between employees and leaders.
Transparent sharing of data and progress builds trust and accountability.
d. Resilience and Adaptability
The readiness and skills of champions help the organisation respond dynamically to shifting priorities and emerging challenges.
4. Case Study Insights: Organisations Leading with Enterprise Change Champions
Many organizations have reaped significant benefits from this approach:
A global financial services firm reported a 30% faster adoption rate for technology transformations after establishing an enterprise champion network, alongside measurable improvements in employee engagement during change windows.
A large insurer credits their champion network with preventing change fatigue across multiple simultaneous programs by pacing adoption and tailoring communications locally, thereby maintaining high service continuity.
These examples highlight that a well-designed enterprise champion model is more than a support function. It is a strategic enabler of organisational resilience and talent development.
Closing Thoughts
Building a sustainable enterprise change champion model requires commitment, structure, and investment. But the payoff is clear: an organisation equipped not only to execute change more effectively but to cultivate the next generation of leaders who understand change at a deep level.
By proving impact through metrics, integrating champions into career pathways, and cultivating a culture of collective ownership and agility, senior change and transformation practitioners can transform their organisations into change-ready powerhouses.
If you’re keen on setting up an enterprise change champion group powered by change data insights, reach out and chat to us.
It used to be that change management is the ‘poor’, neglected cousin of other disciplines in terms of access to functional software to assist in its performance across every aspect of change and risk management. There is a wide range of software available for a range of project management disciplines such as, business analysis, testing, project management, portfolio management, etc. However, for change management, the pickings have been almost non-existent 10 years ago.
Fast forward to 2022, there is now a handful of change management software in the market to assist with various work categories for the change manager. However, there is still ways to go in the understand of organisational change management in the marketplace. Compilations of change management software offering on the internet is usually a mixture of all types of software, many of which are not organisational change management in nature, and instead, technical change management (used by IT folks). For example https://orgmapper.com/change-management-tool/
How does a change management process help a company?
A change management process helps a company by providing a structured approach to minimizing disruptions and transitioning individuals, teams, and organizations from a current state to a desired future state. It minimizes resistance, enhances communication, and ensures that changes align with business goals, ultimately leading to smoother transitions and improved outcomes.
How can change management software help the change practitioner?
What is the implementation of change management?
The implementation of change management involves a structured approach to transitioning individuals, teams, and organizations from a current state to a desired future state. It includes strategies for managing resistance, communication plans, and training initiatives to ensure that changes are adopted effectively and sustainable within the organization.
Project change delivery
The vast majority of change management professionals in the industry are focused on delivering projects and implementing effective change management strategies to enable them to make an informed decision about their approach. It’s no wonder that most change management tools, including project management software and various change tools, are focused to support the entire change process and project delivery as a result, maintaining consistency throughout all initiatives. What are some of the areas in which project change delivery work can be made easier by software?
1. Automating change management deliverable work
A significant part of the work of change management professionals is spent on preparing for and documenting a clear roadmap of change management deliverables. These include detailed impact assessment, learning plan, stakeholder matrix, and type of change plans, etc. These deliverables are critical documents which are critical dependency for other project milestones. For example, stakeholder analysis and matrix is critical before broader stakeholder engagement can be made, since the analysis reveals who the stakeholders are and how they may be engaged throughout the change process.
One of the biggest pains faced by change management professionals is the amount of time required to manually create these deliverable documents. The work can be tedious, requiring weeks of manual work to complete. For example, the stakeholder matrix document can be a brain-numbing piece of activity, wading through a data dump of the organisational directory to determine every Tom, Dick and Harry which titles and names should be included in the stakeholder list for the project. Then, a lot of similar information then must be re-typed and entered into different versions in other change management deliverable documents such as detailed impact assessment or learning needs analysis, ultimately affecting customer satisfaction.
Software can automate much of the manual work involved. For example, Change Automator, a robust workflow automation software, allows the ease of use to link data already captured earlier on in the project, such as the relevant stakeholders matrix, with other change management deliverables such as detailed impact assessment, to ensure the right people are involved and to minimise manual re-work. With the ability to track changes, any data updated in one document will therefore update content in other documents, including integrations with tools like Power BI. This then saves on the tedious re-work required when data is updated or changes, which is pretty much a given throughout the project lifecycle. From a quality perspective, this also ensures any human-error is reduced in the data that should be synchronised across documents.
A common risk in change management delivery is that stakeholders may be left out inadvertently, or that a previously captured stakeholder in the stakeholder matrix is left out in the engagement process due to human-error. The impact of this type of error can be disastrous to the outcome of the project. Having cross-linked documents in one central place reduces the risk for this type of error.
2. Change management survey (readiness and adoption)
A key part of change management success is through careful monitoring of stakeholders throughout the change process to ensure visibility. In the earlier part of the project, this involves understanding to what extent stakeholders may be clear of the objectives of the project, their roles in it, and general awareness. Later on in the project, it could be more on understanding their engagement level of support which can be a predictor of ultimate adoption and overall support for the change. This overall change readiness level should be monitored across the project through surveys or interviews.
Surveys are inherently time consuming to design, administer and report manually. Significant time can be taken throughout each phase of the survey process. This is a no-brainer in terms of using a software tool. Most projects use Microsoft Forms or SurveyMonkey to do the job. However, you may want more robust features such as conditional question design, for example, if a respondent answers ‘yes’ for not supporting the change, then an additional question pops up to ask why.
Surveys can include sentiment analysis where the focus of the survey is on any shifts in stakeholder feelings and attitudes toward the project. In this case, it is critical to define in detail the characters of each stakeholder group in concern. These would then determine respondent characteristics to measure in the survey design.
There are also tools that measure employee sentiments through corporate social media channels such as Yammer and Teams. For example, Swoop Analytics can help to measure collaboration styles and other behavioural insights about how employees interact with each other on those channels. The data map can reveal key influencers and core influential network connectors.
The biggest value of change surveys lies in the reporting. Most survey tools offer fairly simple reporting using bar charts or pie charts. For short, simple surveys these may suffice. However, if you are working on a fairly detailed change adoption tracking survey, more advanced reporting features may be required. You may want to easily change the colour scheme of the chart, change different chart types, identify anomalies and trends, or highlight certain parts of the data to make it easier for your audience.
3. Project change reporting
Having the ease and flexibility of experimenting with different chart designs is critical for stakeholder impact. If you need hours of work to come up with a few charts the likelihood is that you will not bother. Some stakeholders may also have various personal preferences which can easily take significant time to modify. This is especially when you need the time to focus on engaging with your stakeholders, rather than tweaking excel spreadsheets.
Creating the right AI dashboard can create significant impact on stakeholders and help achieve your change objectives. Data speaks for itself and the right data visualisation can create memorable impact more than words alone. If you are driving toward change adoption, then having an AI-enhanced dashboard of core behaviour changes and tracked capability shifts, along with key metrics and key features, can act as a core part of change governance conversations. With a monthly cadence of reviewing these core data points, stakeholders can hold each other accountable to understand remaining work involved and zoom in on how to drive full change adoption.
Change reporting may not be limited to just survey results. Even seemingly ‘boring’ spreadsheet data such as detailed impact assessment may be easily turned into highly visual and interesting reports to help stakeholders understand what the changes mean and how different groups are impacted by the change.
One of the more popular ways in which change delivery has adopted software is in leveraging digital tools that provide functions to onboard or train users of new or changed systems. There are numerous providers in this area. These include WalkMe, UserGuiding, and Userlane.
Most of the tools provide similar functions to help walk users through interfaces of the system and even allow interactive experience where users can be tested in clicking on the right part of the system as a part of the training or onboarding process. The application is always for system interfaces since the tool only supports web-based systems.
Change capability
Another way in which change management software may assist change practitioners is in building change management capabilities related to change capability and documentation methodologies. There are various tools that help to measure, track, and report on change management activities and assess the impact of change initiatives, including key performance indicators and change impact analysis. This clarity could be that you would like to measure the change leadership skills of leaders, change alignment agility of stakeholder groups, or test employees as a part of skills assessment to ensure they have the right skills for the new system or process.
Using change management software, you can easily pre-program test items and answers to make it easy for yourself to score and tabulate audit test results without any manual work. You can also assign weightings to different questions to evaluate the capability of the respondent as a part of an assessment. You can even configure the assessment to provide results to the respondent at the end of the assessment, and email the feedback as well. Generally, these features are only offered as a part of a learning management system where significant time and effort is required to prepare the system for the assessment. Now, digital tools offer easy point-and-click features, with pre-configured templates saving you significant time and cost.
Change portfolio management
Managing a portfolio of initiatives used to be an approach only adopted by more mature organisations. However, with the rapid pace and intensity of changes, more and more organisations are adopting this approach to manage multiple initiatives.
Managing a portfolio of initiatives can only be done via data. There is already a myriad of project portfolio management systems in the market to help PMOs and project portfolio managers manage a slew of initiatives. The focus of project portfolio management systems is on project timelines, cost, resourcing, etc.
Change portfolio management focuses on the impact of changes and how they may impact the organisation across initiatives. There is also focus on change delivery resourcing and change capability development. One of the most critical pain points faced by organisations is change saturation and change fatigue. To better manage a portfolio of initiatives from a change perspective and manage potential change saturation, data is required.
Effective change portfolio management tools can help you:
Identify and plot change saturation points for different parts of the organisation
Identify risk levels of potential change saturation across roles, locations, layers of the organisations, etc.
Assess to what extent changes may be better delivered as an integrated package to one part of the organisation, or broken down to smaller, more digestable chunks
Assess to what extent changes may be better aligned and delivered through integrated messaging from an impacted stakeholder perspective (vs. from project perspective)
In summary, there are many strong reasons why change management professionals should adopt digital change management solutions to achieve greater change outcomes as well as to automate the tedious parts of the work to gain time to spend with stakeholders. With the ever increasing pace of digitisation in organisations, change management must also follow suit in digitising itself. Just as we could use modern fabrication techniques to build skyscrapers that are stronger and more resilient vs using traditional brick and mortar, so should change managers in leveraging digital tools to support digital transformations.
Creating a strategic approach to effective communication and a change management plan and change management strategy in change management is one of the most important pieces of work for the change management practitioner. Done well, proactive change management communication can drive the change initiative to success by instilling a sense of urgency among stakeholders. If not crafted carefully, it can lead the project to its downfall even before the project starts. A good communication strategy and change strategy should be logical, fact based, clear, and uphold honesty. Yet, despite its importance, strategic change management is one of the least understood aspects of the change management process.
A key pitfall for the change practitioner in devising an effective change management strategy is to create one that is ‘cookie cutter’ and ‘generic’. Creating a detailed plan and a generic change strategy is very easy, not because the change practitioner is lazy or is incompetent, but mostly because there is usually a standard and acknowledged ‘way of doing things around here’ in organisations.
Organisations are used to doing things in certain ways and this is often incorporated as a part of the ‘culture’. ‘The way we do things around here’ is often the impetus by which stakeholders reinforce the ‘status quo’ of implementing change in a particular way. This is because ‘this way’ has always worked in the past and is what people are used to.
What’s wrong with using the status quo you may ask? Well, sometimes it may be the best way, but not always. Why? Because not all changes, especially **organizational changes**, are the same.
Changes come in all shapes and sizes, with some large multi-year transformations having disruptions, whilst others are small process improvements. There are also different types of changes, ranging from significant organizational leadership restructuring that impact the entire organization and company culture, connecting business strategy to system implementation through to new product launches. Some changes may require a highly structured approach, process-centric implementation methods that incorporate best practices such as a regulatory process change, which can enhance the likelihood of success. Other changes may be better with a more agile approach, such as transformation programs focused on continuous improvement to improve customer centricity.
Rather than asking what the stakeholders think would be the best change strategy or approach, take a fact-based approach utilizing workplace analytics. If possible, refer to previously implemented changes as benchmarks or comparison yard-sticks. Ask your stakeholders how previously implemented changes fared against their respective change management strategies.
Key points of your research should include the following:
Size/Complexity of the change
Context/Type of change
Numbers of people impacted
Length of the project
Engagement and communication approaches taken
Stakeholder education and influencing approaches taken
Stakeholder responses and engagement levels
Lessons learnt and what worked or did not work
Taking a benchmark approach to developing a change strategy ensures that you take into account the facts of what worked and did not work. You also take into account differences in the change initiatives and how these could have impacted the change strategy taken and therefore the corresponding outcomes. Where possible, use change metrics such as stakeholder responses or survey results. These are powerful indicators of change outcomes against the strategies taken.
Most change management strategies are not strategies
If you review change management strategies devised across initiatives, you will find that most change strategies are not actually strategies, but a compilation of change tactics. These change tactics are a list of aspirational ‘philosophies’ that may be nice to have but there is no real way of knowing how these drive the project to success.
Let’s look at some examples of these change tactics.
Be transparent and truthful. This is a common used one, where the goal is to be as authentic and truthful as possible with the goal of gaining trust of impacted stakeholders. This means not intending to making the messaging overly positive, and erring on the side of being as realistic as possible. This may be hard to implement if Corporative Affairs or Internal Communications does not agree with this approach.
Involve stakeholders in designing the change. This is another popular aspiration for change initiatives. The thinking is to be as inclusive as possible to include a range of stakeholders in the design and implementation of the change, so as to maximise engagement. The more engaged targeted stakeholders are the higher the changes of change adoption success.
Strong senior leader sponsorship. Thanks to a wide range of books and literature touting the importance of gaining senior leader sponsorship, this is another common one. Yes, having senior leaders driving the change will go a long way toward ensuring change outcome success. However, this in itself may not be sufficient. Again, depending on the type of change it maybe better to have a bottom-up, grass roots approach, rather than a top down approach.
All of the above change tactics may seem sound and logical. And they probably are. However, the whole point of a change strategy is not to list out a set of tactics, principles or philosophies. There could be a very long list of seemingly logical tactics. It also may not be possible or realistic to commit fully to every tactic.
Change strategy is about deciding what top few change approaches will be taken that will directly drive the most initiative success. This means that the change practitioner must start with the project targets and objectives. These should be as black and white indicators. For example, increase customer satisfaction by 10%, increase efficiency by 20%, or increase customer responses by 40%.
Now that you have identified the project targets and objectives from the project manager, you now need to identify change management requirements. For example, to increase efficiency by 10%, the project needs to ensure that the customer service representatives follow the new process 100% of the time. To do this, the project may need to design a series of audit and system notification processes to reinforce this behaviour. From a change management perspective your requirement could be ensuring that the report is built into and discussed by the relevant leaders and teams. Also, that the performance scorecard for concerned roles have built in these metrics.
Let’s take another example. To increase customer satisfaction by 20% the project needs to ensure that frontline agents know how to have the right type of conversations with customers. The change management requirement could be to instil continual coaching and feedback to drive continual skills uplift that is based on competency ratings. The Change strategy would then be driving competency based uplift.
In this way you can see that each part of the change strategy directly contributes to reaching the project targets. The direct contribution of each change strategy can then be evaluated in terms of its contribution importance.
So now you know how to devise a change strategy that directly contributes to the goals of the project. Your change management work should be geared around driving this strategy. And the contribution of your work should be clear and explicit. It should not be brushed aside as a ‘nice to have’ or too ‘soft and fluffy’.
If you want to learn more about creating the right change management metrics, visit The Ultimate Guide to Measuring Change.
Creating the right change management strategy is an important step. Even more important throughout the implementation of the project is how you monitor and adapt to the challenges that come your way. Change strategies may need to be tweaked or revised depending on the data you’re seeing along the way. To find out more about how to leverage data to resolve the most challenging questions during your change journey chat to us about how The Change Management platform can help.
Managing multiple change initiatives is not a new concept nor is it new to organizations. What is perhaps ‘newer’ is how change practitioners are using data to manage multiple changes. Change practitioners that manage a portfolio of initiatives used to focus on building capability in various arenas from employee capability, leadership capability, through to the effectiveness of engagement and learning channels. However, using business and change management data to help companies is just as critical.
Is change management becoming more important?
Yes, change management is increasingly vital in today’s fast-paced business environment. Organizations face constant shifts in technology, market demands, and workforce dynamics, which impact their business processes. Effectively managing these changes helps minimize resistance, enhances employee engagement, and ensures smoother transitions, ultimately leading to improved performance and sustainability in a competitive landscape.
In this article, we will explore the top five challenges associated with the current approaches to managing multiple change initiatives, including the implementation of the change due to lack of resources and insufficient resources. We explore these common approaches and critique key challenges, along with alternatives.
Change heatmaps have become a popular tool for classifying departments based on the impact of a change initiative. However, two key issues often arise with this approach: the oversimplification of the traffic light classification system and the lack of granularity at the department level.
One of the most common ways to visually depict the impact of multiple changes is to use the heatmap. This is normally using a 3-point rating system (high, medium, low) to determine the level of impact across the various departments across the organisation. Whilst the rating process is an easy exercise, there are some very serious challenges:
Even for the 3 level rating system the change practitioner may be challenged with how this rating is determined and what it is based on. Not every team within the same department may be equally impacted
There may be different impacts for different roles within the same team and department
The impact may be different depending on whether the focus is on employees, customers, process, system or partner
Typically most use a monthly rating scale. However, for busy organisations with lots of changes, the change volume may go up and down within the same month. With one rating it oversimplifies what actually happens throughout the month
With only 3 levels of ratings, a lot of departments end up having the same rating level for months, meaning there is not much they can do with this data.
In Summary, the summarised monthly rating for one department indicates medium-level change. But at what time of the month, for what role, for what team, and for what type of impact?
The below is an example of a change heatmap from the University of California, Berkeley.
a. Traffic Light Classification Too Simplistic:
The traditional red, yellow, and green traffic light system used in change heatmaps is a simple way to communicate the status of a department’s readiness for change. However, this simplicity can be misleading. Red may indicate a problem, but it does not provide insights into the nature or severity of the issue. Likewise, green may suggest readiness, but it might hide underlying complexities or dependencies.
Even for the 3 level rating system the change practitioner may be challenged with how this rating is determined and what fact it is based on. Also, the impact may be different depending on whether the focus is on employees, customers, process, system or partner. Typically most use a monthly rating scale. However, for busy organisations with lots of changes, the change volume may go up and down within the same month. With one rating it oversimplifies what actually happens throughout the month. Even if the singular departmental rating is split into rating by initiative, this does not provide an aggregate department-level rating that is aggregated based on logic.
To overcome this challenge, organizations need a more nuanced classification system that takes into account the specific issues within each category. This could involve incorporating additional colours or using a numerical scale to better represent the diversity and complexity of challenges within each department.
b. Department Level Not Granular Enough:
While change heatmaps provide a high-level overview, they often lack the granularity required to understand the specific challenges within each department. Different teams within a department may be impacted differently, and a broad classification may not capture these variations.
To address this issue, organizations should consider adopting a more detailed classification system that breaks down each department into its constituent parts. This granular approach allows for a more targeted and effective change management strategy, addressing specific issues at the team and role levels.
In Summary, the singular monthly rating for one department indicates medium-level change. But at what time of the month, for what role, for what team, and for what type of impact?
2) Using Project Milestone Roadmap to Sequence Impacts
Project milestone roadmaps are commonly used to sequence the impacts of change initiatives. However, this approach faces challenges in terms of the sufficiency of milestones and the difficulty of overlaying multiple capacity considerations.
Below is an example from Praxis Framework.
a. Milestones Are Not Sufficient vs Overall Aggregate Impact Levels:
While project milestones provide a structured timeline for change initiatives, they may not capture the full scope of the impact on the organization. Engaging key stakeholders is essential during this process, as milestones often focus on project-specific tasks and may overlook broader organizational changes that occur concurrently. For example, adoption may require months and is not a single point-in-time milestone per se.
To overcome this limitation, organizations should supplement milestone roadmaps with an overall aggregate impact assessment. This holistic view ensures that the sequence of milestones aligns with the broader organizational objectives and minimizes conflicts between concurrent initiatives.
b. Difficulty of Overlaying Multiple Capacity Considerations:
Managing multiple change initiatives requires a delicate balance of resources, and overlaying capacity considerations can be challenging due to the scope of the change. Project milestone roadmaps may not adequately address the interdependencies and additional resources needed due to the resource constraints that arise when multiple initiatives are in progress simultaneously.
To enhance capacity planning, organizations should invest in advanced project management tools that allow for the dynamic adjustment of timelines based on resource availability. This ensures a realistic and achievable sequencing of impacts, taking into account the organization’s overall capacity.
3) Relying Purely on Excel and PowerPoint to Manage Multiple Change Initiatives
While Excel and PowerPoint are ubiquitous tools in the business world, relying solely on them to manage multiple change initiatives presents challenges related to the agile nature of changes and the difficulty of having interactive data-based conversations. This is especially the case that most change initiatives are digital changes, and yet they are been managed using non-digital means? How can change practitioners ‘be the change’ when they are using dated ways of driving digital change?
a. Agile Nature of Changes Means Ongoing Updates Are Required:
Change initiatives are inherently dynamic, and their requirements can evolve rapidly, especially in response to market shifts. Excel and PowerPoint, while useful for static reporting, lack the real-time collaborative capabilities needed to accommodate the agile nature of changes while maintaining the status quo.
To address this challenge, organizations should consider adopting change management and collaboration tools that enable real-time updates and collaboration. Cloud-based platforms provide the flexibility to make ongoing adjustments, ensuring that stakeholders are always working with the latest information.
b. Difficulty of Having Interactive Data-Based Conversations and Federated Model of Change Data:
Excel and PowerPoint may struggle to facilitate interactive discussions around change data. As organizations increasingly operate in a federated model, with dispersed teams working on different aspects of change initiatives, a more collaborative and integrated approach is essential.
Implementing dedicated change management platforms that support interactive data-based discussions can enhance collaboration and provide a centralized repository for change-related information. This ensures that all stakeholders have access to the latest data, fostering a more transparent and collaborative change management process.
4) Preparing Business Operations Readiness for the Amount of Change
Preparing business operations for a significant amount of change requires a strategic approach that incorporates capacity and time considerations while maintaining granularity in data.
a. Using Business Operations Speak: Capacity, resources, time.
Business operations readiness is often discussed in terms of capacity and time. However, the challenge lies in translating these concepts into actionable plans. Capacity planning involves understanding the organization’s ability to absorb change without compromising existing operations, while time considerations are crucial for ensuring a smooth transition without disruptions.
Change practitioners need to distill the ‘ask of the business’ in business speak. Business stakeholders may not be interested in the various classifications of change or the varying degrees of cultural changes involved. What they are interested in is what you want from my team, how much time you need them to dedicate, and for what team members, so that they can plan accordingly.
b. Granularity of Data:
The granularity of data is essential for effective business operations readiness. Generic metrics may not capture the specific needs and challenges of individual departments or teams, leading to oversights that can impact the success of change initiatives.
Implementing a comprehensive data collection and analysis strategy that considers the unique requirements of each business unit ensures a more accurate understanding of operational readiness. This granularity allows organizations to tailor change management strategies to specific needs, enhancing the likelihood of successful implementation.
5) Getting Executive Engagement and Decision Making
Ensuring executive engagement and decision-making is critical for the success of change initiatives. However, achieving this engagement poses its own set of challenges.
To overcome this challenge, organizations should:
Establish Clear Governance and Engagement Channels:
Ensure that there is in place a clear governance bodies making decisions on the overall control of successful change initiatives across the organisation, focusing on the success of the change. A robust communication strategy ensures that communication channels between change management teams and executives are also well-defined and effective. Regular updates and transparent reporting on the progress and challenges of change initiatives build trust and encourage executive engagement.
Align Change Initiatives with Strategic Objectives:
Demonstrate the alignment of change initiatives with key performance indicators related to the organization’s strategic goals and objectives. Executives are more likely to engage when they see how a particular change contributes to the overall success of the organization and its growth.
Provide Decision-Making Frameworks:
Equip executives with decision-making frameworks that guide them through the complexities of change initiatives. Clearly defined criteria for evaluating the success of a change, along with potential risks and mitigation strategies, empower executives to make informed decisions.
Highlight the Business Impact:
Clearly articulate the business impact of change initiatives. Executives are more likely to engage when they understand the tangible benefits and potential risks associated with a particular change. Use data and analytics to support the business case for change.
Offer Ongoing Support and Education:
Ensure that executives have the necessary support and training to navigate the complexities of change management at all levels of the organization. This includes providing relevant information, resources, and sufficient time to help them make informed decisions and actively participate in the change process, especially regarding new processes. Creating ‘bite-sized’ and summarised insights is key for executives.
Effectively managing multiple change initiatives is a complex task that requires a holistic and adaptive approach. By addressing the challenges of change management, including change management obstacles associated with classification, sequencing, tool reliance, business operations readiness, and executive engagement, organizations can enhance their change management strategies and increase the likelihood of successful outcomes, ultimately maintaining a competitive edge. Embracing innovative tools, fostering collaboration, and maintaining a strategic focus on organizational goals are key elements in overcoming these challenges and navigating the ever-evolving landscape of change.
In this article, we’ve stressed the importance of data. You may wonder about the amount of time and effort required to establish all the various points mentioned in the article and if this is even doable. Well, using Excel and other static non-digital ways of managing change data will mean a significant volume of work, and even then it may not provide a clear picture that gives you the various cuts of data required to drive meaningful conversations. Resort to automation provided by change management software such as The Change Compass to assist in data capture, data analysis, and dashboard generation.
So what is the role that change managers play in managing product changes during the agile product delivery process? What are the actions, approaches, deliverables and considerations required for change professionals in an agile environment?
So what is the role that change managers play in managing product changes during the agile product delivery process? What are the actions, approaches, deliverables and considerations required for change professionals in an agile environment?
We will address these in this article.
What is agile product delivery?
According to Scaled Agile, agile product delivery is a “customer-centric approach to defining, building, and releasing a continuous flow of valuable products and services to customers and users”.
Agile product delivery forms a core part of agile project delivery. Each project is delivering a particular product and this is concerned about delivering innovative products and services with the right solutions at the right time.
The mechanics within each product delivery add up to determine the overall project outcome. Therefore, the design of agile product delivery practices is absolutely crucial in achieving overall project goals. Let’s now examine some of these practices in detail.
Customer centricity vs project centricity
In agile methodology the end customer is the number one focus. In various organisations ‘customer’ may be used for various internal stakeholder groups. Yes, often projects may be delivering solutions that are only benefiting internal employee groups. However, the end goal for agile is focused on the end external customer.
This means, whatever solutions or benefits that the project is bringing to the internal stakeholder group, ideally these would support the organisation’s work in benefiting the end customer. In all aspects of prioritisation and discussions of solution design, the focus must always be on the end customer.
The role of the change manager in customer-centricity is to plan out and execute on the change process according to what supports the end customer and enhances customer satisfaction. If the change has a direct impact on the customer, this means engaging the customer (as needed through marketing groups) and considering customer feedback. And if the impact is more on internal stakeholders, thinking still needs to be applied to facilitate the engagement, readiness, and adoption of the change so as to benefit the end customer.
Even when you’re working on internal stakeholders, being customer-centric means:
Putting yourself into the customers’ shoes – Using customer insights, analytics, and data to inform insights about customer preferences
Focusing on the whole product vs individual features – Taking a holistic view of what is in the interest of customers, the design of the overall change should take into account how customers interact with the overall service or product
Designing change to the customer lifetime value – Most organisations would have a mapping of the value delivered to the customer across different phases across time.
Develop on cadence in agile change management
Agile teams have ongoing, structured routines that help them develop solutions on a regular basis. Within each iteration (a standard, fixed timebox where the team delivers incremental value) the team aims to deliver according to plan.
The Change Manager needs to understand the broader plan and milestones of key outcomes delivered by the project, as well as when each iteration will occur. From this project plan, a clear change management team plan detailing the overall approach in engaging stakeholders based on the impact of the change that will be delivered and the frequency and nature of communication should be formed.
Careful attention needs to be placed on setting the expectation with stakeholders on the clarity of readiness of developed solutions. A lot of stakeholders may not be comfortable with how fast solutions may be iterated and that the solution outcome may not be known until, often, closer to the release date. Addressing the stakeholder expectations of release cadence is critical to ensure that there is no misalignment.
Program Increments (PIs) informed the larger timebox of what will be delivered, whilst each iteration delivers a smaller set of solutions. From a stakeholder engagement perspective, there needs to be a balance of painting a clear overall story of what will be delivered within the overall PI, balanced by particular details contained within each iteration.
Working in program increments
To add value as a change manager across a program increment it is critical that you examine the overall program as a whole system. By addressing potential friction points across the work of each agile team and each iteration, the overall program solution starts to take shape. Your job is to interpret what this means to stakeholders and decipher this into engagement and readiness activities.
Sequencing and planning
The schedule of agile releases is mainly determined based on agile team resourcing and delivery deadlines.
Throughout the iterations, how do the release timings impact stakeholders against their existing business-as-usual demands as well as potential releases from other projects? This is a key contribution of the Change Manager in ensuring that change impact release plans are optimised from the perspective of the receiving business. How frequently should communication updates be undertaken for various stakeholder groups given the pace of the releases? Again, the design of this forms a critical part of the overall change plan.
Change delivery also forms a central part of agile team delivery. Change deliverables are often dependent on other agile team members. For example, to deliver change impact assessment you need the finalised solution to be defined by the Business Analyst. In order to deliver the right level of communication briefing to business stakeholders, you need to set the expectation of the timing and minimum information required.
Overall vision and narrative
Is there a clear overall vision and narrative from which individual release communications can build on top of? It’s critical to paint a clear picture of what the end state looks like without the nuances of the mechanics of the solution (as these will not be known at the beginning of the program).
Release on demand
Release on demand is a practice and a process whereby new functionality is deployed as needed based on stakeholder needs. Depending on the change impact of the feature the change manager needs to be ready to send communications and updates as needed, sometimes within a short notice period.
Note that not all releases necessarily require communications for users. And depending on the type of change being released different formats of communication may be leveraged. For example, system changes may benefit from within-app notifications versus emails or other forms of update.
Communications and engagement may also be bundled as necessary to provide a packet of updates to stakeholder groups versus constant and continuous updates. The change manager needs to examine the nature of change impacts and stakeholder needs to determine the right tactic to be used.
Release design
Change impact sizing and design is a critical role taken by the change manager. From change impact assessment, the change manager needs to consider the impact of the overall size of the change impact from a business stakeholder perspective. Where possible, a packet of change may need to be de-scoped to be broken into smaller pieces of change if this is going to be easier for adoption in consultation with stakeholders. On the other hand, many changes may also be bundled together into a larger change release, again based on optimal stakeholder adoption considerations. This form a critical part of lean flow design.
Bugs in agile change management
The change manager has a role to play in setting expectations with stakeholders that with agile system releases that go fast and constant, there should be an expectation that bugs are probably unavoidable. Ensure that users are clear in terms of how to highlight bugs, the documentation process for these issues, and how they will be kept in the loop as each bug is addressed.
On the other hand, bugs may be so disruptive that an effective roll-back approach must be in place in case the change did not land well, particularly when adding new tools. Effective communication content and processes, including discussions about implementing job security, need to be in place to manage this risk. This is a critical part of ongoing agile change management.
BAU integration
With frequent releases, care needs to be given to how the change projects will be adopted and embedded within the impacted business as a part of business-as-usual workflows. For smaller changes, such as hiring a new team member or launching a new product, this may not be critical, but for larger change impacts, the change manager needs to weave each change into a coherent, overall change approach that minimizes disruptions and includes post-release adoption strategies. This includes embedding roles and responsibilities, tracking, and reporting mechanisms.
Automation in agile change management
A part of agile is about delivering fast as frequently as possible. To support this automation of any part of the development process is encouraged where possible. For the change manager in product teams, various digital tools, including change management software, should be leveraged by product managers to support the continuous improvement and deployment of their communication skills. This includes scheduled digital communication, tracking of audience responses, knowledge article views, and digital versions of the single view of change.
Measurement in agile change management
Measurement is a critical part of agile change management. Without the right key performance indicators (KPIs) and metrics to indicate how the change is progressing, it is difficult to know if the trajectory is heading in the right direction towards the end state. A clear set of measurements needs to be in place to measure constant, and continuous change releases.
