A solution demo showcases a product’s features and benefits, allowing potential customers to see it in action. It’s crucial because it creates engagement, addresses specific pain points as a part of key business objectives, and illustrates how the solution meets the audience’s needs, ultimately driving conversion rates and building trust in your offering.
Digital collaboration tool (Zoom, Hangout)
IN-PERSON
Whiteboard
Markers
Post-it notes
Timer
Instructions for running this Playbook
1. Background
Solution demo is a critical part of an agile project. It helps to demonstrate to stakeholders what the end solution could look like and ensures alignment by providing them with objective evidence of solution performance and giving them an opportunity to engage and provide feedback on what the project team has been working on.
How do you prepare for a successful solution demo?
To prepare for a successful solution demo, start by understanding your audience’s needs and pain points. Customize the demo to address these specific challenges while clearly showcasing your solution’s unique features. Practice delivering the presentation, anticipate questions, and ensure all technical aspects function smoothly to create a seamless experience.
A key gap for solution demos without change management input is one that is often focused on the technical or process features. Effective solution demos are designed with the customer needs and stakeholders’ needs in mind and is focused to help them easily picture themselves or their colleagues using the solution. The session is ideally a joint-session with the rest of the project team in designing the demo.
2. Prep
The following are critical prior to conducting the solution demo design session:
User journey – To ensure this can be referenced and utilised to illustrate the journey the user will go through in using the solution
User role profiles – To ensure that critical user profiles are clearly understood so that these can be utilised to outline their usage journeys
Change approach or Change Canvas – To help illustrate critical aspects of how users will be engaged be supported to use the designed solution
Scheduling:
Schedule the meeting when you have evidence that the solution is on track to be presented in case the solution
Include key project team members such as the project manager, business owner, lead developer and business analyst. Also include business representatives from impacted business areas.
Organisation:
Prior to the session undertake the following preparation:
Research previous solutions demos and understand key questions and concerns, especially those aspects with a people and change component (vs. technical issues)
Anticipate concerns and sentiments of targeted business representatives
Talk to business representatives to understand the history of changes that they have been through, how the group has evolved over time through changes
TIP: DESIGN
Focus as much on what a typical experience would be like from an end-user perspective versus on the technicalities of the solution itself.
Position the various scenarios and challenges that the user faces and walk through how these are resolved by the solution.
A good way to demo less technically focused solutions would be through role-plays to show what the solution looks like.
TIP: WHAT TO AVOID
The solution demo is about showing what ‘works’ in a realistic way. It should never be a powerpoint deck walk through.
Following agile principles, the focus is on ‘showing’ versus ‘telling’. The stakeholders need to be able to ‘see’ the solution versus ‘being told’ about it.
3. Run the session
Intro – 5-10 min
Walk through the purpose of the session and why this is required. Emphasise how important it is to incorporate people and change considerations within solution demo design to ensure session success.
1. Discuss overall demo design – 10 min
Overall demo agenda and run-sheet
Length of the demo (normally an hour, or 2 hours for complex solution demos)
Scope of the demo or the portions of the solution to be demo’ed
Roles of team members involved in leading the demo
2. Discuss incorporating user journeys and user profiles in demo design – 15 min
Be focused on the exact portion of the user journey you are going to demo and be precise and clear
Select key user profiles for the demo to illustrate how users will use the solution. This makes the demo much more engaging and real. Ideally use no more than 3 user profiles in most situations for the core demo. For other roles you can also talk through at a high level key usage models
Be focused on the people component in painting a picture of what each user profile is, what challenges they have, and how the solution meets those challenges
Highlight key benefits of the solution as you walk through the user journeys
3. Incorporate change approach in demo design – 10 min
Identify key change approach to call out throughout the user journey:
Focus on painting a clear picture for stakeholders throughout the user journey in how users are supported throughout the change process
Mention key change activities at key junctures of the user journey such as town hall sessions, training sessions, using sandbox to become more familiar with the solution, being supported by change champions, etc.
4. Incorporate key readiness and adoption measurement approaches – 10 min
Identify key change readiness and adoption measurement approaches and call these out and incorporate within the demo. The key is not to go overboard and focus too much on the details. Instead, highlight how solution usage is being measured and behaviours reinforced to achieve overall project objectives. For example:
Overview how change adoption is tracked during the user journey walkthrough
Highlight any behavioural reinforcements to sustain the change as a part of the user journey
Overview how change readiness is measured and reported as a part of the user journey
5. Capturing outcomes and actions required – 5 min
At the end of the session, capture key actions required, timeline required, and a follow up session as required.
What to do with the output?
After you’ve written up key agreements and solution demo run-sheet incorporating those design elements discussed, send these to various project stakeholders. Follow-up with action owners to get ready for the solution demo session.
Finding the right organisational change management software can be overwhelming and daunting. We break down some of the key steps to guide you in the right direction.
To save you feeling innundated by various vendor information, or various relevant stakeholder requests, sit back and focus on what’s the most important.
A key starting point is to decide what will make the most difference to your organisation and where the biggest pains are.
This may go against the standard Procurement process that focused on listing as many features as possible. Instead, its about core strategic focus on the top most critical change management problems.
As you start to explore different change management software solutions. These are the key questions to answer as you go along.
How do I ensure I address the right business problems?
1. Determine which transparent business problems have the biggest impact on the change management process. Key areas to look at include time savings, business value created, benefit realisation, risk assessment, employee experience, and business performance. Which aspect of change does this impact?
2. Avoid having a long and exhaustive list of business problems to address and features to look for. No one tool will address all needs, so it’s about the must-haves versus the nice to haves.
3. Prioritise the importance of various business problems and how they impact change management strategies. Ideally form no more than the top 1-3. This will help you become focused. It also ensures your efforts are targeted.
How do I find out about solutions on the market?
1. Search on Google, using popular search terms such as organisational change management software, change heatmap, single view of change, change management deliverables, enterprise change management software.
Be clear in terms of whether you are after an enterprise or portfolio level tool, or a project delivery type of tool.
2. Review change management software compilation pages such as this, or this.
3. Review any vendor presence in change management associates such as ACMP (Association of Change Management Professionals) or CMI (Change Management Institute). For example, do they have expertise in partnering with the association in developing course materials?
4. Search or ask questions on Linkedin Groups such as those for ACMP, CMI or Organizational Change Practitioners.
How do I get the budget?
To gain the budget and stakeholder approval you are looking for to invest in a change management tool, you need to ensure you have a very clear business case.
1. Estimate the size of the problem. How much cost is the problem causing? If not cost, then time saving, benefit achieved, or business performance levels impacted.
Be as quantitative as possible so that it is easy for your stakeholders to see the importance of the problem and how it aligns with the company’ss key performance indicators. If you would like to calculate the financial benefit of managing a change portfolio across change plans and types of changes visit this article.
E.g. Performance drops can be 10-20% (which can translate to millions of $) from the impact of changes. Managing change across the portfolio is one of the few ways to manage this significant risk. Read more here.
2. Identify the top stakeholders most impacted by the business problem and involve them. For example, if you are dealing with change saturation from change management activities, find the senior business leader most impacted by this pain and involve him/her in the process to gain their support.
3. Involve relevant departments that may impact the budget decision such as PMO, business heads, Procurement, IT, etc.
Some examples include:
– Cost savings in change management efforts including analyst support/resources, and manual time required in data collection, cleansing, data entry, data analysis and report production.
– Cost of business disruptions resulting from lack of data to support business decisions. We’ve found that often one individual instance of using data to make the right business decision can create millions in value
– Building business change capability through the ability to see and prepare for change, and iterate change interventions based on data
– Support speed of decision making and insight generation from weeks to minutes
How do I ensure the features will meet my needs?
1. Link desired features to your prioritised business problems. In this way you are focused on the most important features that will make the most difference for your organisation. Don’t be tempted to have a super long and exhaustive list of requirements with all aspects of change since this may increase cost, narrow down your vendor choice considerably, or worse, end up with a tool where you may not use most of the features. For examples, if the need more about workflow automation software or change project management software in coming up with templates for the change management plan for a change program, or about solving business leader problems?
2. Balance current urgent business needs with emerging business challenges. By choosing an organisational change management tool you are choosing to leverage this in the future for scalability. Be considered in understanding what is needed today, versus what may be needed in 1 or 2 years time. Ensure your change tool will support your emerging needs. For example, as you start to build more data and insights, does your tool have AI features to support trend analysis and forecasting?
3. Determine what is right for your business in terms of their change management capabilities and maturity. Depending on the tool that you select, it may support your change maturity focus in managing the impact of change initiatives. Decide not only whether the tool is easy to use for your business stakeholders (who may or may not be familiar with change management terms and practices). Also, ensure that as you build business change maturity, that the tool can continue to provide value to further the maturity.
4. Build your requirement list, again focused on must-have first before nice to haves before more advanced features. Examples include: service performance levels, data and security, risk management, ease of data access, modes of data input/export, automation, AI/machine learning, ease of integration, etc.
Which provider is the best for me?
Other than technical features and product design, there are other considerations in determining whether the software is right for you and your organisation. Here are some examples:
– How long has company been in operations for?
– What’s the background of the founder and how knowledgeable about the subject matter is he/she based on experience?
– Is there a structured onboarding process including training programs?
– Are the tangible outputs and documentation of the tool overly simplistic? And is there a range of proven analytics visuals that draw out the visibility of key risks and support different types of decision making
– What are the support channels? (e.g. self-help articles, digital Q&A support, user community, etc.)
– Is there a sandbox to trial the tool before signing up?
– How easy is it to administer and maintain? (e.g. if the org. structure changes). Are there automation features or do I need to do manual data entry?
– Must I purchase consulting along with the tool? And is it methodology agnostic?
– What is the annual system down time and what is the notification process?
– Does the tool support the capture of range of change types, including IT change management, operations changes, BAU normal changes, or standard change that happens seasonally during the year
– Do I need integration? Does it integrate with Microsoft Azure, Atlassian Jira Service Management, etc.?
– Is there continuous improvement improvement in the tool roadmap?
– Is the tool more designed for project teams, or from the lenses of business stakeholders?
– Looking at the blog section, does the provider show advanced change management understanding and experience? Or is it superficial?
– What are the AI/Automation features? How are data insights obtained? Are there potential issues if my team has low capability in analytical skills?
When is the right time?
It depends on your business priorities. Most businesses will always have multiple priorities. You need to be clear to what extent the business priority you are solving is critical to the success of your role.
For example, if the business priority is change saturation and limited capacity, then this priority will likely no go away. Even if there are other important business priorities, your role in the longer term may be measured by to what degree you have solved the organisational pains related to change.
We’ve seen lots of examples where the business directly intervenes to solve their pains, if this was not solved by the change team.
Using a software is like eating a buffet. Yes, it might take a long time to be able to sample all the various dishes and feel full and satisfied. However, you don’t need to eat everything in the buffet to start to enjoy the food. Pick your low hanging fruit, the ones that will directly address your business pain quickly. The rest, including building capability, can wait, and will take time.
Should I build in-house or buy?
Again it depends on where you are and the business problems you are trying to solve. If you have a mature change practice, and what the needs are
Be clear about the time you have to solve the business problem. What is the cost of not solving the business problem swiftly? How does this af
However, note that to build a tool in-house there are several considerations:
– Time and resources it takes to design, and continually improve the product. Like any system products it needs constant attention and resources for improvement and gradual maturity. The first iteration will usually not satisfy all your requirements
– Technical resources to design the user interface, technical development, infrastructure alignment, and testing for the product
– Ongoing total cost of ownership including technical development and support, product development, architecture support, infrastructure/system maintenance cost
– Business stakeholder resources for input and testing
– Risk of building a tool that is overly detailed and cumbersome to maintain
– Disadvantage of not being able to leverage industry best practices from constant user feedback that external tools have
Frequently Asked Questions
What does change management software do?
Change management software helps organisations plan, track, and measure change initiatives across their portfolios. Core functions typically include change impact assessment, stakeholder mapping, change capacity planning, and adoption tracking. More advanced platforms aggregate data across multiple concurrent initiatives, giving change leaders a portfolio-level view of risk and readiness.
How much does change management software cost?
Pricing for change management software varies widely depending on the scale of use and feature set. Entry-level tools typically start from a few hundred dollars per month, while enterprise-grade platforms with portfolio management capabilities are priced per user or per initiative. Most vendors offer custom pricing – requesting a demonstration is the most reliable way to get a quote aligned to your specific requirements.
What should I look for when selecting change management software?
The most important criteria are alignment with your primary use case, ease of stakeholder reporting, and integration capability with your existing project and HRIS tools. For organisations managing multiple concurrent changes, portfolio visibility – the ability to see aggregated change load across the business – is the most critical feature to evaluate.
How is change management software different from project management software?
Project management software tracks tasks, timelines, and resources. Change management software tracks the human side of change: who is impacted, how ready they are, how quickly they are adopting new ways of working, and whether expected business outcomes are being realised. The two are complementary rather than substitutes.
As the global landscape continues to evolve, so too does the field of change management. The 2020s promises a shift in the way organizations approach change, driven by a combination of economic factors, continued technological advancements, and the ever-increasing need for adaptability. In this article, we explore the background factors influencing the upcoming changes, and delve into seven key predictions that are set to reshape the realm of change management in the coming year.
Inflation Continue to Drop: A Ray of Economic Hope
One of the pivotal factors shaping the economic landscape in mid 2020s is the anticipated drop in inflation. After grappling with economic uncertainties, organizations can breathe a sigh of relief as the pressure from rising costs eases. This economic respite paves the way for strategic investments and initiatives, creating a conducive environment for change.
Avoiding Recession: Building Resilience Through Change
The specter of recession has loomed large in recent years, casting a shadow on organizational stability. However, as we step into the mid 2020s, the concerted efforts to avoid recession is forecasted to have paid off. Organizations have become more resilient, honing their ability to weather economic storms through strategic change initiatives. This backdrop sets the stage for a transformative year in change management.
Background
Agile Change as Business as Usual
In the 2020s, the concept of Agile Change is no longer a mere ‘work in progress’ but rather an integral part of Business as Usual (BAU). Organizations have recognized the need for agility in the face of rapid change, and Agile change methodologies have transitioned from experimental to foundational. This shift represents a change in mindset, emphasizing iterative processes, collaboration, and responsiveness to evolving circumstances. After more than 10 years of agile project methodology in the market place, agile change practices are starting to become ‘the norm’.
The Rise of Adaptive/Hybrid Change Models
Building on the previous point, agility applies beyond at an ‘intra-methodology’ perspective, but also how change approaches and methodologies need to be mixed and matched to work.
The increasing pace of change demands a more flexible approach from change practitioners. The dichotomy between structure and flexibility, innovation and process-focused strategies, gives rise to adaptive and hybrid change models. The emergence of terms like “wagile” (a fusion of waterfall and agile) underscores the need for a balanced approach that combines the best of both worlds. Organizations must strike a delicate balance between structure and flexibility to navigate the complexity of modern change initiatives.
For example, in regulated business functions there may need to be quite rigid planning of exactly when the changes must take place as well as the level of consultation and engagement required. However, the actual design of different engagement, positioning and employee involvement strategies may be tested in an iterative way.
Expanding Skill Sets for Change Practitioners
To meet business needs change practitioners will need to have a broader range of skills beyond ‘people skills’. In the 2020s, the demand for change professionals with a broader skill set encompassing strategic thinking, digital/data literacy, and business acumen will continue to be on the rise. As change initiatives become more complex, practitioners must equip themselves with multifaceted skills to address the diverse challenges that emerge during the change process.
For example, stakeholders are increasingly looking for data for reporting purposes to get a clearer sense of how changes are tracking. Beyond sentiments and opinions, stakeholders are looking for adoption indicators as well as precise indications of the nature of impacts across the employee population.
The Ascendance of Change Portfolio Management
Change portfolio management will continue to gain increasing visibility and importance in the 2020s. Organizations are recognizing the need to manage change initiatives collectively, aligning them with strategic objectives. The holistic oversight provided by change portfolio management enables organizations to prioritize, monitor, and evaluate change initiatives in a comprehensive manner, ensuring that resources are optimally allocated for maximum impact.
Whilst stakeholders may not be clear of the differences between transformation, portfolio management and change portfolio management, they are clearer of the benefits required in managing people impacts, against the need to maximise business performance and change adoption.
Leveraging Change Data for Informed Decision-Making
In the evolving landscape of change management, data is no longer just a nice-to-have; it’s a necessity. In the 2020s, the norm becomes leveraging change data to make informed decisions. Organizations recognize the value of data analytics in understanding the impact of change, identifying patterns, and proactively addressing challenges. This data-driven approach enhances the efficacy of change initiatives and provides a foundation for continuous improvement.
It is no longer that the expectation for data-led decision making rests in project functions such as technical development, business analysis, testing and user-experience. Change management teams are also expected to demonstrate the impact of their work through data.
Increasing Use of Software in Change Implementation
The leverage of software in change implementation should see an uptick in the 2020s, along with general increase in software usage rates in organisations. Organizations are leveraging technology to streamline and enhance various aspects of the change management process. From change project management tools, change measurement platforms, as well as change portfolio management tools the role of software can accelerate the pace of change initiatives and supports the realisation of benefits.
AI for Change: From Wait-and-See to Full Adoption
As new technologies, Artificial Intelligence (AI technology) and machine learning for change management is no longer a ‘wait-and-see’ proposition; it’s a reality in the 2020s. In terms of use of technology, at early 2020s a lot of users have sat on the fence as others argue about the risks and data privacy and intellectual property in using AI and data security. The launch of Microsoft Co-pilot and the continued adoption of Chat GPT 4 signal a paradigm shift in how organizations approach AI. Users will over time be used to asking a chat bot, using prompts to form analysis and other AI features to augment their work. Advanced AI change tools incorporating generative AI and automation can also assist in decision-making, predictive analytics, and even virtual facilitation, revolutionizing the efficiency and effectiveness of change processes.
In addition, there will be significant interest in change management tools that have incorporated AI features, from data and trend analysis, risk analysis to recommendations on change approaches. Though the accuracy of current models of AI including ChatGPT and other OpenAI models may not be 100% accurate and may feel that there is a long way to go, natural language processing algorithms continues to improve quite quickly.
How will technology shape our lives in the next decade?
In the next decade, technology will significantly reshape our lives by enhancing connectivity, automating tasks, and enabling smarter decision-making. Advances in AI, IoT, and sustainable tech will drive efficiency and innovation, ultimately transforming industries and the way we interact with our environment and each other.
As organizations navigate the complexities of the 2020s, change management emerges as a critical linchpin for success. The predictions outlined in this article reflect an emerging shift in the approach to managing change, from the integration of Agile methodologies to the widespread adoption of AI. Change practitioners must equip themselves with a versatile skill set to thrive in this dynamic environment, where strategic thinking, digital literacy, and adaptability are paramount. As we stand on the cusp of a transformative year, organizations that embrace these predictions are poised not only to weather the winds of change but to harness them for sustained success.
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.
