Change governance maturity varies widely across organizations – from those with established PMOs and formal governance structures to others that rely on existing operational and executive forums without formal change governance setups. Change managers must tailor their influence strategies to fit this maturity spectrum while empowering governance that supports change transformation success. Here we outline practical tips and approaches relevant whether you operate within high-maturity governance or in environments still building foundational capabilities.
1. Leverage Governance Dexterity – Adapt to Your Maturity Context
For organizations with mature PMOs and governance:
Encourage maintaining cadence with purpose – weekly flash checks for quick updates, monthly value reviews to keep benefits front of mind, and quarterly strategic moments for big-picture alignment and celebration. This reduces fatigue and keeps governance tightly connected to business outcomes.
Share frameworks that provide agility within formal governance so cadence remains flexible without diminishing control. For example, leverage agile change management principles to:
Embedding lightweight, iterative review processes that emphasize timely feedback and rapid decision-making without heavy documentation or unnecessary meetings.
Using tools like RACI matrices and decision-rights grids to clarify who has authority and responsibility, so governance can flex in how often or how deeply it engages, but never loses accountability.
Allowing governance forums to scale their activity up or down based on change program phase, risk, or complexity, rather than sticking to a rigid calendar or process.
For less mature organizations without dedicated governance forums:
Propose leveraging existing operational or executive forums to introduce lightweight governance rhythms that do not overburden people. For example, brief monthly check-ins during established leadership meetings or quarterly presentation slots to highlight change progress and risks.
Use simple tools like cadence checklists or short-status emails tailored for existing leaders who may not be change specialists. Position these rhythms as value-adds to existing meetings to gain buy-in.
Practical tips:
Offer templates for flash checks and value meetings that can be easily integrated into the existing meeting culture.
Advocate building urgency without burnout by linking cadence to visible outcomes rather than just process compliance.
2. Drive Enterprise PMO & Portfolio Alignment – Fit Your Organization’s Governance Model
For organizations with established PMOs:
Partner closely with PMO and portfolio managers to ensure change work is fully integrated. Act as a bridge between change activities and portfolio governance to align priorities effectively.
Encourage shared dashboards that combine project and change metrics, giving leadership clarity on both deliverables and adoption risks.
Advocate for change governance representation in portfolio decision forums to embed change risk and opportunities in prioritization.
For organizations without formal PMOs:
Identify operational units or executive groups with portfolio oversight responsibilities and seek informal relationships with key members.
Suggest practical ways to leverage existing governance bodies for change oversight by embedding change highlights in their agenda.
Provide simple portfolio mapping or status tools that don’t require heavy infrastructure but help visualize transformation across initiatives.
Practical tips:
Offer to co-create change input templates that non-PMO forums can use to review change risk, interdependencies and impact.
Share success stories illustrating how integrated PMO-change governance drives consistent messaging and prioritization.
3. Shape Executive Reporting – From Insight to Influence
For organizations with mature reporting processes:
Help refine executive dashboards by ensuring a balance between project status and change readiness/adoption metrics.
Coach change teams to translate data into compelling narratives that highlight risks, opportunities, and decision points.
Push for reporting formats that enable proactive governance action rather than reactive compliance.
For organizations with limited or no formal executive reporting:
Influence existing executive communications by proposing change-related content for leadership newsletters, briefings, or standing meeting updates.
Develop concise, jargon-free reports that fit into current executive reading habits and spotlight what matters most.
Advocate for simple visual reporting tools, e.g., impact bar charts or risk registers that executives can quickly interpret.
Practical tips:
Provide sample executive report templates tailored for different maturity levels.
Offer coaching sessions on storytelling with data to change teams who may be new to executive reporting.
4. Champion Scenario Planning to Build Resilience
Scenario planning is a powerful tool that helps organizations prepare for uncertainty by imagining multiple plausible futures, assessing their impact, and planning appropriate responses. For change practitioners, influencing scenario planning within change governance is critical to making transformation resilient to volatile conditions and unexpected challenges.
For organizations with mature change governance and PMO structures:
Advocate for formal inclusion of scenario planning in governance cycles, such as quarterly strategy reviews or portfolio risk assessments.
Collaborate with PMO, risk, and strategy functions to develop integrated scenario frameworks that tie external uncertainties with change delivery risks.
Use structured tools and templates to develop 2-3 distinct scenarios based on critical uncertainties impacting change programs (e.g., regulatory shifts, technology adoption rates, cost pressures, market dynamics).
Ensure scenario outputs include clear implications for adoption risk, resource allocation, and contingency triggers to inform governance decision-making.
For organizations with limited formal governance:
Promote lightweight scenario planning approaches that can fit into existing forums or leadership discussions without requiring new committees.
Facilitate workshops or brown bag sessions with key stakeholders to brainstorm “what-if” scenarios that highlight risks and opportunities in their own language.
Use simple scenario templates capturing scenario description, key assumptions, impacts, and early warning signs to keep the process manageable and relevant.
Position scenario planning as a practical alternative to reactive firefighting, reinforcing its value for anticipating and mitigating disruption to change efforts.
Practical Tips for All Maturity Levels:
Focus scenario development on a small number (2-3) of meaningful scenarios that highlight material differences rather than an exhaustive list.
Use scenario planning to identify robust strategies that perform well across multiple futures, reducing overcommitment to any single pathway.
Regularly review and update scenarios to reflect new information and organizational shifts, embedding this as a governance cadence.
Engage diverse viewpoints in scenario sessions to challenge assumptions and broaden organizational readiness.
Example Scenario Planning Framework (in brief):
Step
Action
Identify Key Drivers
Pinpoint external and internal uncertainties: economic, technological, regulatory, organizational
Develop Scenarios
Build 2-3 narrative futures exploring combinations of drivers
Analyze Impact
Assess effects on change timelines, adoption, resources
Define Responses
Create contingency plans and decision points
Monitor & Update
Track relevant indicators and review scenarios regularly
5. Clarify Decision Making Authority, and Risk Appetite – Influence Without Direct Control
One of the most frequent governance pitfalls in transformation is unclear decision rights, leading to duplicated effort or “decision limbo,” which stalls progress. Change practitioners can significantly influence clarity around decision making even when not formally leading governance forums.
For organizations with high governance maturity:
Advocate for or refine delegation charters that grant clear authority boundaries across change roles and governance tiers.
Promote use of decision-rights grids paired with RACI matrices, documenting decisions by type, level, and role to eliminate ambiguity.
Encourage articulation of organization’s risk appetite in governance policies to guide decisions on escalation and investment.
Work with governance leads to socialise these tools regularly and embed them in operational processes.
For organizations with emerging or informal governance:
Educate stakeholders about the value of explicit decision clarity through workshops or short guides.
Propose simple RACI templates tailored for key initiatives to clarify roles on responsibility, accountability, consultation, and information sharing.
Introduce a basic decision-rights grid to categorize decisions (routine operational, tactical, strategic) and assign decision tiers even if informally.
Frame this work as risk mitigation: reducing delays and confusion frees leaders to focus on strategic priorities.
Practical Tips Across Maturity Levels:
Develop easy-to-use templates and cheat sheets for RACI and decision grids to distribute widely.
Use storytelling and real case examples to illustrate consequences of unclear decision-making (e.g., project delays, duplicated efforts).
Regularly revisit and update decision frameworks as governance evolves, ensuring ongoing relevance.
Encourage governance sponsors to visibly support and enforce these clarity tools.
6. Define and Promote Clear Escalation Paths
Clear escalation paths empower teams to raise concerns timely and guide issues to the appropriate governance levels without clogging decision forums or escalating unnecessarily. Change managers can champion and embed escalation discipline through influence, education, and practical tools.
For organizations with mature governance:
Collaborate with governance teams to map all escalation routes related to change risks, decisions, and resource conflicts.
Promote communication plans ensuring every contributor understands when and how to escalate – down to roles and contact points.
Incorporate escalation workflows into governance charters, RACI matrices, and decision-rights grids to reinforce paths.
Champion periodic training or refresh sessions aligned with governance cadence to maintain escalation readiness.
For organizations with limited governance forums:
Identify natural escalation points in existing leadership or operational forums and propose embedding change escalation protocols there.
Provide clear documentation and quick-reference escalation flow diagrams for frontline teams and managers.
Coach teams and middle managers on recognizing escalation triggers and the best mode of communication to avoid bottlenecks.
Frame escalation discipline as a way to safeguard both operational pace and leadership bandwidth.
Practical Tips Usable in All Environments:
Use visual flowcharts to depict escalation paths, making them highly accessible and easy to recall.
Set guidelines on what kinds of issues require escalation vs. local resolution to reduce unnecessary escalations.
Promote handling low-level risks swiftly through informal escalation while preserving formal routes for major decisions.
Encourage transparency in escalation outcomes to build trust and learning across the organization.
7. Invest in Stakeholder Education & Engagement – Be the Governance Evangelist
The success of change governance depends as much on people’s understanding and buy-in as on structures and processes. Senior change managers have a vital role in educating stakeholders, increasing governance literacy, and fostering engagement – especially in organizations where governance maturity varies or formal forums are limited.
For organizations with mature governance:
Develop formal stakeholder education programs that provide regular training on governance roles, decision frameworks, escalation processes, and how governance aligns with transformation outcomes.
Use targeted communications that frame governance benefits in terms relevant to each stakeholder group – showing “what’s in it for them.”
Implement forums like governance clinics or Q&A sessions where stakeholders can clarify their roles, raise concerns, and share governance success stories.
Collaborate with governance sponsors to visibly champion these initiatives to prevent stakeholder fatigue and increase participation.
For organizations with emerging or informal governance:
Start small with bite-sized governance literacy sessions embedded in existing communication channels such as team meetings or newsletters – keep it jargon-free and highly practical.
Translate complex governance concepts into everyday language, storytelling, and case examples that resonate with different stakeholder groups.
Identify and coach governance champions within teams who can help cascade key messages informally.
Use tools such as quick reference guides, checklists, and simplified RACI matrices to embed governance knowledge across operational levels.
Practical Tips Across All Maturity Levels:
Conduct a stakeholder governance literacy audit to understand knowledge gaps and tailor education efforts accordingly.
Develop short governance video clips or Q&A hosted by trusted leaders explaining key governance principles and benefits.
Regularly gather feedback through surveys or informal conversations to refine education efforts ensuring they meet stakeholder needs.
Emphasize the connection between good governance practices and the successful delivery of benefits, reducing resistance and increasing advocacy.
Change governance is often viewed as a formal, top-down function but, as change managers, you are uniquely positioned to influence its design and execution regardless of your direct access to governance forums. The key lies in adapting your approaches to the maturity and structure of your organization’s governance, leveraging existing forums and networks, and focusing on clear communication, collaboration, and practical tools.
By championing governance dexterity, bridging PMO and portfolio governance gaps, shaping executive reporting, embedding scenario planning, clarifying decision rights, defining escalation paths, and investing in stakeholder education, you create a foundation where governance truly supports transformation velocity, clarity, and resilience. You also create a strategic change contribution to help the organisation reach its transformation benefit goals.
Tools & Templates for Influence and Education
Cadence Checklists: Ready-to-use templates to propose weekly flash checks, monthly value meetings, and quarterly strategic reviews tailored for different governance forums and maturity.
Sample RACI Matrix & Decision-Rights Grid: Simplified versions that can be adapted for routine and strategic decisions, supporting role clarity and authority distribution.
Escalation Flow Diagram: Visual maps suitable for team briefings and leader coaching in both formal and informal governance contexts.
Stakeholder Education Plan Outline: A scalable framework for assessing needs, designing education content, and measuring engagement impact.
A large financial services organisation spent eight months preparing for a core banking system replacement. The technology was solid. The vendor was experienced. The project team had executed similar programmes at other banks. Four weeks after go-live, the programme was in crisis. Not because of a technical failure, but because the people who needed to use the new system had not been adequately prepared. Nobody had formally assessed whether the organisation was ready.
This scenario is far more common than it should be. Change readiness assessment, the systematic process of understanding whether an organisation’s people, leaders and structures are prepared to absorb a specific change, remains one of the most underinvested practices in change management. It is often skipped entirely, compressed into a single survey sent weeks before go-live, or treated as a compliance exercise rather than a genuine planning input.
This article provides a practical change readiness assessment framework for senior practitioners. We will examine what readiness actually means, when to assess it, and how to translate readiness data into decisions that improve programme outcomes.
What a change readiness assessment actually measures
A change readiness assessment is a structured evaluation of an organisation’s capacity and willingness to successfully implement a specific change. The word “specific” matters: readiness is not a generalised organisational trait. An organisation may be highly ready for a leadership restructure and completely unprepared for a technology migration, even within the same business unit, at the same time.
According to Prosci’s comprehensive research on change readiness, assessing readiness involves two distinct lenses: the nature of the change itself, including its scope, complexity and disruption to current ways of working, and the organisation’s capacity to absorb change, including leadership alignment, cultural factors, and the existing change load on impacted groups.
Getting both lenses right is essential. Practitioners who focus only on the change’s characteristics may overestimate readiness in organisations with limited change capacity. Those who focus only on organisational capacity may underestimate the specific demands of a particular initiative.
Individual readiness versus organisational readiness
One of the most important distinctions in change readiness assessment is the difference between individual and organisational readiness. These are related but not the same thing.
Individual readiness refers to whether specific employees, particularly those whose roles will change significantly, have the awareness, desire, knowledge and ability to adopt the change. Prosci’s ADKAR model provides a well-established framework for assessing individual readiness: do affected employees understand why the change is happening (Awareness), do they want to participate in it (Desire), do they have the knowledge to change (Knowledge), do they have the ability to demonstrate the new behaviour (Ability), and are there systems in place to sustain the change (Reinforcement)?
Organisational readiness operates at a higher level. It examines whether the organisation’s leadership, structures, processes, systems and culture create the conditions for the change to succeed. An individual employee may be highly ready and motivated to adopt a change that the organisation is structurally unprepared to support. Both dimensions need to be assessed.
What readiness assessment is not
It is worth being clear about what a change readiness assessment is not, because the term is frequently misused.
It is not a survey sent to 5,000 employees asking them to rate on a five-point scale how confident they feel about the upcoming change. That is a pulse check and it has its uses, but it is not a readiness assessment. Readiness assessment involves structured inquiry across multiple dimensions, triangulated from multiple sources, interpreted with professional judgement.
It is not a one-time activity. Readiness is dynamic. An organisation that appears ready three months before go-live may not be ready at go-live if key sponsors have left, a competing change has consumed capacity, or training delivery has slipped. Readiness assessment should be conducted at defined points throughout the programme lifecycle, not just at the beginning.
And it is not a box to tick. If the output of your readiness assessment does not influence your implementation plan, your go-live timing or your training design, you have not done a readiness assessment. You have produced a document.
Pre-planning (before detailed design): An initial readiness assessment at the outset of a programme helps you understand the baseline. What change capacity does this organisation currently have? What is the existing change load on impacted groups? How strong is leadership alignment with the programme’s objectives? This assessment shapes the scope and resourcing of your change management approach.
Pre-implementation (60 to 90 days before go-live): A more detailed assessment at this stage moves from organisational capacity to programme-specific readiness. Are the impacted employee groups aware of the change? Is there meaningful desire to participate? Has training been designed and is there time in the schedule to deliver it? This is when gaps in readiness are most actionable.
Pre-go-live (two to four weeks out): A final readiness assessment immediately before go-live is a gate check. It should not be the first time you are looking at readiness, but it should confirm that the critical conditions for a successful launch are in place. This assessment often produces the difficult conversation about whether to proceed as planned, phase the rollout, or delay to allow more preparation time.
Many organisations also conduct readiness assessments post-go-live to understand adoption progress, but at that point the term “readiness” transitions into “adoption measurement.”
A practical change readiness assessment framework
The following framework assesses change readiness across five dimensions. It can be applied to any significant organisational change. The specific indicators within each dimension should be tailored to the nature of the change being assessed.
Dimension 1: Leadership alignment and sponsorship
Change consistently succeeds or fails at the leadership level. Prosci’s benchmark data identifies active and visible executive sponsorship as the single most important factor in change success. Before any major change, the following questions need clear answers:
Does the executive sponsor understand the change deeply enough to actively advocate for it in their own words?
Is the sponsor willing to invest time in the change, not just endorse it in communications?
Are middle managers aligned with the change and prepared to manage the “people side” for their teams?
Is there a clear accountability structure for change outcomes, including adoption and benefit realisation?
Leadership alignment is often assumed rather than tested. A readiness assessment forces the conversation explicitly, identifying where alignment is genuine and where it is merely stated.
Dimension 2: Stakeholder awareness and desire
Readiness requires that the people being asked to change understand why the change is happening and, ideally, want to participate in it. Assessing awareness and desire involves:
Do impacted employees know the change is coming, what it means for them specifically, and what will be different after implementation?
Do they understand the case for change, not just the what but the why?
Are there identifiable groups whose desire to participate is low, and if so, why? Is this a communication gap, a confidence gap, or a substantive objection to the change itself?
Have the most affected stakeholder groups been engaged in co-designing aspects of the change, and has that engagement built genuine buy-in?
The distinction between awareness and desire is important in this dimension. Employees may be fully aware of a change and still have low desire to adopt it. Each requires a different response.
Dimension 3: Organisational capacity for change
Organisational capacity refers to the bandwidth that impacted groups actually have to absorb change. This is distinct from their willingness, it is a function of their current workload, the competing changes already in their environment, and the structural support available to them during the transition.
Key questions include:
What is the current change load on the most impacted groups? Are they already managing multiple concurrent changes?
Do business unit leaders have time in their calendars for change-related activities, including communications, coaching their teams, and attending training?
Is there a track record of change resilience in this part of the business, or is this group already showing signs of change fatigue?
Have the resources required for the change, including backfill, training time, and transition support, been formally allocated?
Research on change saturation shows that employee overwhelm is increasingly a structural issue in large organisations, not an individual failing. Capacity assessment puts a number on the real bandwidth available and surfaces the risk of overloading groups who appear willing but are structurally unable to absorb more change.
Dimension 4: Process and systems readiness
For changes that involve technology or process redesign, a specific assessment of process and systems readiness is critical. This dimension examines:
Have the new processes been designed, documented and tested before they are deployed to the organisation?
Do employees have access to the systems they need, and have those systems been tested in conditions that reflect actual usage?
Are the support structures in place for the transition period, including help desks, super-user networks, and escalation pathways?
Have workarounds or interim arrangements been designed for the period between old-process end and new-process confidence?
This dimension often reveals gaps in programme planning that the change team is not responsible for creating but is responsible for surfacing. A readiness assessment that finds employees are being asked to adopt a process that has not been fully designed is not a criticism of the change team. It is a risk flag that allows the programme to course-correct.
Dimension 5: Cultural readiness
Cultural readiness is the hardest dimension to assess and the easiest to underestimate. It examines whether the organisation’s values, norms and informal ways of working are compatible with what the change requires.
A change that requires more collaborative decision-making will struggle in an organisation with a strong hierarchical culture. A change that requires employees to raise issues and problems early will struggle in an organisation where bad news is historically punished. These are not insurmountable barriers, but they are real ones that need to be factored into change design and implementation timeframes.
Cultural readiness questions include: does this change require employees to behave in ways that are consistent with or contrary to the organisation’s existing cultural norms? Are there cultural champions in the business who embody the behaviours the change requires? Is the change itself culturally coherent, or does it sit in tension with other organisational signals employees are receiving simultaneously?
How to use readiness data to make better decisions
A readiness assessment is only valuable if it influences decisions. The most common failure mode is conducting a thorough assessment and then failing to act on what it reveals, usually because the programme timeline is already locked and the change team lacks the organisational standing to push back on it.
Here is how effective change teams use readiness data:
Gate decisions. Use readiness assessment outputs as a formal input to go/no-go decisions at key programme milestones. If the assessment reveals that leadership alignment is weak or that impacted groups have no capacity in Q3, that information should trigger a genuine conversation about timing, not just a note in the risk register.
Targeted interventions. Readiness data that is segmented by business unit, role, or stakeholder group allows change teams to deploy their limited resources where the risk is highest. Rather than a blanket communications plan, you can design targeted engagement for the groups showing the lowest readiness scores.
Design adjustments. Early readiness assessment, conducted before detailed implementation design, can shape how the change is rolled out. A phased implementation, a longer stabilisation period, or a modified training design may be the right response to readiness data. These decisions are much easier to make before the implementation plan is finalised than after it.
Progress tracking. Conducting readiness assessments at multiple points in the programme allows you to track whether your interventions are working. If awareness scores are not improving after three rounds of communications, the communications strategy needs to change.
Common mistakes in change readiness assessment
The five most common mistakes we see in practice are:
Assessing too late. A readiness assessment conducted four weeks before go-live is not a planning tool. It is damage assessment. Assessment needs to start at programme initiation.
Assessing at the wrong level. Business unit-level readiness scores hide the specific groups where risk is concentrated. Always segment by role or stakeholder group.
Treating subjective ratings as objective data. Readiness assessment involves human judgement applied to inherently ambiguous questions. The data needs to be triangulated, from interviews, observation, and document review, not just surveys.
Separating readiness from implementation planning. If the change team and the programme team are operating independently, readiness data will not reach the people who can act on it.
Assessing without a plan to act. If you are not prepared to delay, redesign, or re-resource based on what the assessment reveals, do not conduct it. A readiness assessment that produces no action undermines trust in the process.
Using digital tools to support change readiness assessment
Managing readiness assessment data across large, complex programmes quickly becomes unwieldy with spreadsheets and documents. Digital change management platforms allow teams to capture readiness data systematically, track it over time, and connect it to other programme data such as change impact, training completion and adoption metrics.
The Change Compass supports this kind of integrated approach, allowing change teams to assess readiness at the stakeholder group level and track how it evolves as the programme progresses. This creates a living picture of programme readiness rather than a static snapshot, which is particularly valuable for multi-year transformation programmes where readiness conditions shift significantly over time.
If you would like to see how this works in practice, book a weekly demo to explore how leading organisations use data-driven readiness tracking to make better go-live decisions.
A change readiness assessment, done well, is one of the highest-return activities a change team can undertake. It surfaces risks early enough to be addressed, creates the evidence base for difficult programme conversations, and focuses change resources on the groups and dimensions where they are most needed.
The organisations that manage change most effectively treat readiness not as a pre-launch checklist but as a continuous, multi-dimensional discipline that informs decisions throughout the programme lifecycle. They assess leadership alignment, stakeholder awareness and desire, organisational capacity, process readiness, and cultural fit, and they use what they find to improve their implementation approach.
The question is not whether you can afford to conduct a thorough change readiness assessment. It is whether you can afford not to.
Frequently asked questions
What is a change readiness assessment?
A change readiness assessment is a structured evaluation of an organisation’s capacity and willingness to implement a specific change successfully. It examines multiple dimensions including leadership alignment, stakeholder awareness and desire, organisational capacity, process and systems readiness, and cultural fit. Unlike a simple survey, a robust readiness assessment triangulates data from multiple sources and produces actionable insights for programme planning.
When should a change readiness assessment be conducted?
Change readiness assessment should be conducted at multiple points in the programme lifecycle, not just once. The three most critical windows are: pre-planning, to establish baseline capacity and change load; pre-implementation (60 to 90 days before go-live), to assess programme-specific readiness and identify gaps; and pre-go-live (two to four weeks out), as a final gate check before launch.
What is the difference between individual and organisational change readiness?
Individual readiness refers to whether specific employees have the awareness, desire, knowledge and ability to adopt the change. Organisational readiness operates at a higher level, examining whether leadership, structures, processes and culture create the conditions for change to succeed. Both need to be assessed, as an organisation may have willing individuals in an environment that is structurally unable to support the change.
What are the key dimensions of a change readiness assessment?
The five key dimensions are: leadership alignment and sponsorship, stakeholder awareness and desire, organisational capacity for change (including current change load and bandwidth), process and systems readiness, and cultural readiness. Each dimension should be assessed using a combination of quantitative ratings and qualitative inquiry, segmented by stakeholder group rather than assessed at the whole-of-business-unit level.
How do you act on the results of a change readiness assessment?
Readiness data should inform gate decisions on timing and go-live, targeted change interventions for the groups showing the lowest readiness, design adjustments to the implementation plan, and progress tracking when assessed at multiple points in the programme. The critical failure mode is conducting a thorough assessment and then failing to act on what it reveals because the programme timeline is already locked.
How can digital tools support change readiness assessment?
Digital change management platforms allow teams to capture readiness data at a granular level, track it over time, and connect it to other programme data such as change impact, training completion and adoption progress. This creates a dynamic picture of readiness rather than a static snapshot, which is particularly valuable for complex, multi-year programmes where readiness conditions evolve significantly.
References
Prosci. Change Readiness: A Comprehensive Guide. https://www.prosci.com/change-readiness
Prosci. The Correlation Between Change Management and Project Success. https://www.prosci.com/blog/the-correlation-between-change-management-and-project-success
AIHR. How To Conduct a Change Readiness Assessment [+ Template]. https://www.aihr.com/blog/change-readiness-assessment-template/
The Change Compass. Why Change Saturation Is a Pandemic for Most Large Organisations. https://thechangecompass.com/why-change-saturation-is-a-pandemic-for-most-large-organisations/
IMPLEMENTATION NOTES
Post ID: 21645
Suggested title: Change readiness assessment: a practical framework for building confidence before you launch
Meta description: A practical change readiness assessment framework covering five key dimensions , leadership alignment, capacity, culture, process and stakeholder desire.
When a change impact assessment is done well, it is one of the most powerful tools in a change practitioner’s kit. It tells you who is affected, how significantly, and in what ways. It helps prioritise your change management effort. It gives project teams a clear line of sight between their decisions and the effect those decisions will have on real people doing real jobs.
When it is done poorly , which is more common , it becomes a box-ticking exercise. Practitioners list every system or process change, assign a red-amber-green rating based on gut feel, and produce a document that sits in SharePoint and is never referenced again.
The gap between those two outcomes is almost entirely down to methodology. This article provides a structured, ten-step approach to conducting a change impact assessment that is genuinely useful, defensible under scrutiny, and designed to inform decisions rather than document assumptions.
Why most change impact assessments fall short
The fundamental problem with most impact assessments is that they conflate activity with impact. Practitioners document what is changing , processes, systems, job roles, reporting lines , but stop short of translating those changes into what they actually mean for the people who will have to live with them.
Prosci’s research on change impact makes this distinction clearly: organisational-level change must be translated to the individual level to be actionable. A system migration is not an impact. The fact that a team of forty finance analysts will need to rebuild their core workflows and learn three new interfaces within six weeks while continuing to close the monthly books , that is an impact.
The second common failure is breadth without depth. Many impact assessments aim to cover every group in the organisation but spend only minutes thinking about each one. A more useful approach is to identify the most affected groups early, assess them in depth, and treat others at a proportionate level of detail.
McKinsey’s 2024 analysis of transformation programmes found that well-informed leaders who focus their change effort on the genuinely high-impact areas are able to achieve 70-80% transformation success rates , the inverse of the commonly quoted failure statistic. Focused, accurate impact assessment is a significant part of what enables that focus.
The ten dimensions of change impact
Before running a change impact assessment, it helps to have a consistent taxonomy of impact types. Prosci identifies ten aspects of change impact that provide a comprehensive lens for any assessment:
Processes , which workflows, procedures, or operating methods are changing
Systems and technology , which tools, platforms, or data sources are affected
Job roles , which roles are being created, modified, or eliminated
Critical behaviours , what people will need to do differently day-to-day
Mindsets and beliefs , what assumptions or ways of thinking need to shift
Reporting structure , how accountability and authority relationships are changing
Performance reviews , how success will be measured and rewarded differently
Compensation , whether pay, incentives, or benefits are affected
Location , whether where or how work is performed is changing
Tools and equipment , what physical or digital tools people need to learn or adopt
Not every dimension will be relevant to every change. The value of this taxonomy is in ensuring you don’t miss a category that, if overlooked, can derail adoption. Compensation and performance review impacts, for instance, are frequently underestimated in their effect on employee resistance.
A ten-step change impact assessment methodology
Here is a structured process for conducting a change impact assessment that is rigorous, scalable, and produces outputs that are actually used.
Step 1: Define the scope and objectives
Before gathering any data, be clear about what the assessment is and is not intended to cover. Key decisions include:
Which groups or roles are in scope
Which change dimensions are most relevant to this particular initiative
What decisions the assessment will inform (resource allocation, sequencing, communication targeting, training design)
Who will use the outputs and in what format
Skipping this step results in assessments that are technically complete but operationally useless.
Step 2: Map the affected stakeholder groups
Create a stakeholder map that identifies every group, role, or team that will experience some form of change. This is broader than just the primary users of a new system , it includes managers, support functions, customers, suppliers, and any team that interfaces with the affected area.
For each group, note the estimated size (headcount), geographic spread, and any known sensitivities or constraints.
Step 3: Gather change information from the project team
Meet with project workstream leads to understand what is actually changing in their area. Use the ten-dimension taxonomy as your interview guide. Capture not just the functional changes but the timelines, dependencies, and any known risks.
At this stage you are collecting raw information about what is changing, not yet assessing impact.
Step 4: Assess impact severity for each group
For each stakeholder group, assess the severity of impact across the relevant dimensions. A simple but effective scale is:
High impact: Significant change to daily work; requires new skills, new processes, or major behaviour change; high potential for resistance or confusion
Medium impact: Moderate change; some adjustment required but within existing capability; manageable with good communication and targeted support
Low impact: Minor change; easily adapted to with basic information; unlikely to generate resistance
Be specific about why a rating has been assigned. “High , because the new system replaces a manual process this team has used for eight years and requires retraining in a four-week window” is defensible. “High” on its own is not.
Step 5: Assess change volume and cumulative load
A single change impact assessment looks at one initiative in isolation. But your employees are not living with one initiative in isolation , they are living with everything that is being asked of them at once.
For each stakeholder group, assess the cumulative change load by mapping other major initiatives that are running concurrently. This step is where a digital change management platform becomes particularly valuable: tools like Change Compass allow you to visualise the total change burden on any group across the portfolio, rather than calculating it manually for each assessment.
A group might have a medium impact score on your initiative but a very high cumulative load score when all concurrent changes are considered. This distinction materially affects your sequencing and resourcing decisions.
Step 6: Identify critical risk groups
Based on impact severity and cumulative load, identify the three to five stakeholder groups that represent the highest change risk. These are the groups where under-investment in change support is most likely to compromise adoption.
For each critical risk group, document:
The specific nature of the impact
The key risks (resistance, capability gap, burnout)
The support they will need (type, timing, delivery channel)
Step 7: Identify change enablers and constraints
Not all impacts are negative. Some changes create genuine opportunities , new skills, better tools, clearer roles. Identifying these is not spin; it is important information for communication design and resistance management.
Equally important are constraints: groups who are already at capacity, upcoming business-critical events that will compete for attention (financial year-end, major product launches), and any political sensitivities around role changes.
Step 8: Build the change impact heat map
Consolidate your assessment data into a change impact heat map , a structured visual that shows, at a glance, which groups are most affected, across which dimensions, and at what level of severity.
This is not just a reporting tool. It is a planning tool that drives decisions about communication targeting, training sequencing, change champion placement, and leadership engagement priorities.
Step 9: Validate with stakeholders
Present your impact assessment findings to key stakeholders , the project team, business owners, and representative managers from the most affected groups , before finalising it. This validation step serves two purposes: it catches errors and assumptions, and it begins the process of building stakeholder ownership of the change.
Expect to revise your assessment based on this feedback. Impact assessments that do not go through a validation step are consistently less accurate.
Step 10: Maintain and update throughout the programme
A change impact assessment is a living document, not a one-time deliverable. As programme scope evolves, decisions are made, and timelines shift, the assessment needs to be updated. Build regular review points into the programme governance cycle, and track whether actual adoption patterns are consistent with your impact predictions.
Practical examples across industries
Change impact assessments look somewhat different in different contexts, but the methodology translates across industries.
Financial services , core banking platform replacement: The most severely impacted groups were typically not IT (who are experienced in platform transitions) but the mid-tier operational teams whose daily work was entirely platform-dependent. The assessment identified that branch operations staff faced both high impact and high cumulative load, and this finding drove a decision to phase the rollout to delay the branches’ go-live date.
Healthcare , electronic medical records implementation: Impact assessment revealed that senior clinicians had the lowest formal training time allocated but the highest behaviour change required (fundamental changes to clinical documentation practices). Rebalancing training allocation based on the assessment findings was credited with avoiding a major adoption failure at go-live.
Government , enterprise resource planning implementation: The assessment identified that the finance team faced impacts across seven of the ten dimensions simultaneously, including role changes, new performance metrics, and a compressed transition period coinciding with budget cycle. This finding led to additional dedicated change support being resourced for that group.
Using Change Compass to automate impact analysis
One of the significant efficiency gains available to change teams is automating the data collection and consolidation steps of a change impact assessment. Rather than maintaining manual spreadsheets and heat maps across a portfolio, platforms like Change Compass allow change data to be captured, updated, and visualised in real time , with portfolio-level roll-ups that show cumulative impact across all programmes for any given stakeholder group.
This capability is particularly valuable for enterprise change functions running ten or more concurrent programmes, where manual tracking is simply not viable at the required level of rigour. The weekly demo is a practical way to see this in action across a live dataset.
A change impact assessment done at this level of rigour is not an overhead. It is the analytical foundation for every subsequent change decision , what to communicate, who to train, when to deploy change champions, where leadership engagement is critical, and how to sequence the work.
The ten-step framework in this article scales from small programme teams to large enterprise change functions. The key discipline is maintaining the distinction between activity (what is changing) and impact (what that means for the people who have to change) , because that distinction is where the real planning value lives.
Frequently asked questions
What is a change impact assessment?
A change impact assessment is a structured analysis of how a programme or project will affect different groups of people in an organisation , their processes, roles, behaviours, systems, and working environment. Its purpose is to inform change management planning by identifying which groups need the most support, and in what ways.
How do you conduct a change impact assessment?
The most effective approach involves defining scope, mapping all affected stakeholder groups, gathering change information from the project team, rating impact severity across each group and change dimension, assessing cumulative load from other concurrent initiatives, and validating findings with key stakeholders. The result is a change impact heat map that drives communication, training, and engagement decisions.
How is a change impact assessment different from a risk assessment?
A risk assessment identifies what could go wrong with the project. A change impact assessment identifies how the project will affect people. The two complement each other: high impact scores on the change assessment should inform and escalate risk assessments, particularly where cumulative load or stakeholder capacity constraints create delivery risk.
Who should be involved in a change impact assessment?
The change practitioner typically leads the assessment, but the inputs come from project workstream leads, business area managers, HR partners, and , critically , representatives of the affected stakeholder groups. Assessments built entirely from the project team’s perspective without validation from the business tend to underestimate the true degree of disruption.
How often should a change impact assessment be updated?
At minimum, at each major project milestone or whenever scope changes materially. In practice, good change practitioners review their impact assessment every four to six weeks during active delivery, and update it whenever adoption data reveals that actual impact is different from what was predicted.
Most organisations that struggle with large-scale change don’t have a capability problem. They have a structural problem. The change practitioners are skilled. The methodology is sound. But the way the change function is organised means it can never move fast enough, influence broadly enough, or demonstrate enough value to earn a permanent seat at the table.
Getting the change management org structure right is one of the most consequential decisions a Head of Transformation or Chief People Officer can make. Done well, it multiplies the impact of every programme in flight. Done poorly, it turns your best change practitioners into glorified project administrators, perpetually reactive and forever underfunded.
This article lays out the structural choices available to enterprise change functions, the factors that determine which model works best, and a practical framework for designing a change management org structure that scales.
Why structure matters more than headcount
The instinct when change initiatives fail is to add more people. Hire another change manager. Bring in contractors. Scale up the programme team. But headcount without the right structure is like adding more lanes to a congested motorway , it doesn’t resolve the underlying problem, it just adds more traffic.
Prosci’s longitudinal research on change management best practices consistently shows that organisations with a dedicated, structured change function are seven times more likely to achieve their change objectives than those relying on ad hoc change support. Yet most large organisations still deploy change management as a project-level add-on rather than an enterprise capability.
The structural question is fundamental: where does change management live, who does it report to, how are resources allocated, and how does it interface with the project management and strategy functions? These decisions shape every other outcome.
The three primary structural models
There is no single right answer to how a change function should be organised. Prosci’s own guidance on the Change Management Office makes clear that the optimal structure depends on organisational culture, strategic priorities, and the maturity of the change capability. That said, most enterprise change functions fall into one of three models.
Centralised model: the change management office
In a centralised structure, change management capability sits in a single, dedicated team , typically called a Change Management Office (CMO) or Centre of Excellence (CoE). This team owns methodology, standards, tools, and resource deployment across the organisation.
The centralised model works best when:
The organisation is running a significant number of concurrent transformation programmes
Leadership wants consistent methodology and quality assurance across all change activity
There is a strong sponsor at the executive level (typically CHRO, COO, or CEO direct report)
The organisation is early in its change maturity journey and needs to build capability systematically
The main risk is that a centralised CMO can become a bottleneck, or worse, a bureaucratic layer that slows programmes down rather than accelerating them.
Federated model: embedded change resources
In a federated structure, change management practitioners are distributed across business units, portfolios, or programmes. Each area maintains its own change capability, with loose coordination at the enterprise level.
This model suits organisations where:
Business units operate with high autonomy and have distinct change contexts
There is already a reasonable level of change maturity across the organisation
Portfolio complexity is high and requires deep contextual knowledge in each area
Speed of deployment matters more than consistency of approach
The risk with a federated model is fragmentation. Without a shared methodology, it becomes difficult to report on change capacity, manage cumulative change load, or build organisational learning across programmes.
Hybrid model: a hub-and-spoke structure
The hybrid model is the most common in mature enterprise organisations , and for good reason. It combines a small central team responsible for methodology, governance, and strategic oversight with embedded change practitioners in each business unit or major programme.
The central hub sets the standards. The spokes execute them, with enough autonomy to adapt to local context.
This model is increasingly favoured by Prosci’s research, which notes that the most effective location for the enterprise CMO is increasingly the Strategy, Transformation and Planning office , rather than HR, as was historically the case , reflecting the shift of change management from a people support function to a strategic business enabler.
Key roles in an enterprise change management structure
Regardless of which structural model you adopt, mature enterprise change functions typically include the following roles. The exact titles will vary by organisation; the functions they perform are consistent.
Head of Change / Director of Organisational Change Management
This is the senior leadership role accountable for the overall change capability. They are responsible for:
Setting strategy for the change function and building its maturity
Engaging executive sponsors and senior leaders
Overseeing portfolio-level change risk and capacity
Championing the value of change management internally
In many organisations, this role is being elevated from Head of Change to Chief Transformation Officer or equivalent, reflecting the growing strategic importance of the function.
Change managers / change leads
These are the practitioners who own change delivery at the programme or project level. Their responsibilities include:
Developing and executing change management plans for specific initiatives
Conducting stakeholder analyses and change impact assessments
Designing and delivering communications and engagement activities
Monitoring adoption and reporting on change progress
Senior change managers typically work across multiple programmes or are allocated to the highest-complexity transformations.
Change analysts
Change analysts provide the data and analytical backbone of the change function. Their work includes:
Maintaining change portfolio data and tracking cumulative change load
Analysing change impact data across the employee population
Producing reporting for programme boards and executive leadership
Supporting the development of measurement frameworks
As change management becomes more data-driven, the change analyst role is increasing in prominence and seniority.
Change champions / change network coordinators
These are typically not full-time change roles, but rather a network of business representatives who support adoption at the ground level. A well-run change champion network can significantly extend the reach of a small central team. The CMO typically designs and manages the champion programme; the champions themselves remain in their business unit roles.
How to determine the right team size
One of the most common questions organisations ask is: how many change practitioners do we need? The honest answer is that there is no universal ratio, but there are sensible parameters.
A useful starting point is to map your change portfolio , the number of concurrent programmes with significant people impact , and assess the complexity and scale of each. As a general guide:
Small, low-complexity programmes: 0.2,0.3 FTE change support
Alongside programme-level resourcing, enterprise functions typically maintain a small strategic overhead for methodology, governance, and capability building , typically 1,2 FTE depending on organisation size.
One critical input to this calculation is cumulative change load. McKinsey research on transformation success consistently highlights that organisations running multiple transformations concurrently face compounding risk , not just from each individual programme, but from the combined demand placed on the employee population. Structural visibility of this cumulative load is one of the most valuable things an enterprise change function can provide.
Reporting line: where should the change function sit?
Where the change function reports has a significant effect on its influence, scope, and budget. The most common reporting lines and their trade-offs are:
Reporting to HR / People & Culture: Provides strong integration with people processes (talent, learning, engagement) but can result in a perception that change management is a “soft” function focused primarily on communication rather than business outcomes.
Reporting to the PMO: Enables tight integration with project governance, budget cycles, and programme reporting. The risk is that change becomes subordinate to project delivery rather than a co-equal discipline.
Reporting to Strategy / Transformation: Positions change as a strategic function with executive visibility. This is the model Prosci’s research increasingly identifies as most effective, as it places change capability at the point where strategic decisions are made.
Reporting directly to the CEO / COO: Common in organisations undergoing significant enterprise transformation. Provides the highest level of authority but requires a senior, commercially credible leader to hold the role.
The role of digital tools in scaling your change function
One of the practical challenges all change functions face is scale. A team of five or six change practitioners cannot manually track the change portfolio, analyse cumulative impact, maintain stakeholder data, and produce meaningful reporting across twenty or thirty concurrent programmes.
This is where a digital change management platform becomes operationally important. Tools like Change Compass allow change functions to centralise change portfolio data, automate impact reporting, and provide leadership with real-time visibility of change load across the organisation , without adding headcount. For enterprise change functions operating a hub-and-spoke model, a shared digital platform also creates consistency between the central team and embedded practitioners.
The Change Compass platform supports everything from individual change impact assessments through to portfolio-level analytics, enabling the change function to make the case for resources and demonstrate measurable value to the business.
A five-step framework for designing your change management org structure
If you are building or redesigning a change function, here is a practical sequence to follow:
Map your change portfolio , Catalogue all programmes currently in flight or planned for the next 18 months. Assess the complexity, scale, and people impact of each. This gives you a baseline for resource requirements.
Assess your change maturity , A centralised, method-heavy CMO is rarely the right starting point for an organisation with low change maturity. Build a structure that is achievable now and scalable as maturity grows.
Choose your structural model , Based on your portfolio size, maturity, and culture, select from centralised, federated, or hybrid. Most enterprise organisations above a certain scale will land on a hybrid hub-and-spoke model.
Define the reporting line , Engage senior leadership to determine where the change function sits. The reporting line determines influence; be explicit about this rather than accepting a default.
Define roles, not just headcount , Specify the function each role performs, not just the title. A Head of Change and two change managers with clearly defined accountabilities will outperform a team of ten with ambiguous responsibilities.
Common structural pitfalls to avoid
Even well-intentioned change functions fall into recurring structural traps:
Embedding change too deep in HR: The function loses commercial credibility and access to early strategic conversations.
Making the CMO the gatekeeper for all change activity: This creates a bottleneck and frustrates programme teams. The CMO’s job is to set standards and build capability, not approve every change plan.
Understaffing the analytical function: Without data, the change function cannot demonstrate value or make the case for its own resourcing.
Treating the champion network as a substitute for professional change management: Champions extend reach , they do not replace it.
Failing to document the charter: Without a clear, documented mandate, the change function’s scope will be contested constantly.
The change management org structure you design will either amplify or constrain everything your practitioners do. Getting it right requires more than drawing an org chart. It requires a clear view of your change portfolio, an honest assessment of your maturity, a deliberate choice about where the function sits in the business, and well-defined roles that reflect the actual work.
For organisations serious about building enterprise change capability, the structural conversation is not a one-time exercise , it evolves as the business grows, the portfolio expands, and maturity deepens. The organisations that treat change capability as a permanent strategic asset, structured and resourced accordingly, are the ones that consistently outperform on the delivery of major transformations.
Frequently asked questions
What is change management org structure?
Change management org structure refers to how an organisation’s change management capability is formally organised , including the team configuration, reporting lines, roles, and accountability arrangements. A well-designed structure ensures that change practitioners have the authority, resources, and visibility needed to support major transformation programmes effectively.
What are the main models for structuring a change management function?
The three primary models are centralised (a single CMO or CoE), federated (change practitioners distributed across business units), and hybrid hub-and-spoke (a small central team with embedded practitioners across the portfolio). Most large enterprises use a hybrid model, balancing consistency of methodology with the contextual agility that embedded roles provide.
Where should the change management function report?
Prosci’s research increasingly points to Strategy, Transformation and Planning as the most effective location, ahead of HR and the PMO. The right reporting line depends on your organisation’s structure, but the key principle is that the change function needs proximity to where strategic decisions are made, not just where people processes are managed.
How many change managers does an enterprise need?
There is no universal ratio, but a useful starting framework is 0.2,0.3 FTE for small/low-complexity programmes, 0.5,1.0 FTE for medium programmes, and 1.5,3.0+ FTE for large enterprise transformations. The total portfolio of concurrent programmes drives the overall requirement, with additional capacity for governance and capability building at the central level.
What is the difference between a Change Management Office and a Centre of Excellence?
A Change Management Office (CMO) typically refers to a team that provides operational change management support and resources to programmes. A Centre of Excellence (CoE) tends to focus more on methodology, capability building, standards, and thought leadership , often with a smaller core team that influences rather than delivers change activity. In practice, the terms are often used interchangeably.
How does change management org structure affect programme outcomes?
Significantly. Prosci research shows that organisations with effective change management are seven times more likely to meet their change objectives. Structure determines whether change management is deployed early, resourced adequately, and given the authority to influence programme design , or whether it is bolted on late as a communications exercise.
What key metrics should be included in a change management dashboard?
A change management dashboard should include key metrics such as project progress, employee engagement levels, feedback scores, and timeline adherence. Additionally, tracking resistance rates and training effectiveness can provide valuable insights into the success of the change initiative, enabling more informed decision-making throughout the process.
A good change adoption dashboard can make or break the full benefit realization of a change initiative. It captures the essence of what stakeholders need to focus on to drive full change adoption. This visual representation of the status and progress of a change initiative provides real-time data and insights into how well-impacted employees are adopting the change and what steps can be taken to improve adoption rates. In this article, we will outline the steps for designing an effective change adoption dashboard.
Change adoption is often only measured toward the end of a change initiative. This is a mistake since the adoption journey can start as early as the project commencement, or when stakeholders start hearing about the initiative. At a minimum, change adoption should be defined and agreed upon before significant change impact happens. If you are implementing a system this will be well before the system go-live.
These are the key steps in building a great change project adoption dashboard.
The first step in designing a change adoption dashboard is to clearly define the objectives of the change initiative. This includes understanding what the change is, what it aims to achieve, and what the desired outcomes are. Understanding the objectives of the change initiative is critical to defining the metrics that will be used to measure adoption and success.
If your initiative has a long list of objectives, be careful not to be tempted to start incorporating all of these into your dashboard. Your task is to pin down the most critical change management objectives that must be met in order for the initiative to be successful. If you are really struggling with how many objectives you should focus on, aim for the top three.
Step 2: Identify Key Metrics
Once the objectives of the change initiative have been defined, the next step is to identify the key metrics that will be used to measure adoption and success. These metrics should be directly tied to the objectives of the change initiative and should provide actionable insights into the progress and success of the change.
Some examples of metrics that can be used to measure change adoption include:
Stakeholder engagement levels (depending on your stakeholder impacts these could be customer, employee or partners)
Stakeholder engagement levels (depending on your stakeholder impacts these could be customer, employee or partners)
User adoption rates
User adoption rates
Process improvement metrics
Process improvement metrics
Time to adoption
Time to adoption
Feedback from employees
Feedback from employees
The key is to locate the few metrics that will form the core of what full change adoption means. As a general rule, this often means a behaviour change of some kind. Here are some examples.
If the goal is changing a business process from A to B. Then you are looking for employees to start following the new process B. Then, identify the core behaviours that mean following process B.
If the goal is changing a business process from A to B. Then you are looking for employees to start following the new process B. Then, identify the core behaviours that mean following process B.
If the goal is to start using a new system, then you would focus on system usage. Also focus on tracking any workarounds that employees may resort to in order not to use the system.
If the goal is to start using a new system, then you would focus on system usage. Also focus on tracking any workarounds that employees may resort to in order not to use the system.
If the goal is to improve customer conversations, then you would focus on the quality of those conversations using key indicators. This may involve call listening or customer satisfaction ratings.
If the goal is to improve customer conversations, then you would focus on the quality of those conversations using key indicators. This may involve call listening or customer satisfaction ratings.
Again, ensure you are not over-extending yourself by picking too many metrics. The more there is, the more work there is. Having too many metrics also lead to attention dilution, and you start to loose stakeholder focus on the more critical metrics compared to less critical ones.
In the group of metrics you’ve chosen, if there is no behaviour measure then it is likely you may have missed the most critical element of change adoption. In most cases, behaviour change metric is essential for any change adoption dashboard.
If your change process involves too many behaviour steps, then focus on ones that are easier to track and report on. In a system implementation project, they could be system usage reports or login frequency.
Step 3: Choose the Right Visualization Techniques
The next step in designing a change adoption dashboard is to choose the right visualization techniques. The visualizations should be chosen based on the data that needs to be displayed and the insights that need to be gained. Some examples of visualization techniques that can be used include:
Bar graphs: to display changes in metrics over time
Bar graphs: to display changes in metrics over time
Pie charts: to display the distribution of data
Pie charts: to display the distribution of data
Line charts: to display changes in metrics over time
Line charts: to display changes in metrics over time
Heat maps: to display the distribution of data on a map
Heat maps: to display the distribution of data on a map
Selection of charts can be technical, and your goal is always to choose the right type of chart to make it easier for the audience to understand and interpret. Minimise on having too many colors since this can be distracting and overwhelming. Use colours carefully and only to show a particular point or to highlight a finding. Choosing the wrong chart can mean more questions than answers for your stakeholders, so choose carefully.
Beyond just having a collection of charts, modern dashboards have a mixture of different types of visuals to aid easy stakeholder understanding. For example, you could have different data ‘tiles’ that show key figures or trends. You may also want to incorporate key text descriptions of findings or trends in your dashboard. Having a mixture of different types of information can help your stakeholders greatly and avoid data saturation.
Step 4: Design the Dashboard
Once the objectives, metrics, and visualization techniques have been defined, the next step is to design the dashboard. The design should be intuitive and user-friendly, with the ability to drill down into the data to gain deeper insights. The dashboard should also be accessible to all stakeholders, including employees, managers, and executives.
Data visualisation is a discipline in itself. For a general overview and key tips on chart design and selection visit our article to learn more about data visualisation techniques.
To reduce manual work in constantly updating and producing the dashboard for your stakeholders think about leveraging technical solutions to do this for you. A common approach is to use excel spreadsheet and PowerBI. This may be feasible for some, but it often involves using a PowerBI expert (which may come at a cost), and any time you want to change the dashboard you need to loop back the expert to do it for you.
The Change Compass has incorporated powerful and intuitive dashboarding and charting features so that you do not need to be an expert to create a dashboard. Reference our templates as examples and create your own dashboard with a few clicks.
Step 5: Test and Refine the Dashboard
The final step in designing a change adoption dashboard is to test and refine it. This includes testing the dashboard with a small group of stakeholders and getting their feedback. Based on their feedback, the dashboard can be refined and improved until it provides the insights and data that stakeholders need to drive change adoption.
A key part of this step is testing any automation process in dashboard generation. Is the data accurate? Is it recent and updated? What operating rhythms do you need to have in place to ensure that the process flows smoothly, and that you get the dashboard produced every week/month/quarter?
Step 6: Continuously Monitor and Update the Dashboard
It is important to continuously monitor the change adoption dashboard and update it regularly. This will help to ensure that the dashboard remains relevant and provides the most up-to-date information on the progress of the change initiative.
The reality is that stakeholders will very likely get bored with the same dashboard time and time again. They will likely suggest changes and amendments from time to time. Anticipate this and proactively improve your dashboard. Does it drive the right stakeholder focus and conversation? If not, tweak it.
Good stakeholder conversations mean that your stakeholders are getting to the roots of why the change is or is not taking place. The data presented prompts the constant focus and avoids diversion in that focus. This is also a journey for your key stakeholders to find meaning in what it takes to lead the change and reinforce the change to get business results.
Summary
Designing an effective change adoption dashboard is a critical step in ensuring the success of change initiatives. By providing real-time data and insights into how well employees are adopting the change, a change adoption dashboard can help key stakeholders make informed decisions and take action to improve adoption rates. Ultimately it is about achieving the full initiative benefits targeted. By following the steps outlined in this article, change managers can design a change adoption dashboard that provides the insights they need to drive change adoption.
Building and executing a change adoption dashboard can be a manually intensive and time consuming exercise. Leverage technology tools that incorporates automation and AI. You will find that this can significantly increase the speed in which you are able to execute on not just the change dashboard, but driving the overall change delivery. For example, you can leverage out-of-the-box features such as forecasting and natural language query to save significant time and effort.
Have a chat to us about what options there are to help you do this.
Level 1: Air Traffic Control—Establishing Oversight and Laying the Foundation Seasoned transformation and change practitioners know the challenge: senior leaders are rarely interested in “change training” but are critical to the success of your change portfolio. Their…
In today’s dynamic business environment, managing multiple changes simultaneously is the norm, not the exception. As change leaders and transformation experts, we’re expected to provide clarity, reduce disruption, and drive successful adoption—often across a crowded…
Section 1: What Change Maturity Looks Like – And How Data Made It Real Shifting from Capability Sessions to Data-Driven Check out our article on how to effectively manage change at the organisational level through driving organisational change maturity has been through capability sessions: workshops, training…
