There is now plenty of research and articles on successful organizational change management out there. However, most of these are focused on driving a singular change process impacting a set of key stakeholders with one change management plan. The single change may be the launch of a new product, digital transformation, a radical change that impacts the company culture, changes to internal processes, a change in the company’s strategic goals, or some kind of organizational transformation that breaks from the status quo, or examples of transformational change that lead to clear success. How many organisations can you think of that are just driving one singular change initiative across the entire organisation? Exactly.
Particularly when an organization is adopting agile ways of working, managing multiple change initiatives becomes even more critical. If everyone is working towards one big initiative launch it is much easier to plan for. It is more complex with lots of initiatives all launching a series of changes throughout the year. However, in agile organisations this is the norm. Managing the impact of changes on the frontline, in this case, becomes more complex with significant coordination and planning involved.
To effectively manage multiple change initiatives one needs to establish the following:
To manage multiple change initiatives one needs to be able to see what is changing. This sounds simple but yet one of the hardest things to accomplish for large organisations where there are often more than a hundred or hundreds of change initiatives at any one time. This is not about individual project management. To achieve this, one needs to be able to capture the data on the change impacts and how they impact different parts of the organization. This can then be used to better plan for initiatives as a part of the strategic plan.
Most organisations still struggle with spreadsheets to try and create some view of what is changing, however still not able to effectively capture the totality of what is changing since this involves a view of not just projects, but also BAU (business as usual) initiatives. To move with the times, organisations need to be able to leverage digital means of understanding what is changing, how they impact stakeholders and team members, and what this means from a planning perspective.
Effective organisational change governance and decision making
Most organisations are good at ensuring that there is a structured way of allocating the dollars to the right priorities when it comes to funding projects. However, the same may not be said for effective governance in orchestrating and planning for how change initiatives are implemented and embedded into BAU, particularly with regards to business processes. This is often not a part of the company’s culture and a part of the change management process.
An effective operations governance process is required, leveraging from a clear view of the totality of what is changing, and through this effective sequence, package, integrate or prioritise the change impacts on the organization. This includes tracking key performance indicators of the changes and ensure the entire team understands how this is tracked and reported to drive the success of change initiatives. Strong organisational leadership from the senior executives and effective communication is required to drive full adoption.
The governance body needs to be able to establish clear decision-making and escalation processes and articulate this to initiative drivers.
Oversight of Change Initiatives: Strategies for Successful Change
With significant changes happening concurrently, it is a top priority for change managers to establish clear and scalable business engagement channels as a part of the change management strategy to ensure that stakeholder groups feel like they are a part of designing the changes (vs. being a victim of them). This includes regular business forums such as weekly, monthly or quarterly meetings and standups. Other communication channels would also include intranet, email, Yammer or audio-visual outlets.
It is through well-oiled engagement channels across the entire organization that initiative owners and business leaders can quickly and frequently implement changes rapidly and concurrently. This will thereby increase the chances of success for change.
To read more about managing multiple initiatives check out our Knowledge section under Portfolio Management where we have a range of practical articles.
The MoSCoW method of prioritization is well used by Business Analysts, Project Managers, and Software Developers in software development. The focus is on identifying and agreeing with key stakeholders what are the core levels of requirements that should be focused on more than others. This process of prioritization is a great way to enable a better outcome in focusing the efforts of the team on the most important aspects of the solution given limited time and cost. Let’s take a closer look.
The MoSCoW prioritization technique is well used by Business Analysts, Project Managers and Software Developers and particularly relevant in agile project management. The focus is on identifying and agreeing with key stakeholders what are the core levels of requirements that should be focused on more than others. This process of prioritization will then enable a better outcome in focusing the efforts of the team on the most important aspects of the solution given limited time and cost.
MoSCoW stands for: Must Have, Should Have, and Could Have.
There is significant opportunity for change practitioners to also adopt this technique to better prioritise a range of different change interventions. Too often, change activities are planned as a result of stakeholder requests, and not necessarily as a result of a prioritized approach of what approaches/activities provides the best outcome versus others.
1. Must Haves:
These are core, fundamental project requirements that must be there for the end outcome to be there. These are the non-negotiable ones defined at the startup of the project without which the goals of the project cannot be achieved.
For example, in implementing a new system, the users must know that the system is going to replace the previous system and the reason for this. Users must also know how to operate the new system prior to the older system being switched off.
2. Should Haves:
These are features or requirements that would have a high priority to reach the project outcome within the product development process. These can often be core features that will add metrics to the user/customer experience. However, they are not a must, and given challenges in time or cost they can be deprioritized.
For example, for a new system implementation it would be highly desirable to allow the users to access a sandbox to be able to play with the features prior to the launch to improve their readiness. It could also be that due to the large number of users using the system it makes sense to conduct a large scale awareness campaign to broadcast the arrival of the new system. Core user experience requirements and basic navigation functionalities may be a part of this category, as a part of the minimum viable product (MVP).
3. Could Haves:
These are nice to haves given sufficient resources such as time and cost. These requirements are definitely not critical and can easily be deprioritized as needed.
For example, in implementing the new system it may be nice to have coaching workshops with users prior to the go-live to offer additional learning support for those who may need more help. It could also be various system support materials such as cheat sheets, booklets, etc. to help the user embed the ins and outs of using the new system.
4. Won’t Haves (or Would Haves):
These are potential features or requirements that may be looked at in the future if there is sufficient resources available. This is the lowest in the order of priority, meaning that it will not make significant impact to the outcome of the project.
For example, in implementing the new system refresh training sessions could be offered later down the line for some users after go live. Depending on the organization and previous experiences an ‘embedment campaign’ could also be scheduled to drive continual usage of the system. But given the cost required these are deemed lowest in the priority.
In prioritizing change management approaches and interventions this way, we are adopting a structured method of determining the activities we are investing in to get the right outcome. The clarity of which interventions are core and foundational, versus others that are desirable or nice to haves is important to the success of the initiative. This could also avoid any disagreements or questioning of the change approach further down the line as the approach follows a structured and agreed process with stakeholders.
In today’s dynamic business environment, marked by ongoing disruptions like environmental challenges, economic shifts, and the rapid advancement of AI tools, the pace of change demands that organizational agility and change readiness become critical capabilities for sustained competitive advantage and success. As businesses strive to remain competitive and responsive to ever-changing conditions, change practitioners play a pivotal role in designing and incorporating agility into their change planning and implementation efforts.
This article explores the importance of agility in creating an agile organization through effective organizational change management, drawing on research from industry experts such as McKinsey, and offers valuable insights for change practitioners to foster agility in their projects while building a change-ready workforce and navigating unpredictable business decisions, stakeholders, and environments.
The Significance of Agility in Change Management:
Agility has emerged as a key attribute for organizations seeking to thrive amidst disruption. McKinsey’s research on enterprise agility highlights the positive business impact achieved by companies that effectively embrace agility. These organizations demonstrate higher customer satisfaction, increased revenue growth, and improved employee engagement. By incorporating agility into their change initiatives, organizations can respond swiftly to market changes, capitalize on emerging opportunities, and mitigate risks more effectively.
Specifically, what this means is that imagine you are in a program of 5 projects over 2 years. All projects are working with a range of stakeholders within 2 divisions. There can be significant influence that your program can have on the work practices of these 2 divisions over a 2 year period. Now imagine incorporating agile practices in how you implement change. You now have the ability to really shift the dial for these work functions.
Designing Agile Change Management Strategies:
Change practitioners working on individual projects play a vital role in fostering agility within their organizations. To design and incorporate agility into change planning and implementation, practitioners should consider the following strategies:
Embrace iterative approaches: This may sound like a no-brainer, but definitely start by incorporating agile principles into your project planning and delivery. By breaking down change initiatives into smaller, manageable increments, practitioners can iterate and adjust their strategies based on real-time feedback and evolving stakeholder needs. Not a lot of change practitioners do this well. A lot still follow the standard plan and execute approach without a lot of iteration and pivoting of tactics and approaches.
Foster a culture of experimentation: Encourage stakeholders and team members to experiment with new ideas and solutions. Create a safe environment where psychological safety is prioritized, and setbacks are seen as learning opportunities, enabling continuous improvement and challenging the status quo of innovation. You may or may not have the luxury of being a part of a project team that promotes this environment. However, you can proactively set the expectation with your stakeholders and explain why this is valuable to help deliver a better change outcome.
Encourage collaboration and cross-functional teamwork: Establish channels for open communication, collaboration, and knowledge sharing. Cross-functional teams can contribute diverse perspectives and expertise, enabling quicker decision-making and adaptability. This may sound like a generic corporate speak … team work and collaboration. However, you can easily design cross-functional teams, work processes and decision making forums to encourage this. The connection and collaboration across teams helps them to be more agile to understand different business forces and perspectives, avoiding ‘insular thinking’.
Prioritize flexibility and adaptability: Recognize that change plans may need to be adjusted or revised as circumstances evolve. Build flexibility into the change management process, allowing for agility in response to unexpected challenges or opportunities. In every project, there are aspects that are different from other projects, even if you are involving the same stakeholders. Designing chuncked-down, flexible modules of change helps you to be more agile.
Remaining Agile as a Change Practitioner:
Change practitioners themselves must also cultivate transparency and agility to navigate the dynamic nature of their projects. Here are some key strategies for remaining agile:
Embrace a growth mindset in your change approach: Adopt a mindset that values continuous learning, adaptability, and continuous improvement. Embrace new change tactics, methodologies, technologies, and tools that enhance your change management capabilities. Try new digital or automation solutions.
Develop strong relationship-building skills: Cultivate effective relationships with stakeholders and maintain open lines of communication. Building trust and rapport enables better collaboration and facilitates agility in responding to shifting stakeholder needs. By doing this, you can have much more influence on your stakeholders.
Stay informed and anticipate change: Continuously monitor industry trends, technological advancements, and organizational dynamics. Anticipate potential disruptions and proactively adjust your change plans to accommodate evolving circumstances. This requires strong business acumen.
Foster personal resilience: Change management can be challenging, particularly when faced with unexpected changes. Develop personal resilience by cultivating emotional intelligence, stress management techniques, and the ability to adapt to new circumstances. To lead and influence your stakeholders you need to be their anchor.
In an era of ongoing disruptions and environmental challenges, agility has emerged as a crucial capability for organizations embarking on change initiatives. Change practitioners play a pivotal role in designing and incorporating agility into their change planning and implementation efforts.
By embracing iterative approaches, fostering a culture of experimentation, encouraging collaboration, and prioritizing flexibility, change practitioners can drive agility within their organizations. Additionally, by developing a growth mindset, nurturing strong relationships, staying informed, and fostering personal resilience, change practitioners can remain agile in the face of evolving business decisions, stakeholders, and environments. Embracing agility in change management is key to successfully navigating the ever-changing landscape of the digital world.
Change is an inevitable part of, not just corporate life and business processes, but life in general. It’s a natural occurrence that we all must face at some point. But despite the many benefits that organizational change can bring, many of us are still reluctant to embrace it. After all, for many, it is easier to keep doing the same thing than to do something different and unknown. With the unknown comes risks of disruption and a desire for consistency. Risks that may be scary. Risks that things may be worse than the current scenario.
Often resistance to change can be thought of as an outcome of bad change management. If you don’t effectively manage your stakeholders or have not effectively assessed the impact of change, there are likely going to be common reasons for root causes of resistance for change resistance, including a lack of confidence among stakeholders. Resistance may arise from bad change interventions, including ineffective consultation or engagement of stakeholders.
However, sometimes despite everything you’ve done. You’ve ticked every box and followed almost a ‘textbook’ approach to the change process. Despite this, you are still getting change resistance from some stakeholder groups. Why is this happening?
Sometimes there may be very few levers you can pull in preventing the resistance. You’ve gotten your leadership cohorts to reinforce and evangelize the purpose and benefits of the change. You’ve tried all you can to reach the hearts not just the minds of what you think impacted employees want to hear.
Why is this happening? It could be the fear of failure or loss aversion that has led to the resistance. This is the research-backed fact that people tend to have a cognitive bias where the pain of losing is much stronger than the pleasure of gaining.
One example of this phenomenon is why people stay in bad marriages. Despite the obvious benefits of leaving an unhappy marriage, many people still choose to stay in it. This is because they fear the loss of familiarity, comfort, and security that their marriage provides. This is despite how unhappy they honestly are in the marriage. They may also be afraid of the unknown or the changes that come with divorce. These same fears and reluctance to change can also be seen in organizations and their team members facing change.
For something less dramatic, another example could be changing phones. We are wedded to our phones for a big chunk of how we run our lives. Changing a phone operating system, brand, or even model can be a quite a change that a lot of people are not inclined to go through, until they are pushed to do it.
When organizations decide to implement successful changes, they often focus on the potential benefits that will come from the change, including the introduction of a new product line. They may present a logical argument for why the change is necessary and how it will benefit everyone involved. However, even with a clear and logical argument, people may still be reluctant to embrace change. This is because change often means loss, even if it is the loss of something negative or unwanted.
For example, if an organization decides to implement new software, employee resistance may occur even if it will make their jobs easier and more efficient. This is because they are comfortable with the current system, and they fear the unknown as a significant cause of resistance, or the potential loss of job security and skills that they have developed with the current system. They may also fear that the new system will require them to learn new skills or take on new responsibilities, stemming from their fear of the unknown. This can be despite your best efforts to create a positive picture of the end state.
There are still lots of examples in organisations where employees prefer to stick to their current manual ways of work using spreadsheets, versus the more efficient and effective digital tools.
They may have created the spreadsheet themselves. They may have spent months building consensus across the organisation to use this process. Changing this process could mean not only a lack of familiarity, but it could also result in a loss of their ‘importance’ of their role. So as a result, people continue to maintain the status quo. Stay within the comfort zone. After all, if they don’t change, they can’t be ‘blamed’ if something goes wrong.
As change practitioners, we cannot just blame those impacted by the change. We may also need to see if this applies to us. For example, a lot of change practitioners still use manual spreadsheets to create a ‘single view of change’ despite the amount of manual work that is required. They may have faced leaders who question the integrity of the rating system or become ‘bored’ with the same heatmap or chart since they can’t use it to make black-and-white business decisions. But, fear of the unfamiliarity dominates.
Organizations need to recognize this fear of loss and work to address it in line with their organizational goals, as clarity is essential in managing change. Here are some practical suggestions for designing change initiatives that can help tackle this barrier:
1. Look at the data about how your target employees have responded to different types of changes in the past. What types of responses were there with a certain type or volume of change? How were these dealt with? What were the outcomes? What types of employees were more ‘resistant’ than others?
2. Communicate Clearly, Early and Transparently: Slow change adopters may need more time to prepare for change and what it means for them. Involving key stakeholders as part of the communication process can clarify available options if they do not like the end state. What if they disagree? Communication should be clear, transparent, and empathetic. It should focus on the benefits of the change, and address any concerns or fears employees may have. It should also focus on what would happen if the changes are not adopted.
3. Involve employees in the Change Process (where it makes sense): Inviting employees to participate in the change process can help them feel more invested in the change and less fearful of losing control. When employees have a voice in the decision-making process, they are more likely to feel valued and respected. This also allows businesses to identify potential challenges and concerns that employees may have, which can be addressed before the change is implemented. In addition, setting key metrics can help in evaluating the effectiveness of this approach. This approach may need to be applied carefully, especially when dealing with a highly resistant group of employees. If not carefully managed, the change approach may get out of control.
4. Provide Support: Change can be overwhelming and stressful, especially when employees feel like they are not equipped to handle it. Providing support and training can help employees feel more confident and prepared for the change effort. It can also help them see the benefits of the change more clearly. This may sound like common sense. But it’s amazing how many change initiatives don’t provide any support to impacted groups, beyond technical support.
5. Celebrate Successes: Change can be a long and difficult process, so it is essential to celebrate successes in a timely manner along the way. Recognizing and acknowledging employee efforts and successes can help maintain momentum and motivation. This is another seemingly ‘no-brainer’. Designing a series of successes helps create positivity.
6. Be Patient: Change takes time, and employees need time to adjust. It is essential to be patient and understanding. Rushing the process or ignoring employees’ concerns can lead to resistance and resentment. In your change readiness assessment or strategic plan during the baselining phase of the project, if you’ve found that change adoption could be slow and resistance could be expected, ensure you’ve factored in sufficient timing.
Change is difficult, even when it makes logical sense and has many benefits. People are often afraid of losing something, even if it is something negative or unwanted, which can lead to discomfort. Organizations need to recognize this fear of loss and work to address it when implementing changes. Recognising this cognitive bias is the first step. By providing support, and resources, and involving employees in the change process, organizations can help reduce the fear of loss and successfully implement change.
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.
