The change management process is the sequence a change travels from decision to daily habit, and the version that delivers adoption treats that sequence as a loop run on evidence rather than a timeline approved in advance. Most organisations still design the process as a straight line: assess readiness, publish a communication plan, run training, monitor, declare success. That picture is tidy, easy to approve and easy to report against, and it bears little resemblance to what happens when a change meets real people with real workloads.
This guide is for change, HR and transformation leaders who are accountable for adoption, not just for delivery. It argues that the seven steps of the process still matter, but that their order, pace and content should be set by what your people data shows during delivery, not by a plan frozen at kickoff. By the end you will be able to design a process that fits your organisation’s maturity, reads the change from the impacted person’s side, measures continuously, and adjusts between rollout cycles instead of after the post-implementation review.
Why linear processes fail
A linear change management process fails because it treats the organisation as stable, the change as isolated and the plan as an accurate forecast, and none of the three holds in a complex organisation. Traditional models assume that if you follow the steps correctly, transformation will succeed. That assumption misses something fundamental about how organisations behave once a change starts to move.
The environment has also become harder to plan against. A 2026 Harvard Business Review analysis by Gartner HR researchers attributes the growing difficulty of leading through change to four converging factors: changes are stacked on top of one another, they are continuous with no clear start or end date, they are larger and interdependent, and they are increasingly driven by external forces such as technology and geopolitics. A process that assumes one change, one timeline and one team is designing for a world that no longer exists.
The core problems with linear change management approaches
Readiness is not static. An assessment conducted three months before go-live captures a moment in time, not a prediction of future readiness. Organisations that are ready today might not be ready when implementation arrives, especially if other changes have occurred, budget pressures have intensified or key leaders have departed.
Impact is not uniform. The same change affects different parts of the organisation differently. Finance functions often adopt new processes faster than frontline operations. Risk-averse cultures resist more than learning-oriented ones. Users with technical comfort embrace systems more readily than non-technical staff.
Problems emerge during implementation. Linear models assume that discovering problems is the job of the assessment phase. But the most important insights often emerge during implementation, when reality collides with assumptions. When adoption stalls in unexpected places or proceeds faster than projected, that is not a failure of planning. It is valuable data about what actually drives adoption in your specific context.
Multi-change reality is ignored. Traditional change management processes often overlook a critical fact: organisations do not exist in a vacuum. They are managing multiple concurrent changes, each competing for attention, resources and cognitive capacity. A single change initiative that ignores this broader landscape is designing for failure.
The evolution: from rigid steps to an iterative process
An iterative change management process plans, implements, measures, learns and adjusts, then cycles again with what it has learned. Modern change management processes embrace this agile change management approach because complex change reveals itself through delivery, not through analysis beforehand.
The shift is visible in the profession’s own data. Prosci’s latest benchmarking found that fewer than 70% of participants now follow a formal change management methodology, the first time that has been true since 2011, a decline Prosci links to the rise of agile and adaptive approaches. The same study found that practitioners actively managing a portfolio of changes rose from 38% to 43%. Practice is moving from one-off project processes towards continuous, portfolio-level operation. For a deeper look at the research behind this move, see our summary of why iterative, agile change management succeeds where linear approaches fail.
The iterative change cycle
Each pass through the cycle asks the same five questions of a defined cohort, function or geography:
Plan: Set clear goals and success criteria for the next phase. What do we want to achieve? How will we know if it is working? What are we uncertain about?
Design: Develop specific interventions based on current data. How will we communicate? What training will we provide? Which segments need differentiated approaches? What support structures do we need?
Implement: Execute interventions with a specific cohort, function or geography. Gather feedback continuously, not just at the end. Monitor adoption patterns as they emerge, and track both expected and unexpected outcomes.
Measure: Collect data on what is actually happening. Are people adopting, and are they adopting correctly? Where are barriers emerging? Where is adoption stronger than expected? Which change management metrics reveal the true picture?
Learn and adjust: Analyse what the data reveals. Refine the approach for the next iteration based on actual findings, challenge initial assumptions with evidence, and apply lessons to improve subsequent rollout phases.
This iterative cycle is not a sign that the original plan was wrong. It is recognition that complex change reveals itself through iteration. The first iteration builds foundational understanding. Each subsequent iteration deepens insight and refines the change management approach, so the fifth cohort should adopt faster and with fewer barriers than the first.
The organisational context matters
The same change management methodology works differently depending on the organisation it is implemented in, which is why copying another company’s process rarely reproduces its results. Change maturity, leadership capability and culture all change what a good process looks like.
Have muscle memory and infrastructure for iterative change
Build on existing change management best practices
Low maturity organisations:
Need more structured guidance and explicit governance
Require more time between iterations to consolidate learning
Benefit from clearer milestones and checkpoints
Need more deliberate stakeholder engagement
Require foundational change management skills development
The first step of any change management process is an honest assessment of organisational change maturity. Can this organisation move at pace, or does it need a more gradual approach? Does change leadership have experience, or do they need explicit guidance? Is there existing change governance infrastructure, or does it need to be built?
These answers shape the design of your change management process. They determine the pace of implementation, the frequency of iterations, the depth of stakeholder engagement required, the level of central coordination needed, and the support structures and resources you will have to provide.
The impact-centric perspective
An impact-centric process designs around the lived experience of the person who has to change, not around the project’s categories of “users”, “stakeholders” and “early adopters”. Every change affects real people, and the quality of your design depends on how well you understand what the change asks of each of them, given everything else they carry.
This matters more as changes interlock. The Gartner HR researchers writing in Harvard Business Review describe today’s changes as interdependent rather than separate, which means the effect on one person rarely comes from one initiative alone. A practical way to start is a structured change impact assessment that maps what changes for each group, by how much and when.
From the impacted person’s perspective
Change saturation: What else is happening simultaneously? Is this the only change or one of many? If multiple initiatives are converging, are there cumulative impacts on adoption capacity? Can timing be adjusted to reduce simultaneous load? Recognising the need for change capacity assessment prevents the saturation that kills adoption.
Historical context: Has this person experienced successful or unsuccessful change previously? Do they trust that change will actually happen, or are they sceptical based on past experience? Historical success builds confidence; historical failure builds resistance. Understanding this history shapes engagement strategy.
Individual capacity: Do they have the time, emotional energy and cognitive capacity to engage with this change given everything else they are managing? Change practitioners often assume capacity that does not actually exist. Realistic capacity assessment determines what is achievable.
Personal impact: How does this change specifically affect this person’s role, status, daily work and success metrics? Benefits are not universal. For some people, change creates opportunity. For others, it creates threat. Understanding this individual reality shapes what engagement and support each person needs.
Interdependencies: How does this person’s adoption depend on others adopting first? If the finance team needs to be ready before sales can go live, sequencing matters. If adoption in one location enables adoption in another, geography shapes timing.
When you map change from the impacted person’s perspective rather than a project perspective, you design very different interventions. You might stagger rollout to reduce simultaneous load. You might emphasise positive historical examples if trust is low. You might provide dedicated support to individuals carrying a disproportionate change load.
Data-informed design and continuous adjustment
This is where the modern change management process differs most sharply from the traditional one: nothing is assumed, and everything is measured. Implementing change without data is like navigating without instruments. Prosci’s research shows the payoff: among participants who measured compliance and overall performance, 76% met or exceeded project objectives, compared with 24% of those who did not measure.
Before the process begins: baseline data collection
A baseline gives every later iteration something to be compared against. At minimum, capture:
The current state of readiness
Knowledge and capability gaps
Cultural orientation toward this specific change
Locations of excitement versus resistance
Adoption history in this organisation
Change management performance metrics from past initiatives
During implementation: continuous change monitoring
As the process unfolds, data collection continues and tracks the full path from awareness to behaviour:
Awareness tracking: Are people aware of the change?
Understanding measurement: Do they understand why it is needed?
Engagement monitoring: Are they completing training?
Application assessment: Are they applying what they have learned?
Barrier identification: Where are adoption barriers emerging?
Success pattern analysis: What is driving adoption in the places where it is working?
This data then becomes the basis for iteration. If a readiness assessment showed low awareness and commitment did not emerge from initial communication, you are not simply communicating more. You are investigating why the message is not landing, and the reason shapes the solution.
How to measure change management success
Measuring change management success means tracking whether people are using the new way of working, how well, and whether it lasts, then using the answer to change what you do next. A single end-of-project survey cannot do that, and the real value of measurement is diagnostic rather than evaluative.
Consider the common case where adoption is strong in Finance but weak in Operations. You do not just provide more training to Operations. You investigate why Finance is succeeding:
Is it their culture?
Their leadership?
Their process design?
Their support structure?
Understanding the difference helps you replicate success in Operations rather than trying harder with a one-size-fits-all approach.
Effective measurement covers six dimensions throughout the change, and change management success metrics should be defined before implementation begins:
Adoption: who is using the new process or system, and how proficiently.
Readiness indicators: awareness, understanding, commitment and capability levels.
Behaviour change: whether people are actually changing how they work, not just attending training.
Performance impact: operational results against the baseline.
Sentiment and engagement: confidence, trust and satisfaction.
Sustainability: whether adoption persists over time or reverts.
Data-informed change means starting with hypotheses but letting reality determine strategy. It means being willing to abandon approaches that are not working and trying something different. It means recognising that what worked for one change will not necessarily work for the next one, even in the same organisation.
The 7-step change management process
The seven steps are a readiness checklist for an adaptive loop, not a one-way conveyor. Modern change management processes are iterative rather than strictly linear, but they still progress through recognisable phases, and understanding how those phases interact prevents you from getting lost in iteration. Steps 1 to 5 are the cycle every change passes through; Steps 6 and 7 are the organisational conditions that decide whether the cycle can run well.
Step 1: Pre-change planning
Before formal change begins, build foundations:
Assess organisational readiness and change maturity
Map the current change landscape and change saturation levels
Identify governance structures and leadership commitment
Conduct an impact assessment across all affected areas
Understand who is affected and how
Baseline the current state across adoption readiness, capability, culture and sentiment
This step establishes what you are working with and sets the pace and approach for everything that follows.
Step 2: Awareness and readiness building
Help people understand what is changing and why it matters. This is not one communication. It is repeated, multi-channel, multi-format messaging that reaches people where they are, and it should be tested against a readiness assessment so you know whether the message has landed.
Different stakeholders need different messages:
Finance needs to understand financial impact
Operations needs to understand process implications
Frontline staff need to understand how their day-to-day work changes
Leadership needs to understand the strategic rationale
Done well, this step moves people from unawareness to understanding and from indifference to some level of commitment. The ADKAR model’s first two elements, awareness and desire, describe this movement in individual terms, and Prosci’s ADKAR overview is a useful reference for sequencing it.
Step 3: Capability building
Equip people with what they need to succeed:
Formal training programmes
Documentation and job aids
Peer support and buddy systems
Dedicated help desk support
Access to subject matter experts
Practice environments and sandboxes
This step recognises that people need different things: some need formal training, some learn by doing, some need one-on-one coaching. The process design accommodates this variation rather than enforcing uniformity.
Step 4: Implementation
This is where iteration becomes critical:
Launch the change, typically with an initial cohort or geography
Measure what is actually happening through change management tracking
Identify where adoption is strong and where it is struggling
Surface barriers and success drivers
Iterate and refine the approach for the next rollout based on learnings
Repeat with subsequent cohorts or geographies
Each cycle improves adoption rates and reduces barriers based on evidence from previous cycles.
Sustained change requires ongoing reinforcement, continued support and regular adjustment as the organisation learns how to work most effectively with the new system or process.
Step 6: Integration with organisational strategy
The change management process does not exist in isolation from organisational strategy and capability. It is shaped by, and integrated with, several critical factors.
Leadership capability
Do leaders understand change management principles? Can they articulate why change is needed? Will they model new behaviours? Are they present and visible during critical phases? Weak leadership capability requires more structured support, more centralised governance, more explicit role definition for leaders, and coaching and capability building for change leadership.
Operational capacity
Can the organisation actually absorb this change given current workload, staffing and priorities? If not, what needs to give? Pretending capacity exists when it does not is the fastest path to failed adoption. A realistic assessment covers:
Current workload and priorities
Available resources and time
Competing demands
Realistic timeline expectations
If you do not yet have a way to quantify this, start with a change capacity model that compares the load of planned changes against the headroom each group actually has.
Change governance
How are multiple concurrent change initiatives being coordinated? Are they sequenced to reduce simultaneous load? Is someone preventing conflicting changes from landing at the same time? Is there a portfolio view preventing change saturation? Effective enterprise change management requires:
Does the organisation already have change management tools and techniques, governance structures and experienced practitioners? If so, the new process integrates with these. If not, do you have the resources to build this capability as part of this change, or do you need to work within the absence of this infrastructure?
Culture and values
What is the culture willing to embrace? A highly risk-averse culture needs a different change design than a learning-oriented culture. A hierarchical culture responds to authority differently than a collaborative culture. These are not barriers to overcome but realities to work with.
The future: digital and AI-enabled change management
The future of the change management process lies in combining digital platforms with AI to expand scale, precision and speed while keeping human judgement in charge. The evidence so far says the hard part of AI adoption is not the technology. Prosci’s study of 1,107 professionals found that 63% of AI implementation challenges stem from human factors rather than technical limitations, which is precisely the territory a change process exists to manage.
Current state versus future state
Current state:
Practitioners manually collect data through surveys, interviews and focus groups
Manual analysis takes weeks
Pattern identification is limited by human capacity and intuition
Iteration is based on what practitioners notice and stakeholders tell them
Future state:
Digital platforms instrument change, collecting data continuously across hundreds of engagement touchpoints
Adoption behaviours, performance metrics and sentiment indicators are tracked in real time
Machine learning identifies patterns humans might miss
AI surfaces adoption barriers in specific segments before they become critical
Algorithms predict adoption risk by analysing patterns in past changes
AI-powered change management analytics
AI-powered insights can highlight which individuals or segments need support before adoption stalls, identify which change management activities are working and where, recommend where to focus effort for maximum impact, correlate adoption patterns with dozens of organisational variables, predict adoption risk and success likelihood, and generate automated change analysis and recommendations. Our complete guide to AI in change management covers the practical use cases.
But here is the critical point: AI generates recommendations, and humans make decisions. AI can tell you that adoption in Division X is 40% below projection and that users in this division score lower on confidence. It can recommend increasing coaching support. A human change leader, understanding business context, organisational politics and strategic priorities, decides whether to follow that recommendation or adjust it based on factors the algorithm cannot see.
Human expertise plus technology
The future of managing change is not humans replaced by AI. It is humans augmented by AI:
Technology handling data collection and pattern recognition at scale
Humans providing strategic direction and contextual interpretation
AI generating insights while humans make nuanced decisions
Platforms enabling measurement while practitioners apply judgement
This future requires change management processes that build in data infrastructure from the beginning. It requires defining success metrics and change management KPIs upfront, continuous measurement rather than point-in-time assessment, treating change as an operational discipline with data infrastructure, building change management analytics capabilities, and investing in platforms that enable measurement at scale. A change intelligence platform such as Change Compass is built for this: it brings change impacts, capacity and adoption signals into one view, so the loop described in this guide runs on current data rather than on last quarter’s survey.
Designing your change management process
The change management framework that works for your organisation is not generic. It is shaped by organisational maturity, leadership capability, change landscape and strategic priorities. Designing it is a six-part exercise, and each part feeds the next.
Step 1: Assess current state
What is the organisation’s change maturity? What is leadership’s experience with managing change? What governance exists? What is the cultural orientation? What other change initiatives are underway? What is capacity like? What is the historical success rate with change? This assessment shapes everything downstream and determines whether you need a more structured or more adaptive approach.
Step 2: Define success metrics
Before you even start, define what success looks like:
What adoption rate is acceptable?
What performance improvements are required?
What capability needs to be built?
How will you measure change management effectiveness?
What change management success metrics will you track?
Who is affected? In how many different ways? What are their specific needs and barriers? What is their capacity? What other changes are they managing? This impact-centric change assessment shapes:
Sequencing and phasing decisions
Support structures and resource allocation
Communication strategies
Training approaches
Risk mitigation plans
Step 4: Design the iterative approach
Do not assume linear execution. Plan for iterative rollout:
How will you test learning in the first iteration?
How will you apply that learning in subsequent iterations?
What decisions will you make between iterations?
How will the speed of iteration balance with consolidation of learning?
What change monitoring mechanisms will track progress?
Step 5: Build in continuous measurement
From day one, measure what is actually happening:
Adoption patterns and proficiency levels
Adoption barriers and resistance points
Performance impact against baseline
Sentiment evolution throughout phases
Capability building and confidence
Change management performance metrics
Use this data to guide iteration and make evidence-informed decisions about change management success.
Step 6: Integrate with governance
How does this change process integrate with portfolio governance? How is this change initiative sequenced relative to others? How is load being managed? Is there coordination to prevent saturation? Is there an escalation process when adoption barriers emerge? Effective change management requires integration with broader enterprise change management practices, not isolated project-level execution.
Change management best practices for process design
Start with clarity on the fundamentals of change management:
A clear vision and business case
Visible and committed sponsorship
Adequate resources and realistic timelines
Honest assessment of starting conditions
Embrace iteration and learning:
Plan, do, measure, learn and adjust cycles
Willingness to challenge assumptions
Evidence-based decision making
A continuous improvement mindset
Maintain human focus:
Individual impact assessment
Capacity and saturation awareness
Support tailored to needs
Empathy for the lived experience of change
Use data and technology:
Baseline and continuous measurement
Pattern identification and analysis
Predictive insights where possible
Human interpretation of findings
Integrate with organisational reality:
Respect cultural context
Work with leadership capability
Acknowledge capacity constraints
Coordinate with other changes
The process as an adaptive system
The modern change management process is fundamentally different from traditional linear models. It recognises that complex organisational change cannot be managed through predetermined steps, and it requires data-informed iteration, contextual adaptation and continuous learning.
It treats change not as a project to execute but as an adaptive system to manage. It honours organisational reality rather than fighting it. It measures continually and lets data guide direction. It remains iterative throughout, learning and adjusting rather than staying rigidly committed to original plans.
Most importantly, it recognises that change success depends on whether individual people actually change their behaviours, adopt new ways of working and sustain those changes over time. Everything else (process, communication, training, systems) exists to support that human reality. Organisations that embrace this approach do not achieve perfect transformations. They achieve transformation that sticks, that builds organisational capability, and that positions them for the next wave of change.
What to do before your next change goes live
Take the seven steps you already use and make three changes this quarter. Run the first rollout to a single cohort and agree in advance what result from that cohort would make you alter the plan. Put one adoption measure and one capacity measure on the same page, reviewed fortnightly with sponsors. And check the change against everything else landing on the same people before you confirm a date. None of this requires a new methodology or a new team. It requires deciding, before kickoff, that the process will respond to evidence, and then letting it. Do that, and the review that follows the go-live reads as a record of what you learned and adjusted, not an explanation of why adoption fell short.
Frequently asked questions
What is the change management process?
The change management process is the structured approach for moving individuals, teams and organisations from a current state to a desired future state. It typically includes pre-change planning, awareness building, capability development, implementation with reinforcement, and sustainment. Modern versions are iterative rather than linear, using continuous measurement and agile change management principles to adjust to real-time adoption data.
What is the difference between linear and iterative change management processes?
A linear process follows predetermined steps (plan, communicate, train, implement, measure at the end) and assumes that following the methodology correctly guarantees success. An iterative process repeats a plan, implement, measure, learn and adjust cycle with each cohort or phase. Iterative approaches suit complex change because they let evidence inform strategy, so barriers are found early and what works is replicated.
How does organisational change maturity affect process design?
Change maturity determines how fast an organisation can move through iterative cycles and how much structure it needs. High-maturity organisations with experienced leaders and strong governance can move quickly and adjust decisively. Low-maturity organisations need more explicit governance, more support and more time between iterations to consolidate learning. Assess maturity before designing the process, because it sets the pace, structure and governance you need.
How do you measure change management effectiveness throughout implementation?
Track adoption, readiness indicators, behaviour change, performance impact, sentiment and sustainability, and define the success metrics before implementation begins. Continuous measurement shows what is actually driving adoption or resistance in your context, which is almost always different from planning assumptions. It lets you replicate what works, fix what does not and make evidence-informed decisions with each cycle.
How does the process account for multiple concurrent changes?
Effective enterprise change management maps the full change landscape, assesses cumulative impact and saturation, sequences changes to reduce simultaneous load, and builds support for people managing several changes at once. Portfolio-level governance coordinates initiatives, prevents conflicting changes and monitors capacity. Single-change processes that ignore this context tend to fail because they design for capacity that does not exist.
Data Foundations and the Limits of Traditional Reporting
Change and transformation leaders are increasingly tasked with supporting decision making through robust, actionable reporting. Despite the rise of specialist tools, teams still lean heavily on Excel and Power BI because of their familiarity, ease and widespread adoption. However, as the pace and scale of organisational change accelerate, these choices reveal critical limitations, especially in supporting nuanced organisational insights.
Why High, Medium, Low Reporting Falls Short
Many change teams default to tracking change impact and volume using simple “high, medium, low” traffic light metrics. While this method offers speed and clarity for basic reporting, it fails to capture context, regional nuance, or the real intensity of change across diverse teams. This coarse approach risks obscuring important details, leaving senior leaders without the depth needed to target interventions or accurately forecast operational risks.
Change practitioners are often short on time and choosing whatever is easier and faster often becomes the default choice, i.e. Excel. This short-sighted approach focuses on quickly generating an output to try and meeting stakeholder needs without thinking strategically what makes sense at an organisational level, and the value of change data to drive strategy and manage implementation risks.
Data Capture: Getting the Inputs Right
Excel’s flexibility lets teams start capturing change data quickly, but often at the expense of structure. When fields and templates vary, information can’t be standardized or consistently compared. Manual entry introduces duplication, missing values, and divergent interpretations of change categories. Power BI requires disciplined and structured underlying data to function well; without careful source management, output dashboards reflect input chaos rather than clarity. Therefore, when pairing Excel with Power BI chart generation, often a BI (business intelligence) specialist is required to help configure and structure the chart outputs in Power BI.
Tips for effective data capture:
Establish clear data templates and definitions before rolling out change tracking.
Centralize where possible to avoid data silos and redundant records.
Assign responsibilities for maintaining quality and completeness at the point of entry.
Data Cleansing and Auditing: Maintaining Integrity
Excel and Power BI users are frequently responsible for manual data validation. The process is time-consuming, highly error-prone, and often fails to catch hidden inconsistencies, especially as data volumes grow. Excel’s lack of built-in auditing makes it tough to track changes or attribute ownership, increasing risks for compliance and reliability.
Best practices for cleansing and auditing:
Automate as much validation as possible, using scripts or built-in platform features.
Use a single master source rather than local versions to simplify updates.
Develop version control and change logs to support traceability and confidence in reporting.
Visualization, Dashboarding, and Interpretation Challenges in Change Reporting
After establishing robust data foundations, the next hurdle for senior change practitioners is translating raw information into clear, actionable insights. While Excel and Power BI each provide capabilities for visualizing change data, both bring unique challenges that can limit their effectiveness in supporting strategic decision making.
Visualization and Dashboard Design
Excel’s charting options are familiar and flexible for simple visualizations, but quickly become unwieldy as complexity grows. Static pivot charts and tables, combined with manual refreshing, reduce the potential for interactive analysis. Power BI offers more engaging, dynamic visuals and interactive dashboards, yet users frequently run into formatting frustrations, such as limited customization, bulky interfaces, and difficulties aligning visuals to precise narrative goals.
Some specific visualization and dashboard challenges include:
Difficulty representing complex, multidimensional change metrics within simplistic dashboards, e.g. impact by stakeholder by location by business unit by type of change.
Limited ability in both tools to customize visual details such as consistent colour themes or layered insights without significant effort.
Dashboard performance degradation with very large or complex datasets, reducing responsiveness and usability.
Interpreting Data and Supporting Decision Making
Effective dashboards must not only display data properly but also guide users toward meaningful interpretation. Both Excel and Power BI outputs can suffer when change teams focus too heavily on volume metrics or simple aggregated scores (like high/medium/low, or counting activities such as communication sent) without contextualizing underlying drivers. This can mislead executives into overgeneralized conclusions or missed risks.
Challenges include:
Dashboards overwhelmed by numbers without narrative or highlight indicators.
Difficulty embedding qualitative insights alongside quantitative data in either tool.
Sparse real-time feedback loops; often snapshots lag behind ongoing operational realities.
Tips and Tricks for Effective Visualization and Insights
Limit dashboard visuals to key metrics that align tightly with decision priorities; avoid clutter.
Use conditional formatting or custom visuals (in Power BI) to draw attention to anomalies or trends.
Build interactive filters and drill-downs to enable users to explore data layers progressively.
Combine quantitative data with qualitative notes or commentary fields to bring context to numbers.
Schedule regular dashboard updates and ensure data pipelines feed timely, validated information.
Once the foundation of reliable data capture and cleansing is set, the next major hurdle for senior change practitioners is transforming raw change data into clear, actionable insights. Excel and Power BI both offer visualization and dashboarding capabilities, yet each presents challenges that can limit their effectiveness in supporting strategic decision-making.
Visualization and dashboard design challenges
Excel’s charting features are familiar and flexible for simple visuals but quickly become cumbersome as complexity grows. Its static pivot charts and manual refresh cycles limit interactive exploration. Power BI adds interactive and dynamic visualizations but users often encounter limitations such as restricted formatting options, bulky interfaces, and considerable effort required to tailor visuals to convey precise change narratives.
Specific challenges include:
Struggling to represent complex, multi-dimensional change metrics adequately within simplistic dashboards.
Limited ability to apply consistent colour schemes or layered insights without advanced customization.
Performance degradation in dashboards when datasets become large or complex, impacting responsiveness and user experience.
Data interpretation and decision-making support
A dashboard’s true value comes from guiding users towards meaningful interpretation rather than just presentation of numbers. Both Excel and Power BI outputs may fall short if change teams rely excessively on aggregated volume metrics or high/medium/low scales without embedding context or deeper qualitative insight. This risks executives making generalized conclusions or overlooking subtle risks.
Key challenges include:
Dashboards overrun with numbers lacking narrative or prioritized highlights.
Difficulty integrating qualitative insights alongside quantitative data within either platform.
Reporting often static or delayed, providing snapshots that lag behind real-time operational realities.
Tips and tricks for more effective visualization and insight generation
Restrict dashboards to key metrics closely aligned with leadership priorities to avoid clutter.
Leverage conditional formatting or Power BI’s custom visuals to highlight trends, outliers or emerging risks.
Incorporate interactive filters and drill-downs allowing users to progressively explore data layers themselves.
Pair quantitative dashboards with qualitative commentary fields or summary narratives to provide context.
Implement disciplined refresh schedules ensuring data pipelines are timely and validated for ongoing accuracy.
Practical advice for change teams and when to consider dedicated change management tools
Change teams vary widely in size, maturity, and complexity of their reporting needs. For less mature or smaller teams just starting out, Excel often remains the most accessible and cost-effective platform for capturing and communicating change-related data. However, as organisational demands grow in complexity and leadership expects richer insights to support timely decisions, purpose-built change management tools become increasingly valuable.
Excel as a starting point
For teams in the early stages of developing change reporting capabilities, Excel offers several advantages:
Familiar user interface widely known across organisations.
Low entry cost with flexible options for data input, simple visualizations, and ad hoc analysis.
Easy to distribute offline or via basic file-sharing when centralised platforms are unavailable.
However, small teams should be mindful of Excel’s limitations and implement these best practices:
Design standardised templates with clear field definitions to improve consistency.
Concentrate on key metrics and avoid overly complex sheets to reduce error risk.
Apply version control discipline and regular data audits to maintain data accuracy.
Plan for future scalability by documenting data sources and formulas for easier migration.
Progressing to Power BI and beyond
As reporting needs mature, teams can leverage Power BI to create more dynamic, interactive dashboards for leadership. The platform offers:
Integration with multiple data sources, enabling holistic organisational views.
Rich visualizations and real-time data refresh capabilities.
Role-based access control improving collaboration and data governance.
Yet Power BI demands some specialist skills and governance protocols:
Teams should invest in upskilling or partnering internally to build and maintain reports.
Establish rigorous data governance to avoid “data swamp” issues.
Define clear escalation paths for dashboard issues to maintain reliability and trust.
When to adopt purpose-built change management platforms
For organisations undergoing complex change or those needing to embed change reporting deeply in strategic decision making, specialist tools like The Change Compass provide clear advantages:
Tailored data models specific to change management, capturing impact, readiness, resistance, and other essential dimensions.
Automated data capture integrations from multiple enterprise systems reducing manual effort and errors.
Advanced analytics and visualizations designed to support executive decision making with predictive insights and scenario planning, leveraging AI capabilities.
Ease of creating/editing chart and dashboards to match stakeholder needs, e.g. The Change Compass has 50+ visuals to cater for the most discerning stakeholder
Collaboration features aligned to change team workflows.
Built-in auditing, compliance, and performance monitoring focused on change initiatives.
Purpose-built platforms significantly reduce the effort required to turn change data into trusted, actionable insights, freeing change leaders to focus on driving transformation rather than managing reporting challenges.
Summary advice for change teams
Stage
Recommended tools
Focus areas
Starting out
Excel
Standardise templates, focus on core metrics, enforce data discipline
Purpose-built enterprise platforms (e.g. The Change Compass)
Integrate systems, leverage tailored analytics, support operations and executive decisions
Selecting the right reporting approach depends on organisational scale, available skills, and leadership needs. Recognising when traditional tools have reached their limits and investing in specialist change management platforms ensures reporting evolves as a strategic asset rather than a bottleneck.
This staged approach supports both incremental improvements and long-term transformation in how change teams provide decision support through high-quality, actionable reporting.
Practical advice for change teams and when to consider dedicated change management tools
Change teams vary widely in size, maturity, and complexity of their reporting needs. For less mature or smaller teams just starting out, Excel often remains the most accessible and cost-effective platform for capturing and communicating change-related data. However, as organisational demands grow in complexity and leadership expects richer insights to support timely decisions, purpose-built change management tools become increasingly valuable.
Excel as a starting point
For teams in the early stages of developing change reporting capabilities, Excel offers several advantages:
Familiar user interface widely known across organisations.
Low entry cost with flexible options for data input, simple visualizations, and ad hoc analysis.
Easy to distribute offline or via basic file-sharing when centralised platforms are unavailable.
However, small teams should be mindful of Excel’s limitations and implement these best practices:
Design standardised templates with clear field definitions to improve consistency.
Concentrate on key metrics and avoid overly complex sheets to reduce error risk.
Apply version control discipline and regular data audits to maintain data accuracy.
Plan for future scalability by documenting data sources and formulas for easier migration.
Progressing to Power BI and beyond
As reporting needs mature, teams can leverage Power BI to create more dynamic, interactive dashboards for leadership. The platform offers:
Integration with multiple data sources, enabling holistic organisational views.
Rich visualizations and real-time data refresh capabilities.
Role-based access control improving collaboration and data governance.
Yet Power BI demands some specialist skills and governance protocols:
Teams should invest in upskilling or partnering internally to build and maintain reports.
Establish rigorous data governance to avoid “data swamp” issues.
Define clear escalation paths for dashboard issues to maintain reliability and trust.
When to adopt purpose-built change management platforms
For organisations with complex change environments or those needing to embed change reporting deeply in strategic decision making, specialist tools like The Change Compass provide clear advantages:
Tailored data models specific to change management, capturing impact, readiness, resistance, and other essential dimensions.
Automated data capture integrations from multiple enterprise systems reducing manual effort and errors.
Advanced analytics and visualizations designed to support executive decision making with predictive insights.
Collaboration features aligned to change team workflows.
Built-in auditing, compliance, and performance monitoring focused on change initiatives.
Purpose-built platforms significantly reduce the effort required to turn change data into trusted, actionable insights, freeing change leaders to focus on driving transformation rather than managing reporting challenges.
Selecting the right reporting approach depends on organisational scale, available skills, and leadership needs. Recognising when traditional tools have reached their limits and investing in specialist change management platforms ensures reporting evolves as a strategic asset rather than a bottleneck.
This staged approach supports both incremental improvements and long-term transformation in how change teams provide decision support through high-quality, actionable reporting. With greater maturity, change teams also start to invest in various facets of data management, from data governance, data cleansing and data insights to provide a significant lift in perceived value by senior business stakeholders.
Understanding the real distinction between traditional, project-focused change management and the practice of enterprise change management (ECM) opens the door to a structured approach to genuine organisational agility and resilience. While project-based approaches often provide short-term benefits, ECM elevates change to an ongoing strategic capability, ensuring the entire organisation moves in concert rather than as a collection of isolated initiatives.
Rethinking the project lens
Traditionally, change management has surfaced in response to specific projects or change initiatives such as rolling out new technology platforms, redesigning new processes, digital transformation or introducing new products. These efforts share familiar hallmarks:
Project teams focus their energy on preparing the change process for affected employees, ensuring communications are clear, training is tailored, and stakeholder concerns are addressed swiftly. Metrics such as training completion rates or engagement scores offer a sense of progress, and feedback loops close as soon as “go-live” is achieved.
Project-centric change targets only those directly impacted by the initiative.
Coordination and collaboration between projects may be limited or absent.
Yet, this approach can quickly run into problems as the scale and frequency of the pace of change grows. And let’s face it, which sizeable organisation isn’t going through multiple changes at the same time? What appears to be a tightly managed process locally can, at an organisational level, lead to fragmentation, duplicated effort, and staff exhaustion – sometimes described as “change fatigue”. Diverse teams may be asked to adapt to multiple new systems, processes or behaviours in rapid succession, often with little integration or prioritisation.
Making sense of change saturation
Change fatigue is not a product of resistance to ‘doing things differently’ – it’s a predictable response when staff face overlapping initiatives with inadequate support or context. Portfolio-level visibility is rare in project-centric models, so team members may juggle competing demands with limited clarity on which changes matter most.
People become disengaged when the rationale for change is unclear or inconsistent.
Fragmented delivery means lessons learnt in one project aren’t transferred to others.
Resource conflicts emerge, exacerbating the pace and stress of simultaneous transitions.
Such issues underscore why organisations are searching for a more holistic way to approach change. Rather than reactively managing each initiative, ECM creates a deliberate structure for balancing effort, building capability, and driving lasting value in support of organisational strategy.
ECM is not a “set and forget” solution, nor a suite of templates for project managers to file away. It’s a disciplined, repeatable practice, and an approach that blends governance, data, collaboration and technology so that change becomes woven into daily operations. The core aim is for organisational change to transform from a series of disruptions to a united strategic capability aligned with strategic objectives and goals at various levels of the organisation.
Anchoring change in strategy and purpose
ECM starts with a clear connection to strategy. Initiatives are not pursued simply because they fit a project schedule – they are selected, sequenced and resourced to deliver against longer-term organisational goals and values. This strategic alignment requires regular, portfolio-wide reviews and a strong sense of interdependencies.
Change activity is mapped against broader business priorities for successful change management.
Leadership and employee engagement is visible and continuous throughout cycles of change.
Decisions are made with an understanding of cumulative change impact on staff and operations.
Governance and portfolio management
One of the defining features of ECM is the elevation of governance from discrete project steering groups to enterprise-wide oversight. This means all change activity – from small tweaks to major transformations – is managed within a portfolio framework. Coordinated governance offers leaders:
Real-time visibility of all initiatives, reducing risk of overlapping or conflicting changes;
The ability to sequence work to avoid bottlenecks or overload;
Standard tools for collecting outcomes, learning, and scaling success.
This portfolio approach doesn’t stifle innovation or agility – it enables them. With the big (and ‘medium’) picture in hand, leadership can make timely adjustments, redirect resources where needed, and capitalise on synergies between concurrent change efforts.
Consistent methodology and language
To embed ECM, organisations need a consistent approach to how change is defined, planned, and delivered. This includes shared terminology, frameworks, capability building and tools. A common language ensures that teams across functions understand what’s expected and how to measure success.
Shared frameworks reduce confusion and speed up onboarding new projects.
Common metrics allow lessons learnt from one area to influence others.
Continuous capability development ensures capability is refreshed as the organisation evolves (and capability does not just refer to training).
Cultivating organisational capability
ECM demands proactive investment in building change expertise at all levels, including the enterprise level. Unlike traditional approaches centred in specialist teams, ECM diffuses capability throughout the organisation. Everyone – from the executive team to frontline employee change champions – can access the knowledge, resources, and support necessary to champion change in their own environment.
The benefit of this diffusion is that change management doesn’t become a bottleneck or a specialist bottling plant; rather, it becomes part of the organisational DNA, supporting sustainable transitions even as pressure for change intensifies.
Capability-building programs help embed change management skills into routine business operations.
Peer communities foster exchange of techniques, stories and practical tools.
Capability-building programs help embed change into routine business operations.
Integrating change with core functions
Real value arises when change management links arms with other core business functions – risk, finance, HR, operations, technology:
Risk management: Proactive identification and management of people-related and operational risks ensure less disruption and faster remediation.
Human resources: Structured alignment of talent, training and role transitions supports staff through periods of uncertainty.
Finance: Budgets reflect strategic priorities and benefit targets, allowing responsive reallocation as circumstances shift.
Operations: Rollouts are coordinated with and catered to day-to-day workflow, minimising friction and confusion.
This interconnected approach elevates change from a project concern to a constant enabler, strengthening business readiness and agility.
Data, measurement and digital enablement
ECM takes measurement seriously, moving beyond output metrics to focus on outcomes and behaviour. Reporting and analytics track adoption rates, operational impact, readiness levels, and risk hotspots across all initiatives in progress.
Dashboards provide visibility for boards, executive teams and change leaders.
Analytics highlight trends over time, support decision-making, and provide evidence for resource allocation, including data on impact, capacity, readiness and adoption
Stakeholder feedback is collected continuously and drives refinement of practices.
Digital platforms make this easier – centralising data, automating routine assessments, and allowing fast recognition of leading and lagging indicators in change efforts. However, technology is an enabler not a replacement for skilled analysis and strategic judgement.
Continuous improvement and learning loops
ECM embeds cycles of review, adjustment and learning. Change accelerates, but so too does the speed of feedback, reflection, and correction. Leaders and teams benefit from:
Structured periodic reviews such as portfolio level PI planning (program increment planning);
Real-time lessons learned loops;
Identification and scaling of success stories;
Open channels for feedback and honest discussion.
These activities foster resilience, build trust, and demystify the process of change, turning every initiative – successful or otherwise – into an opportunity for deeper organisational learning.
Overcoming obstacles in enterprise change management
Establishing ECM is a long-term commitment and not without its challenges. Common obstacles include:
Leadership inertia or lack of sustained sponsorship;
Underinvestment in resources and capability growth;
Cultural resistance – where staff view working with change data as a burden rather than an opportunity;
Conflicting priorities between business units;
Difficulty standardising reporting or aligning diverse teams.
Overcoming these barriers requires persistent engagement, investment in technology and skills, and a strong focus on communication. Leadership needs to be visible, responsive, and ready to recalibrate as conditions change.
Implementing enterprise change management: A practical roadmap
Organisations seeking to build ECM need a clear game plan. Here’s a practical roadmap synthesised from best practice:
Vision and Alignment Begin with a shared understanding of why ECM matters and the results it is supposed to deliver. Shape the vision in conversation across the business, not from the top down.
Assessment of Current State Map change activity in flight, assess capability gaps, and audit readiness. Involve a range of stakeholders in the diagnosis phase to surface risks and opportunities, including readiness assessments where applicable.
Strategic Planning and Design Create a blueprint for integrated governance, methodology, and reporting lines. Define responsibilities, success measures and timing with input from relevant business units.
Capability-Building Investment Establish ongoing programs for training, coaching, and skill development. Make capability-building an expected part of career pathways and leadership routines.
Technology Selection and Integration Choose digital tools that fit scale, and goals. Integrate with other business systems where it makes sense for seamless reporting.
Delivery and Implementation Roll out ECM frameworks in parallel with major projects and business-as-usual activities. Regularly review progress, and support teams with tailored resources.
Evaluation, Review and Improvement Set up mechanisms for real-time feedback and course correction. Celebrate success, learn from setbacks, and continually update strategies as the business evolves.
Demonstrating the value of ECM requires robust evidence that change capability translates into real organisational outcomes. Key measures include key performance indicators related to adoption rates: How quickly and thoroughly staff take up new behaviours, systems or processes.
Adoption rates: How quickly and thoroughly staff take up new behaviours, systems or processes.
Readiness indices: Staff sense of preparedness and confidence ahead of change launches.
Business impact: Direct and indirect effects of change on performance, service delivery, quality, and customer satisfaction.
Resource allocation and utilisation: Efficiency in people, budget, and technology deployment over time.
Lessons learnt and continuous improvement: Degree of learning captured and applied to future projects.
Using a dashboard approach, organisations can compare progress between regions or functions, surface best practices, and allocate resources based on what works.
Enterprise change in action
ECM comes to life best through real examples. Consider an organisation embarking on major tech transformation. Early stages are plagued with confusion over responsibilities, inconsistent reporting, and pockets of resistance. By shifting to an ECM approach, the organisation sets up a central governance board, standardises its methodology, introduces regular engagement forums, and builds ongoing feedback loops.
The pace of adoption increases as staff gain clarity.
Risks are flagged earlier, allowing for timely intervention.
Costs are controlled through better prioritisation.
Change becomes less disruptive, more predictable, and ultimately more valuable.
In another scenario, a business grapples with multi-site process rollouts. ECM allows for custom pacing, local adaptation with centralised oversight, and regular calibration of resource needs. Staff feel more engaged and less overwhelmed, while leadership gains better transparency over outcomes.
Frequently Asked Questions
Why is ECM worth the investment?
ECM isn’t a luxury – it’s an organising principle for sustainable performance. It helps prevent costly failures and delays, reduces risk, and builds shared capability that fuels growth in an increasingly volatile world.
How does ECM drive transformation success?
By connecting change activity directly to broader strategy, creating clear frameworks and governance, and embedding skills at every level, ECM supports smooth, coordinated transitions – turning vision into reality with measurable benefit.
What analytical tools and technology support ECM?
Dashboards, portfolio level charts, and centralised analytics platforms provide transparency, drive accountability, and highlight the most impactful interventions. These tools work best when paired with regular dialogue and active review. Starting with simple excel sheets may make sense, but in the longer term have significant limitations.
How do organisations diffuse change leadership beyond core teams?
Training programs, peer communities, and open communication mean staff across every function can act as change advocates, spreading best practice without relying on a small group of specialists.
Final reflections
Enterprise change management represents a profound shift away from treating change as a series of one-off events towards establishing enduring, organization-wide capabilities in organizational change management. Through strategic alignment, integrated governance, continuous development, and robust measurement, ECM helps businesses thrive amid complexity and uncertainty, significantly improving the change implementation process.
The journey toward ECM takes sustained commitment, but the benefits – a culture that welcomes new ideas, adapts faster, and builds lasting value – are worth the effort. For those determined to succeed, ECM stands not just as a methodology, but the bedrock of a truly adaptive organisation.
What this also means is that the change and transformation team or practice increases its influence and contribution to the business goals in a direct way. Senior leaders and key stakeholders will see very clearly the value and contribution of the change management team and how it drives forward the business agenda. Gone are the days where change practice is seen as a nice-to-have with little contribution to business objectives.
When navigating the complexities of organizational change, leaders often rely on analogies to communicate the journey and keep their teams motivated. One common analogy used in traditional change management is the “light at the end of the tunnel,” which portrays the change process as a long, dark journey with an illuminating endpoint. We explores why the “light at the end of the tunnel” analogy is inadequate, proposes a more accurate depiction, and provides practical tips for developing a clear vision and crafting a compelling narrative to guide your organization through change.
‘The light at the end of the tunnel’ is often used an analogy when describing the change journey. The tunnel describes the change journey, often dark with potential obstacles along the way. People may not know exactly what the end looks like and at times it may feel frustrating and challenging. Eventually, approaching the end of the journey, people start to see the light at the end of the tunnel. Excitement builds and people get more excited and relieved. The end.
The other key reason why people use this analogy is to stress how important it is to engage employees so that they are clear with what the end of the tunnel looks like. Being clear with what the end state looks like is critical for change agents to sustain momentum and energy to want to keep going along the change journey. The ability to ‘see’ the light at the end of the tunnel in your impacted stakeholders is a key indicator of eventual change success. However, this analogy falls short in capturing the dynamic and multifaceted nature of modern organizational transformations.
In reality, the path to successful change management models, guided by change management theory and supported by change management statistics, is more like a tunnel with intermittent windows of light, reflecting the multiple initiatives and milestones that punctuate the journey during the process of change. By adopting this more nuanced analogy, leaders can better communicate the realities of effective change management, maintain momentum, and foster sustained engagement across the organization.
Misleading Simplicity
The “light at the end of the tunnel” analogy suggests a linear, singular path with a single destination. It implies that the journey is uniformly dark and challenging until the very end, where a sudden and complete transformation occurs. This perspective can be misleading for several reasons:
Oversimplification: Organizational change management is rarely a single, straightforward journey. It involves multiple phases, each with its own challenges and victories, including discrete change projects. The analogy fails to account for the complexity and non-linear nature of most change processes, highlighting the need for a better change model.
Unrealistic Expectations: By implying that the journey is mostly dark and only brightens at the end, this analogy can demoralize teams. It suggests that rewards and progress are only visible at the conclusion, which can lead to fatigue and disengagement.
Neglect of Ongoing Progress: The analogy does not recognize the incremental achievements and intermittent successes that occur throughout the change process. These smaller victories are crucial for maintaining motivation and momentum.
Failing to Reflect Reality
In reality, organizational change involves multiple change management initiatives running concurrently, each aimed at improving the current state, challenges, and successes, including evolving business models necessary for business success. These initiatives create a landscape that is far from uniformly dark; instead, it is punctuated with periods of light – moments of clarity, success, and learning.
When there are multiple initiatives the key then becomes to pain the overall picture of what the end of the tunnel looks like. This is not just what the end state of one initiative looks like. It is what the culmination of all the various changes look like. Sometimes it leads to potential change fatigue with information overload and other times the change management process requires more change efforts. This may lead to employee resistance and lack of trust. It is about articulating super clearly what it means to have reached particular milestones within the various strategies undertaken (of which the various changes are aimed to support). This design process may incorporate design thinking concepts to come up with new ways in executing the change management approach.
A More Accurate Analogy: A Tunnel with Intermittent Windows of Light
Embracing the Multifaceted Nature of Change
A more fitting analogy for the change journey is a tunnel with intermittent windows of light. This analogy acknowledges the complexity and multifaceted nature of change. Here’s why it’s more appropriate:
Multiple Initiatives: Organizations often undertake several change initiatives simultaneously. Each initiative represents a different window of light, providing opportunities for progress and insight along the way.
Intermittent Successes: This analogy highlights the importance of recognizing and celebrating interim successes. These windows of light can rejuvenate the team’s spirit and provide evidence that the change is working.
Continuous Learning: Intermittent light symbolizes moments of learning and adaptation. As the organization progresses, these windows provide valuable feedback, allowing for adjustments and improvements.
Sustained Motivation: By acknowledging periodic achievements, this analogy helps sustain motivation. Teams can look forward to these windows of light, making the journey less daunting and more engaging.
Developing a Clear Picture of the End State
Importance of a Clear Vision
A clear and compelling vision is essential for guiding the organization through change and increases the probability of change success. It provides a sense of direction and purpose, helping teams understand the ultimate goal and their role in achieving the desired future state. Here are practical steps to develop and communicate a clear picture of the end state using a structured approach:
Define the Vision: Articulate a clear, concise, and inspiring vision that encapsulates the desired end state. This vision should align with the organization’s values and strategic objectives.
Involve Stakeholders: Engage key stakeholders in the vision development process. Their input and buy-in are critical for ensuring that the vision is relevant and achievable.
Visualize the Future: Create visual representations of the end state, such as diagrams, infographics, or mock-ups. These tools can help make the vision more tangible and relatable.
Break Down the Vision: Decompose the vision into specific, measurable objectives and milestones. This makes the vision more manageable and provides clear targets for the team to aim for.
Communicate Consistently: Regularly communicate the vision and progress towards it. Use multiple channels and formats to ensure that the message reaches all parts of the organization.
Crafting the Story for Your Audience
Tailoring the Narrative
Crafting a compelling story that resonates with different audiences within the organization is crucial for maintaining engagement and momentum. Here’s how to tailor the narrative effectively:
Understand Your Audience: Different groups within the organization will have different concerns, priorities, and levels of influence. Tailor the narrative to address the specific needs and interests of each audience segment.
Highlight Relevance: Explain how the change will impact each audience group. Highlight the benefits and address potential concerns to demonstrate relevance and importance.
Use Relatable Examples: Use examples and stories that resonate with each audience group. Relatable narratives can make the vision more accessible and credible.
Showcase Interim Wins: Regularly share stories of interim successes and milestones. These stories can serve as proof points that the change is progressing and having a positive impact.
Leverage Champions: Identify and empower change champions within each audience group. These individuals can help amplify the narrative and foster a sense of ownership and commitment.
The story can be, and should be, articulated at different levels of the organisation. Senior leaders have a role to play to illustrate what business will look like and how the organisation will function differently. Departmental managers also have a role to play to spell out how the work of the department will change accordingly. Team leaders also need to play a part in deciphering what the changes will look like and how the work of the team will evolve in the future. The managerial skills required in doing this and to help employee join dots is critical and cannot be neglected.
Keeping the Momentum
Maintaining momentum throughout the change process requires continuous effort and strategic communication, including effective communication strategies. Here are some tips to keep the energy and enthusiasm alive:
Celebrate Milestones: Acknowledge and celebrate interim successes and milestones. This not only boosts morale but also reinforces the perception of progress.
Provide Regular Updates: Keep the organization informed about the progress, challenges, and next steps. Transparency builds trust and keeps the team aligned.
Encourage Feedback: Create channels for feedback and actively seek input from the team. This fosters a sense of involvement and helps identify areas for improvement.
Adapt and Iterate: Be prepared to adapt the approach based on feedback and changing circumstances. Flexibility is key to navigating the complexities of change, and it is crucial to anticipate and address resistance to change throughout the process.
Recognize Effort: Regularly recognize and reward the efforts and contributions of individuals and teams. Appreciation and recognition can significantly enhance motivation and engagement, helping employees step out of their comfort zone.
The “light at the end of the tunnel” analogy, while common, fails to capture the true nature of organizational change. A more accurate depiction is a tunnel with intermittent windows of light, reflecting the multiple initiatives, interim successes, and continuous learning that characterize the change journey. By adopting this more nuanced analogy, leaders can better communicate the realities of change, maintain momentum, and foster sustained engagement across the organization.
To navigate the complexities of change effectively, it is crucial to develop a clear vision of the end state and craft a compelling narrative tailored to different audiences. Regularly celebrating milestones, providing updates, encouraging feedback, and recognizing effort are all essential strategies for maintaining motivation and ensuring the successful implementation of change initiatives. By embracing these practices, organizations can not only survive the journey through the tunnel but thrive and emerge stronger on the other side.
Disruptions are all around us. First, the various disruptions with Covid on all aspects of people’s lives around the globe. Now we have the riots across the US as well as other countries about racial inequality. With these, we have the backdrop of constant significant changes and changes in new technologies that constantly challenge how we run our lives. What next you may ask?
Disruptions to how change management initiatives are managed seem to never cease. You think you’ve been through the worst with Covid impacting the budget expenditure on projects and the implementation timeline thrown up in the air due to lack of business capacity. The racial riots are disrupting normal business operations and it is back to business continuity plans for some organizations. How might we continue to manage our various change initiatives amongst these constant disruptions?
Strategic approaches
In being able to effectively respond to constant business disruptions on initiatives, a set of routines and business processes need to take place prior to the individual disruptions. Developing a strategic plan is essential to achieve the desired results and navigate these challenges.
Use the three horizons of growth as a framework to focus efforts on initiatives
McKinsey’s three horizons of growth describe 3 horizons of which initiatives should be clustered. Each horizon forms a critical set of initiatives from which the organisation may continue to develop and grow. If all focus was placed on horizon 1 that are focused on the here and now shorter-term initiatives, then the organisation is not placed to deal with emerging challenges addressed under horizons 2 and 3. Vice versa if all the effort is placed on horizon 3 and not 1.
With business disruptions, the effort and expenditure placed on initiatives can be evaluated in light of which horizon they are in. For example, if the Covid disruption is so significant on the business that it’s a matter of survival, then all efforts should focus on horizon 1 initiatives that contribute to organisational survival in terms of revenue and cost management. If the disruption is significant but not debilitating then it may be wise to spend half of the effort on horizon 1 with the rest on horizons 2 and 3.
Adopt a portfolio approach to manage changes
When initiatives are treated in isolation it is very difficult to flex and adjust to changes compared to a portfolio approach to manage change initiatives. Individual initiatives have limited resource capacity and project activities will have limited impact compared to multiple initiatives.
Having a portfolio approach to manage changes means having established the following:
Data-based approach to manage change impacts with a view of change impacts across initiatives for business leaders.
Ability to visualize and plan the change impacts from a business-unit-centric and stakeholder group centric perspective
Ability to manage resourcing across initiatives so that as required resources may be flexed up or down across the overall portfolio based on prioritisation
Ability to guide and prepare each business for multiple changes across initiatives
Key stakeholder messages may be synchronised and packaged across initiatives versus an initiative by initiative approach
Improved ability to map out clearly the various skills and capabilities being implemented across initiatives to avoid duplication and improve synergies
What can change practitioners contribute in planning for disruptions?
Derive different change scenarios
Scenario planning as a technique is rarely used in a project planning context. However, it is especially critical and relevant within an agile environment. Agile project practices mean that changes keep iterating and therefore it may be hard to anticipate what the end solution or incremental change will look like. It may also be hard to anticipate how the business models and business will respond to the changes being proposed if we don’t know what the changes will look like.
To allow adequate time to plan for changes it is very helpful to derive at least 2 scenarios. In an agile environment, change practitioners need to adopt a hypothesis-based approach to deriving change approaches. Let’s take an example of a standard system implementation project. In rolling out a new system these could be 2 likely scenarios based on the hypothesis being posed.
Hypothesis: The system being implemented is easy and intuitive for users and therefore the change approach will be sufficient with awareness raising and a 1 hour training session
Scenario 1: The hypothesis is true and all users have found it easy and intuitive to use and therefore the change approach proposed is sufficient to prepare the users for this change.
Scenario 2: The hypothesis is only partially true and there are some user groups who struggled to understand all features of the system and need additional help and guidance. Additional training sessions with coaches are proposed
A different way of contrasting different scenarios will be to derive different project expenditures and funding requirements and resulting change delivery work. For example, under the system implementation project, a ‘Toyota’ approach of delivery could involve minimum training and stakeholder awareness generation. For a ‘Rolls Royce’ approach of delivery which will cost significantly more could include tailored coaching sessions for each stakeholder group, 1:1 coaching for senior leaders, a long awareness campaign, and an extensive measurement system. This helps stakeholders understand the cost of delivery and will help them to select an appropriate delivery model.
The usefulness of planning ahead to anticipate for different scenarios mean that steps may be taken to be ready for either of the scenarios and so the project team will not be caught off guard in case the hypothesis proposed is proved false.
To be able to visualize different scenarios it is important to show the different impacts of the scenarios. This includes the impact of time, sequencing, and impact levels on stakeholder groups. With a different rollout approach will stakeholder groups have better bandwidth and ability to adopt the change or will the bandwidth be more limited?
Here is an example of a scenario planning visual where the user can simply drag the impact bars to different times and be able to save this as a scenario. After saving the scenario the next activity will be to analyse the scenario to make sense of the potential impacts of this scenario on the business and impacted stakeholders. Are there project dependencies that need to be taken into consideration? What is the overall change impact across initiatives as a result of the changes in this scenario? How does this impact the customer versus internal stakeholder groups?
For scenarios to be used in a practical way it is important to be able to list any ‘proof points’ that outline how we can tell that the scenario is becoming true or not. These proof points can include anything ranging from stakeholder reactions, the timing of the implementation, the complexity of the features or solution, cost, and other tangible measurements such as system response time, time taken to perform the process, etc.
Agree on decision making principle with stakeholder
Prior to any disruptions, it is important to agree with stakeholders key decision-making principles. Having clear, agreed decision-making principles means that key decisions can be made without subjecting to personal opinions or preferences. During any times of disruption Decision-making principles can be organised as ‘trade-off’ principles with a prioritised order of importance. Below are some examples:
Cost
Time
People resource bandwidth
Benefit realisation
Stakeholder readiness and acceptance
External media implications
Factor in critical path in project planning
The critical path method is a way in which a project’s key interdependencies are linked and mapped out in a linear way so as to understand the key logical points along the project. From this any potential disruptions, slippages or delays in project deliverables and how they impact the remaining deliverables can be clearly understood and planned for.
A clear understanding of the critical path within a project means that with any disruptions to activities the impacts of this on the rest of the deliverables can easily be articulated. To deal with the disruptions to the project a longer implementation may need to be negotiated with the impacted businesses, or depending on the nature of the disruption, a different project approach with different deliverables may need to be derived.
Here we discussed multiple ways in which the change practitioner can help the organisation get ready for various disruptions to change initiatives. During periods of disruptive change, it is even more critical for change practitioners to demonstrate their value to lead and maneuver around and plan for uncertainty. Agile organisations are well placed to deal with disruptions, however, an effective set of routines, practices, preparations, and capabilities are all critical to building overall organisational readiness.
