Most organisations today would not dream of running a marketing function without dashboards, attribution models, and conversion analytics. They would not manage a supply chain without real-time inventory data, nor run an HR function without workforce metrics tracking attrition, engagement, and capability gaps. Yet change management, a discipline that directly shapes whether major investments deliver their intended outcomes, has largely remained opinion-driven, practitioner-intuition-based, and dangerously under-measured.
This is not a minor oversight. Prosci’s research on change management maturity consistently finds that organisations at the lowest maturity levels rely almost entirely on anecdotal judgement to make change decisions, whilst those at the highest levels treat change data as a strategic asset. The gap between these two groups is not just a matter of methodology. It translates directly into project success rates, employee adoption speed, and the return on transformation investment.
Building a data-driven change management environment is not about adding a few pulse surveys or tracking training completion rates. It requires a fundamental shift in how change is designed, measured, and governed across an organisation. This article outlines what that environment looks like across eight core components, and how leaders and practitioners can begin building it intentionally rather than by accident.
Download the framework overview below and keep reading for a detailed breakdown of each component.
Why change management must become data-driven
The argument for data-driven change management is not primarily about technology or efficiency. It is about credibility and accountability. When a CFO asks a change lead to demonstrate the impact of their work, or when a programme board needs to decide whether to accelerate, pause, or redesign an initiative, gut-feel and experience alone are not sufficient. Other business disciplines have moved well past this point.
McKinsey research on data-driven organisations has consistently shown that companies making decisions anchored in data and analytics outperform their peers on profitability, productivity, and agility. The same logic applies within change management. When practitioners can demonstrate, through data, that a particular stakeholder group is under-supported, that change saturation is spiking in a specific business unit, or that adoption of a new system has plateaued despite training completion, they are in a fundamentally stronger position to influence decision-making and resource allocation.
The opportunity is also significant from a risk management perspective. Gartner has identified that organisations which systematically measure change adoption and resistance are better placed to detect early warning signals before they become programme-threatening issues. Without data, change teams are essentially navigating blind, responding to crises after they have already formed rather than anticipating and mitigating them in advance.
Components 1 and 2: Portfolio data capture and a data-driven approach through all project phases
The first and most foundational component of a data-driven change environment is the systematic capture of data across both individual initiatives and the full change portfolio. This distinction matters enormously. Many organisations collect some change data at the project level, such as survey results for a single rollout, but almost none aggregate and analyse that data at the portfolio level to understand cumulative impact, change load, and cross-initiative dependencies.
Portfolio-wide data allows change leaders to answer questions that project-level data simply cannot. Which business units are carrying the highest volume of change concurrently? Which employee segments are being asked to adopt multiple new systems, processes, or ways of working simultaneously? Where is change fatigue most likely to undermine adoption? Without this aggregated view, organisations routinely overload their most critical teams while leaving others underutilised, and they only discover the problem when attrition spikes or project benefits fail to materialise.
The second component is ensuring that data collection is not a one-off activity conducted at project close, but rather a discipline embedded throughout every phase of a project. From the initial scoping of an initiative through to post-implementation review, data should be informing decisions at each gate. During the design phase, this means capturing baseline data on current-state capability and readiness. During implementation, it means tracking adoption indicators in near real-time. During stabilisation, it means measuring the sustainability of change rather than simply declaring victory at go-live.
Organisations that do this well treat their change data with the same rigour as financial data. They define what will be measured before the project starts, assign accountability for data collection, and build reporting cycles into the project governance rhythm rather than bolting them on as an afterthought.
Components 3 and 4: User-centric perspectives and building insight capability
The third component requires a fundamental reorientation in how change data is framed and interpreted. Most project teams collect data from a project-centric vantage point, asking questions like “how well is our project being received?” or “what percentage of users have completed training?” These are useful metrics, but they are centred on the project’s needs rather than the employee’s experience.
A user-centric or business-centric approach asks different questions. It asks what the total change experience looks like from an individual employee’s perspective. It asks how many initiatives are simultaneously demanding their attention and behavioural adaptation. It considers the emotional and cognitive load being placed on people, not just the logistical progress of a project. Harvard Business Review research on digital transformation has found that employee experience during change is one of the strongest predictors of whether new capabilities are actually embedded or quickly abandoned once the change team moves on.
This shift from project-centric to user-centric data collection requires both a change in mindset and a change in measurement design. It means segmenting data by employee group, role, and location rather than by project milestone. It means tracking the cumulative volume of change hitting specific teams and correlating that with engagement and performance indicators. And it means building feedback loops that give employees a genuine voice in how change is being managed, not just a satisfaction score collected after the fact.
The fourth component is the investment required to build genuine insight capability within change teams and across the organisation more broadly. Collecting data and generating insight from it are two entirely different things. Many organisations have more change data than they realise, sitting in pulse survey results, help desk tickets, training completion systems, and performance dashboards. The challenge is synthesising that data into actionable intelligence.
Building this capability means investing in the analytical skills of change practitioners, providing them with the tools to visualise and interrogate data, and creating the time and space to reflect on what the data is telling them. It also means establishing clear processes for translating insights into recommendations and ensuring those recommendations reach the people with authority to act on them. Without this investment, data collection becomes an administrative exercise rather than a strategic advantage.
Components 5 and 6: Leadership sponsorship and a culture of data sharing
Data-driven change management will not take hold without visible and sustained leadership sponsorship. This is the fifth component, and it is often the most underestimated. Leaders who publicly champion data-led decision-making in change create permission for their teams to invest the time and resources required. Leaders who default to intuition and experience, regardless of what the data shows, effectively signal that the data exercise is performative.
Sponsorship in this context is not just about approving a budget line for analytics tools. It is about leaders actively using change data in their own decision-making. When a senior executive asks the change team to present data-informed insights at a programme board rather than a traffic-light status report, they are modelling the behaviour they want to see. When a CEO references change readiness data in a town hall, they signal to the organisation that this information is taken seriously at the highest levels.
Prosci’s longitudinal research on change sponsorship has repeatedly found that active and visible executive sponsorship is the single most important contributor to change success. When that sponsorship is explicitly directed at data-led investment and focus, it accelerates the maturation of the entire change capability.
The sixth component addresses one of the most culturally challenging aspects of data-driven change: the willingness to share data openly across project teams, business units, and functions. In many organisations, change data is treated as proprietary to the team that collected it, hoarded because it is seen as a source of competitive advantage internally, or withheld because it reveals uncomfortable truths about how a project is tracking.
A genuinely data-driven change environment requires a culture of openness and collaboration around data. This means that a project team running an ERP rollout shares its adoption and readiness data with the team managing a concurrent process redesign, so that both teams can coordinate their demands on shared employee groups. It means that lessons learned from one initiative are captured in a structured and accessible format and drawn upon by the next. And it means that underperformance revealed by data is treated as a prompt for problem-solving rather than a source of blame.
Components 7 and 8: Embedding data in meetings and governance structures
Even when an organisation has invested in data collection, analytical capability, and leadership sponsorship, it is surprisingly common for that data to live in reports and dashboards that nobody regularly reads. The seventh component of a data-driven change environment is the deliberate embedding of change data into the routine meeting cadences of the business. Data that is not discussed is not used.
In practice, this means that change readiness and adoption data appears as a standing agenda item in programme steering committees, leadership team meetings, and operational forums. It means that when a business unit leader reviews their team’s performance in a monthly operations meeting, change capacity and load data is part of that conversation alongside financial and operational metrics. It means that the language of data-driven change becomes normalised in everyday business discourse rather than confined to specialist change team conversations.
This requires a degree of simplification in how change data is presented. Complex analytical outputs need to be distilled into formats that are genuinely accessible to busy senior leaders. The most effective organisations develop one-page change dashboards that surface the three or four metrics that matter most at any given point in the programme lifecycle, rather than overwhelming decision-makers with every data point collected. The goal is to make it easier to use the data than to ignore it.
The eighth and final component is the formalisation of data governance within change management roles and responsibilities. This is where data-driven practice becomes institutionalised rather than dependent on the enthusiasm of individual practitioners. Data governance in a change context means clearly defining who is responsible for collecting which data, at what intervals, using what methodology, and for what audience. It means establishing quality standards for change data, including consistency of definitions across projects so that portfolio-level analysis is meaningful. And it means building accountability into role descriptions and performance conversations, so that data stewardship is treated as a professional responsibility rather than an optional extra.
Organisations that have formalized this governance typically assign data responsibilities within change roles at different levels. Senior change leaders own the portfolio data framework and reporting to executive audiences. Project-level change managers own data collection and insight generation for their initiative. Change champions and business-side partners carry responsibility for ground-level data quality and feedback loop management. Without this clarity, data governance defaults to whoever happens to be most interested, which means it often falls away under delivery pressure.
The barriers to building a data-driven change environment
Understanding the eight components is considerably easier than implementing them, and it is worth being honest about the barriers that most organisations will encounter.
The most pervasive barrier is cultural. Change management has historically been positioned as a “soft” discipline, grounded in psychology, communication, and human relationships. Some practitioners actively resist data-driven approaches on the grounds that human experience cannot be reduced to metrics. This tension is real, but it is also a false dichotomy. Data does not replace human judgment. It informs it. The most effective change practitioners are those who can hold both the quantitative and qualitative dimensions of change simultaneously, using data to identify where to focus their human-centred attention.
The second barrier is structural. Change management in many organisations sits at the project level, with no central function, no shared data infrastructure, and no mandate to aggregate information across initiatives. Building a portfolio-level data capability requires either a centralised change function with the authority to set standards and collect cross-project data, or a federated model with strong governance and coordination mechanisms. Neither is trivial to establish, particularly in organisations where change management is resourced ad hoc through consulting arrangements.
The third barrier is technical. Many organisations lack the tools to collect, consolidate, and visualise change data at scale. Pulse surveys run through different platforms, training data sits in an LMS, adoption metrics are buried in IT service desk records, and change assessments are locked in PowerPoint presentations. Without a common platform or at least a clear data integration approach, the burden of assembling a coherent picture falls on individual practitioners who are already stretched.
Finally, there is the time and investment barrier. Building a data-driven change environment is not a project with a start and end date. It is a capability development journey that requires sustained investment in tools, skills, processes, and cultural change. Organisations that treat it as a quick win or a one-time technology implementation invariably find that the change does not stick. The same principles that apply to any complex organisational change apply here: clear sponsorship, sustained focus, and a realistic timeline.
How The Change Compass supports the data-driven change model
For organisations working to move from intuition-driven to evidence-driven change practice, The Change Compass provides a purpose-built platform designed around exactly the eight components outlined above. It enables change teams to capture initiative and portfolio-level data in a consistent format, visualise cumulative change load by business unit and employee segment, and track adoption and readiness across the programme lifecycle. Critically, it presents this data in formats designed for both change practitioners and senior leaders, making it practical to embed change metrics into the governance and meeting structures that drive organisational decisions. For teams building or maturing their data-driven change capability, it removes the burden of building bespoke data infrastructure from scratch, so practitioners can focus on generating insight and influencing decisions rather than managing spreadsheets.
Frequently asked questions
What does a data-driven change management environment mean in practice? A data-driven change management environment is one where decisions about how to design, resource, and adjust change programmes are grounded in evidence rather than practitioner intuition alone. It encompasses the systematic collection of data across individual initiatives and the full change portfolio, the development of analytical capability to generate insight from that data, and the embedding of change metrics into routine governance and leadership conversations.
What are the most important metrics to track in change management? The most critical metrics vary by phase, but typically include change load and saturation by employee group, stakeholder readiness scores, adoption indicators such as system usage or process adherence rates, and sentiment measures captured through pulse surveys. Portfolio-level metrics that aggregate these data points across concurrent initiatives are particularly valuable because they reveal cumulative impacts that project-level reporting misses entirely.
How do you build a change management data capability without a large team? Start with consistency rather than comprehensiveness. Define a small set of standard metrics that every change initiative will collect, establish a shared reporting template, and create a simple mechanism for aggregating data at the portfolio level. Even a modest capability built on common definitions and shared tools will generate far more insight than a sophisticated approach that is inconsistently applied across projects.
Why is leadership sponsorship critical for data-driven change? Leadership sponsorship shapes what is taken seriously in an organisation. When senior leaders actively request and use change data in their decision-making, they signal to the rest of the organisation that this information has strategic value. Without that signal, data collection efforts are often deprioritised under delivery pressure, and the insights generated by change teams fail to reach the people with authority to act on them.
The past 1.5 years has been super challenging for most organisations. The constant stop and start interruptions of Covid has taken a toll on most employees. One minute we are going back to work the next minute we are not. One minute we have Covid cases under control, the next minute infection rates are out of control.
However, corporate initiatives are not in any way slowed down by Covid. If anything there is more organisational change resulting from Covid. Covid has not only resulted in ways of working changes, but also deep industry, economy, consumer and technology changes.
Now that most economies are starting to come out of lockdowns and opening up, what does this mean for initiatives? Well, amidst the atmosphere of the emotional and psycho-social turmoil that has been the journey for most employees as a result of COVID, the most important change approach can be summarised by one word ….
OPTIMISM
Why is it important to incorporate a sense of optimism within every change initiative?
After more than a year of being isolated and experiencing the various disruptions of not being able to have a normal life of shopping, visiting friends and travelling, we need to acknowledge and reset the mood. How we approach work is indeed affected by the overall mood around us. Resetting the mood and instilling a sense of positivity and optimism is absolutely critical.
Without optimism, employees may still be harbouring the lingering mood of dealing with Covid. Negativity will never help to transition people during the change process. It is hope and optimism that will carry energy and excitement which will then drive action.
Think of the last time you were feeling down and weary. What were some of your behaviours? Typical behaviours when you’re feeling down in the dumps include not connecting with family and friends, being socially withdrawn, disruptions in sleep, being less physically active, etc. You were also more likely to think negatively, such as “things won’t get better”, “there’s no point trying”, “might as well not try”. These are definitely not the thoughts and behaviours that will help people transition during the change process.
So how do we instil a sense of optimism within our change initiatives?
1. Celebrate the ‘return to normal’ (whatever normal looks like!). As companies start to gradually have employees return to work, initiatives must also support this by creating a sense of excitement and positivity. Think of approaches such as:
Uplifting speeches by leaders
Gift objects such as cupcakes and drinks as a part of the celebration theme
Online events promoting positive discussions and sharing
Social events fostering activity and excitement
2. Highlight new ideas and approaches to the initiative. To demonstrate that things are no longer just ‘ho-hum’ as was the case during Covid, adopt new engagement and communication approaches to liven up the initiative. Even better, ask impacted stakeholders to come up with bright ideas of how to generate a renewed sense of optimism
3. Leverage the power of communication to impart excitement and positivity. Incorporate bright and colourful images, quotes and graphic themes to instil positive energy.
4. Display consistent behaviour. There is nothing worse than having positive themes throughout, only to have initiative leads speak with monotone voice supplemented by lethargic behaviour. We are social animals. We can ‘smell’ low energy. You may need to proactive coach your leaders to ensure that they are displaying the right behaviours across all modalities …. The tone of voice, gestures, responses, reactions, etc. All aspects of behaviour can impart mood. And your job is to design and shape them to be one that is more positive.
Adopting a behavioural science approach to managing behaviour change means leveraging scientific research about human behaviours and using this to better manage employee behaviour and change. A lot of the common practices in change management are not always based on scientific research. What is assumed as common change approaches may in fact not be substantiated by research and data.
A behavioural science approach to managing change recognizes that successful change initiatives require more than just new processes or training programs—they hinge on shifting employee behaviour and embedding new behaviours across the organization. By drawing on evidence-based insights, such as the transtheoretical model, change practitioners can better understand how individuals move through stages of personal growth and adopt new ways of working. This approach underscores the crucial role of leadership, with the executive team and direct reports acting as role models who demonstrate and reinforce desired behaviors. Engaging small groups and the wider workforce in the process ensures that behavioural change is not only top-down but also authentic and sustainable, addressing the way people perceive and respond to organizational change over the long term.
Moreover, involving employees in both the design and reporting of change efforts fosters ownership and helps weave multiple changes into the fabric of the organization. Performance reviews and ongoing reinforcement are essential for sustaining new behaviors and achieving better outcomes. By prioritizing human-centric design and leveraging the power of relationships—such as the nature of leadership relationships and the influence of peer networks—organizations can create an environment where behavioural change is not just a one-off initiative but a continuous process aimed at long-term success.
How to create a behavioral and cultural shift?
To create a behavioural and cultural shift, engage stakeholders through open communication, set clear objectives, and model desired behaviours. Encourage feedback and recognize progress to reinforce the change. Additionally, provide training and resources to support individuals as they adapt, ensuring a cohesive transition towards the new culture.
We talk to an industry veteran of behavioural science, Tony Salvador. Tony has 30+ years of research background behind him and a long-time ex-Inteller and Senior Fellow. At Intel, Tony travelled around the globe researching human factors and how people behave with technology.
There are many valuable takeaways for the change practitioner.
Some of these include:
Engineering psychology and human centric design
Analogy of pickaxe and the change approach
Principle of aversion to loss
People involvement and transactional change
Determining the nature of leadership relationship with employees
Story telling and insight into change culture
Example of Brazilian translator and people’s stories
Power of observation and listening
The nature of relationships and how they determine change
Change rationale in weaving in multiple changes
Involving people in reporting to achieve authenticity
Building the case and involving employees to derive case for change
Research on aversion to loss can explain why people don’t want to change. I spoke with Senior Fellow, anthropologist and ex-Inteller Tony Salvador.
It sounds completely illogical but true ….
This plays out in various facets of how people make decisions about choices … including in a change transformations context.
This is just one of the many things I spoke with Tony Salvador about.
Change aversion is a powerful psychological concept rooted in loss aversion, where individuals tend to fear losing what they have more than they value gaining something of equal magnitude. This phenomenon plays a significant role in why many people resist new changes, whether in their personal lives or within organizations, and particularly affects how product managers, leaders, and customer-facing teams approach change initiatives. It impacts their decision-making processes heavily, especially when they perceive potential losses that could overshadow a gain of equal magnitude.
At the individual level, the degree of change aversion varies depending on personal circumstances and perceptions. Original research grounded in Prospect Theory explains that people evaluate potential changes not just by the prospective benefits but by the risks of losing familiar routines, status, or comfort. For example, individuals are often more concerned about losing $2 than they are motivated by the prospect of gaining $5, because the psychological impact of loss outweighs that of an equivalent gain. This loss aversion creates an emotional barrier that can prevent even well-intentioned changes from being embraced.
The effects of change aversion can be observed in many contexts, including business transformations and customer satisfaction. For product managers, understanding this aversion is crucial when introducing new features or product updates. Despite best intentions customers might resist changes that disrupt their habitual usage or create uncertainty – even when these changes offer clear improvements or potential benefits. This reluctance can negatively impact customer feedback and satisfaction because the change is perceived as a threat rather than an opportunity, despite significant change efforts.
One helpful point of reference for managing change aversion is recognizing that the degree of aversion is not uniform. Organizational change studies show that people feel more averse to changes imposed upon them (such as being assigned new tasks) than to changes they self-initiate (like managing their own time differently). This highlights the importance of agency in the change process. When employees or customers feel involved or have some control, their resistance diminishes.
The potential benefits of understanding and addressing change aversion are profound. Company leaders who communicate transparently about what changes mean, acknowledge possible losses, and provide support and resources can create an environment where people feel safer to engage with change. This approach can be extended to personal lives, for example, in maintaining new year’s resolutions where individuals face their own internal resistance rooted in loss aversion to giving up old habits or comforts.
Moreover, energetic speeches or inspirational messaging via emails can sometimes fail to overcome change aversion if they neglect the underlying psychological resistance. Instead, effective change management embraces empathy and addresses the emotional loss individuals perceive. This understanding is particularly vital for product managers relying on customer feedback to refine changes, as they must balance the introduction of innovation with the human tendency to resist disruption.
In summary, loss aversion explains why change feels threatening and why resistance often arises despite good intentions and clear advantages of the new change. By acknowledging the psychological concept of change aversion and its individual variability, organizations and individuals can better design, communicate, and implement changes that minimize resistance and maximize acceptance and satisfaction.
This nuanced understanding provides a valuable toolkit for navigating change in both organizational settings and personal lives, helping transform resistance into openness and enabling progress despite the natural human tendency toward aversion to loss.
Lots of golden nuggets of wisdom takeaways for change practitioners from the man who spent 30+ years working for Intel researching about people behaviour and how they operate in social and technological environments.
Stay tuned for the full recording.
Why do people oppose change?
People often oppose change due to change aversion, a psychological tendency where individuals fear losing what they already possess. This resistance is rooted in the discomfort of uncertainty and potential negative outcomes. Understanding this can help leaders implement strategies to ease transitions and foster acceptance within teams.
When organisations roll out a new system or digital tool, the default playbook tends to look something like this: schedule a training session, send a few announcement emails, hold a town hall or go-live event, and then declare the project complete. It is a familiar pattern, and it is one that consistently fails to produce the outcomes that organisations need. Completion rates for training modules say little about whether people are actually using the new system in their day-to-day work. Attendance at a launch event does not translate into changed behaviour at the desk. The gap between “we trained everyone” and “everyone is using the system effectively” can be enormous, and it is precisely this gap that derails the return on investment for so many technology and transformation programmes.
The root cause of this gap is a fundamental misunderstanding of what user onboarding actually requires. Onboarding is not a moment in time. It is not a box to tick. It is a multi-stage process that unfolds over weeks and months, requiring deliberate effort across a range of levers that together determine whether adoption becomes embedded in the organisation or quietly fades after the initial excitement. Research from Prosci consistently shows that projects with excellent change management are six times more likely to meet their objectives than those with poor change management – yet most organisations still treat onboarding as a communications and training exercise rather than a full change management process.
Full adoption – the kind where people are confident, willing, and consistently using a new system in ways that deliver business value – requires addressing at least eight distinct levers: user capability, user motivation, user capacity, senior manager buy-in, line manager buy-in, communication and awareness, measurement and reinforcement, and strategic alignment. Miss any one of these, and adoption will remain partial at best. This article explores each lever in depth and offers a practical framework for designing an onboarding journey that achieves sustainable, organisation-wide change.
The event-based model of onboarding has its roots in a reasonable intuition: people need information before they can use something new, so give them that information in a structured setting and they will be ready to go. The problem is that adult learning and behaviour change are far more complex than this model assumes. A single training session, however well designed, provides exposure – but exposure is not the same as competence, and competence is not the same as adoption. People need repeated practice, contextualised support, and the confidence that comes from doing something real, not just simulated, before new behaviours become habitual.
Gartner research on digital workplace adoption has highlighted that most technology investments underperform because organisations focus almost entirely on the technical deployment and the go-live moment, while underinvesting in the sustained behaviour change work that happens afterwards. The post-go-live period – typically the first 90 days – is where adoption is either won or lost, yet it is precisely this period that receives the least structured attention in most programme plans. Change management activity drops off just as employees are encountering real-world friction, forming habits, and deciding whether the new way of working is genuinely worth the effort.
Thinking of onboarding as a journey rather than an event reframes the entire challenge. It shifts the question from “did we deliver training?” to “are people using the system confidently and consistently?” It moves the success metric from outputs (training completion, attendance) to outcomes (usage rates, error rates, productivity metrics, user satisfaction). And it creates the organisational mandate to sustain change management activity well beyond go-live, which is where real adoption is ultimately built.
The eight levers of full user adoption
Achieving full adoption requires organisations to work across eight interconnected levers simultaneously. These are not sequential steps but parallel dimensions of the onboarding journey, each of which must receive deliberate design and ongoing attention throughout the adoption lifecycle.
User capability is the most obvious lever – people need to know how to use the system. But capability goes beyond knowing where to click. It encompasses conceptual understanding of why the system works the way it does, procedural fluency in completing tasks efficiently, and the confidence to troubleshoot when things do not go as expected. User motivation is equally foundational. Even highly capable users will revert to old ways of working if they do not see a compelling reason to change. Motivation is shaped by how clearly the benefits of adoption are communicated in terms that are personally relevant to each user group, not just in terms of organisational efficiency.
User capacity is a lever that is frequently overlooked. Employees may be capable and motivated to use a new system, yet lack the time and mental bandwidth to develop proficiency during a busy period. If adoption is competing with peak workloads or concurrent change initiatives, it will consistently lose. Senior manager buy-in and line manager buy-in are the two sponsorship levers, and they operate quite differently. Senior leaders shape the strategic narrative and signal organisational priority; line managers shape the day-to-day environment in which people actually change their behaviour. Communication and awareness, measurement and reinforcement, and strategic alignment round out the framework, ensuring that adoption is visible, tracked, and connected to the organisation’s broader direction of travel.
Building user capability and confidence
Effective capability building starts well before go-live and continues long after it. The pre-launch phase should focus on building awareness and foundational understanding – what is changing, why it matters, and what it will mean for each role. This is distinct from system training, which is most effective when delivered as close to the point of first real use as possible. Training delivered weeks before go-live is largely forgotten by the time it is needed, a finding that is well-established in learning science and confirmed repeatedly in enterprise technology deployments.
Learning design for onboarding should be role-specific, scenario-based, and layered. Generic system overviews are far less effective than task-focused modules that walk users through the exact workflows they will use in their specific jobs. Scenario-based learning – where participants practise in realistic simulations before working with live data – builds procedural fluency in a low-stakes environment. Layered learning, where foundational skills are covered at go-live and more advanced capabilities are introduced over the following weeks, respects the cognitive reality that people can only absorb so much at once.
Confidence is the bridge between capability and consistent use. Many users who have completed training still hesitate to use a new system in real situations because they are not confident they will get it right. Support mechanisms in the post-go-live period – floor walkers, super-users embedded in teams, easily accessible help resources, and a psychologically safe environment where asking questions is normalised – are as important as the training itself. A McKinsey study on large-scale transformation programmes found that organisations that invested heavily in on-the-job support during the first 90 days post-launch achieved adoption rates that were significantly higher than those that relied on classroom training alone.
The critical role of manager buy-in
Of all the levers in the onboarding framework, manager buy-in at both the senior and line manager levels may be the most powerful and the most underdeveloped in practice. Prosci’s research on change management best practices consistently identifies active and visible sponsorship as the single most important contributor to successful change outcomes – yet sponsorship is often confused with endorsement. A senior leader who approves a project and appears at the launch event has provided endorsement. What they need to provide is active, ongoing, visible engagement: talking about the change in team meetings, asking questions about adoption progress, removing barriers when they arise, and role-modelling the new behaviours themselves.
Line managers are the proximate influence on employee behaviour. Employees take their cues from their direct manager about what is genuinely important, what will be rewarded, and what can safely be deprioritised. When line managers actively support adoption – checking in on how team members are finding the new system, making time for practice and questions, celebrating progress – adoption accelerates. When line managers are neutral or disengaged – perhaps because they were not adequately prepared for their role in the change – adoption stalls even when users have received excellent training.
Preparing managers for their adoption role requires specific attention. Many managers have deep expertise in their functional domain but have not been equipped with change leadership skills. An effective onboarding programme includes a specific workstream for managers: helping them understand the adoption journey their teams will experience, giving them language and tools to have productive conversations about the change, and keeping them informed of adoption data so they can act on it. When line managers become active agents of adoption rather than passive recipients of communications, the impact on outcomes is substantial and sustained.
Measurement and reinforcement as adoption drivers
What gets measured gets managed – and in the context of user adoption, this principle is not merely a cliche but a practical necessity. Organisations that track adoption metrics systematically are able to identify where the journey is breaking down, intervene before disengagement becomes entrenched, and demonstrate the value of their change management investment to senior stakeholders. Organisations that rely on training completion rates as their primary adoption metric are flying blind, because completion tells you nothing about whether the learning transferred into changed behaviour.
A robust adoption measurement framework tracks leading and lagging indicators across the adoption journey. Leading indicators – the precursors to adoption – include training completion, awareness levels (measured through pulse surveys), manager engagement scores, and the volume and nature of support requests. Lagging indicators – the actual adoption outcomes – include system usage rates by role and team, error rates, productivity metrics, and user satisfaction scores. Together, these data points paint a picture of where adoption is strong and where it needs additional support.
Reinforcement is the sustained activity that converts early adoption into embedded habit. According to research published in the Harvard Business Review, behaviours that are reinforced through recognition, feedback, and accountability are far more likely to stick than those that are simply trained and left to self-sustain. Reinforcement mechanisms in an onboarding journey include celebrating adoption milestones publicly, incorporating system use into performance conversations, updating processes and job aids so that the new way of working is embedded in documented procedures, and periodically refreshing skills as the system evolves. Reinforcement is not a one-time activity but an ongoing practice that spans the full adoption lifecycle.
Designing an onboarding journey for your organisation
Designing an effective onboarding journey begins with understanding the adoption landscape for the specific change. Not all systems affect all users in the same way, and not all user groups will face the same adoption challenges. A thorough impact assessment – identifying which roles are affected, how significantly their work will change, what capability gaps exist, and what motivational barriers may arise – is the foundation of a well-targeted onboarding plan. Without this analysis, organisations tend to apply a generic approach that works reasonably well for the easiest-to-adopt groups and fails the groups that most need support.
The onboarding journey should be mapped as a timeline with clear phases: awareness and readiness (pre-go-live), active adoption (the first 30-60 days post-go-live), and embedding and reinforcement (60-180 days and beyond). Each phase has different objectives and requires different interventions. The awareness phase focuses on building a compelling case for change and preparing the organisation to receive and use it. The active adoption phase delivers training, floor support, and manager engagement at the moment of real use. The embedding phase shifts focus to reinforcement, measurement, and continuous improvement.
Strategic alignment – the eighth lever – means ensuring that the onboarding journey is designed in the context of the organisation’s broader change portfolio and strategic priorities. If the new system is one of five significant changes landing on the same population in the same quarter, user capacity will be stretched and motivation will be harder to sustain. Understanding the change landscape and sequencing or pacing adoption activity accordingly is a strategic decision that sits above the programme level and requires executive attention. Organisations that manage their change portfolios deliberately are consistently more successful at achieving individual adoption outcomes because they protect the cognitive and emotional capacity their people need to change.
How The Change Compass supports the full onboarding journey
The Change Compass is a purpose-built platform designed to help organisations manage the complexity of change at scale, and this directly supports the full user onboarding journey described in this article. At its core, The Change Compass gives change leaders and senior managers a clear, data-driven view of the change landscape across the organisation – who is being affected by what, when, and at what intensity. This portfolio-level visibility is the foundation for making strategic decisions about sequencing, pacing, and resourcing adoption activity for individual systems and tools.
For onboarding programmes specifically, The Change Compass helps organisations track adoption levers systematically, identify at-risk populations before disengagement becomes entrenched, and provide managers with the information they need to fulfil their sponsorship role effectively. The platform’s change impact data makes it possible to have evidence-based conversations with senior leaders about where adoption support is most needed, making the case for sustained investment in the embedding phase rather than allowing change management activity to drop off after go-live.
By connecting the onboarding journey to the broader change portfolio, The Change Compass also helps organisations protect user capacity – ensuring that adoption of a new system is not sabotaged by competing demands from other concurrent changes. This is a dimension of adoption planning that is almost impossible to manage without the kind of cross-programme visibility that a dedicated platform provides. The result is an onboarding experience that is not only better planned but better sustained, delivering the full adoption outcomes that justify the investment in new systems and tools.
Frequently asked questions
How long should a user onboarding journey last?
The duration of an onboarding journey depends on the complexity of the system, the extent of the behaviour change required, and the size and diversity of the user population. As a general guide, the active adoption phase spans the first 60 days post-go-live, and the embedding phase extends to at least 180 days. For highly complex systems or large-scale deployments, structured adoption support may continue for 12 months or more. The key signal that the embedding phase can be scaled back is sustained, consistent usage rates across user groups – not the passage of a fixed amount of time.
What is the difference between user adoption and user engagement?
User adoption refers to the extent to which people are using a new system or tool in place of previous ways of working – it is fundamentally about behaviour change. User engagement refers to the quality and depth of that use – whether people are using the system confidently, efficiently, and in ways that realise its full capability. Both matter. High adoption with low engagement (everyone logs in but few use advanced features) leaves value on the table. A well-designed onboarding journey addresses both, building adoption first and deepening engagement over time through progressive capability development and reinforcement.
How do you measure whether onboarding has been successful?
Success in onboarding is measured against the adoption outcomes defined at the outset of the programme, not against activity metrics like training completion or event attendance. Meaningful measures of onboarding success include system usage rates by role and team (compared against targets), error rates and support ticket volumes (trending down over time), user confidence and satisfaction scores (measured through pulse surveys), and ultimately the business outcomes that the system was intended to deliver – whether that is processing efficiency, data quality, customer experience, or another value driver. Establishing baseline measures before go-live and tracking them through the adoption journey is essential to demonstrating value and identifying where intervention is needed.
What is the most common reason user adoption fails?
The single most common reason user adoption fails is the premature withdrawal of change management support after go-live. Organisations invest heavily in the lead-up to launch and then assume that adoption will sustain itself once the system is live and users have been trained. In reality, the post-go-live period is where the hardest adoption work happens – where users encounter real-world friction, form habits, and decide whether the new way of working is worth sustaining. Without structured support, reinforcement, and active manager engagement during this period, many users revert to workarounds or old systems. Sustained investment in the embedding phase is the most reliable way to protect the gains made in the active adoption phase.
Gartner. (2022). How to Drive Digital Adoption in the Workplace. Gartner Research. https://www.gartner.com/en/information-technology/insights/digital-workplace
