In the world of scaled agile, “Release on Demand” is a concept that has profound implications for agile teams and their project approaches. It guides teams on how to release and deliver value when stakeholders and customers are truly ready to receive it. However, a crucial, often-overlooked factor in this concept is the role of change management. While Release on Demand has primarily been framed as a technical approach within the Scaled Agile Framework (SAFe), the readiness of people—including end-users, stakeholders, customers, and partners—forms an equally vital part of determining the demand for release.
As change management practitioners, understanding and actively shaping “Release on Demand” can significantly impact project outcomes. In this article, we’ll explore how change management can enhance this core SAFe concept through strategic timing, prioritisation, and thoughtful execution of each release. We’ll also discuss how to structure governance cadences to ensure operational and people readiness, going beyond the technical lens.
Understanding Release on Demand in SAFe
Within SAFe, Release on Demand means that project outputs or new functionality are delivered when the organisation, teams, and stakeholders are ready to adopt and benefit from it. It enables flexible delivery rather than a rigid release schedule. The four key activities for Release on Demand are:
Release – Delivering the product or change to users.
Stabilise and Operate – Ensuring the release is operationally sound and running smoothly.
Measure and Learn – Assessing the release’s impact and learning from the results.
Adjust – Making necessary improvements based on insights gained.
The goal of these activities is to minimise risk, gather user feedback, and optimise the release to maximise impact. While these steps seem straightforward, they demand thoughtful change management to ensure all stakeholders are prepared to support, use, and benefit from the release. Let’s delve deeper into how a change management approach can strengthen each of these activities.
People Readiness as the Core Demand Factor
The “demand” for a release is often misunderstood as being purely about project or market readiness. However, the reality is that it depends on multiple factors, including how ready people are to adopt the change. For any release to succeed, people readiness is crucial and requires focus on:
End-User Readiness: Ensuring that end-users are prepared for the new tools, processes, or functionalities. This could mean conducting user training, crafting support resources, and managing expectations.
Stakeholder Readiness: Stakeholders at all levels need to understand the change, its rationale, and its anticipated impact. This may involve regular briefings, updates, and even individual consultations.
Customer and Partner Readiness: For customer-facing or partner-facing releases, it’s essential to gauge external readiness as well. A clear communication plan and alignment of goals with partners or clients can smooth the path for a successful launch.
These readiness efforts form a significant part of the “demand” in Release on Demand and reflect the reality that people’s capacity to adapt often determines when a release will be genuinely effective.
The Broader Change Landscape
People readiness isn’t only determined by a single project or team but by the broader change landscape within an organisation. Multiple changes or ongoing initiatives can either enhance or inhibit readiness for a new release. For instance, if an organisation is already undergoing a significant digital transformation, adding another change may lead to overload and resistance.
Change practitioners should map the change landscape to identify concurrent changes and evaluate how these may impact readiness for Release on Demand. By assessing the timing and impact of other changes, change managers can:
Avoid change fatigue by spacing out initiatives.
Synchronize related changes to reduce redundancy.
Communicate the overall strategic direction to help stakeholders and users understand how individual changes fit into the bigger picture.
By accounting for these interdependencies, change management can improve people readiness and ensure the Release on Demand aligns with the organisation’s capacity to handle it.
Applying the Four Key Steps in Release on Demand
Let’s explore how change management activities can amplify each of the four Release on Demand steps:
1. Release: The release phase requires both technical and people preparation. Beyond deploying the technical elements, change management practitioners should:
Develop targeted communication plans to inform all affected stakeholders.
Offer targeted training sessions or resources that build users’ confidence and competence.
Ensure adequate support is in place for the transition, including help desks or peer mentoring.
2. Stabilise and Operate: After a release, it’s crucial to monitor adoption and support operational stability. The change team can:
Collect feedback from end-users and support staff on initial challenges and address these promptly.
Identify and celebrate quick wins that demonstrate the release’s value.
Work closely with operations teams to resolve any unforeseen issues that may inhibit adoption or cause frustration.
3. Measure and Learn: This step goes beyond tracking technical metrics and should also capture change-specific insights. Change management can contribute by:
Conducting surveys, interviews, or focus groups to gauge user and stakeholder sentiment.
Monitoring adoption rates and identifying any training gaps or knowledge shortfalls.
Collaborating with product or project teams to share insights that may refine or prioritisation subsequent releases.
4. Adjust: Based on insights gained from the Measure and Learn phase, change managers can advise on necessary adjustments. These might include:
Refining future communication and training plans based on user feedback.
Addressing any gaps in stakeholder support or sponsorship.
Adjusting the timing of subsequent releases to better align with people readiness.
The iterative nature of these four steps aligns well with agile methodologies, allowing change managers to continuously refine and enhance their approach.
The Critical Role of Sequencing, Prioritisation, and Timing
For change management practitioners, Release on Demand isn’t just about executing steps—it’s about doing so in the right sequence and at the right time. The impact of a release depends significantly on when it occurs, who is prepared for it, and how well each group’s readiness aligns with the release cadence.
Here are some tips to help change managers get the timing right:
Analyze stakeholder engagement levels: Regularly assess how engaged and ready stakeholders are, tailoring messaging and interventions based on their feedback and sentiment.
Prioritisation change activities based on impact: Not all releases will have the same impact, so change teams should focus resources on those that require the most user readiness efforts.
Create phased rollouts: If full-scale readiness across the board isn’t achievable, a phased rollout can provide users with time to adapt, while allowing the change team to address any emergent issues in stages.
By managing the release cadence thoughtfully, change managers can avoid the disruptions caused by hasty releases and ensure the deployment feels both manageable and meaningful for users.
Release governance in SAFe is often perceived as a predominantly technical or project-focused process. However, effective governance should encompass business operations and people readiness as well. Change management plays a pivotal role in designing governance cadences that account for these critical aspects.
To integrate change governance within release governance, change practitioners should:
Establish clear communication channels with project teams and product owners to ensure people readiness factors are consistently part of release discussions.
Implement a readiness checklist that includes technical, operational, and people readiness criteria. This checklist should be reviewed and signed off by relevant stakeholders before any release.
Maintain a cadence of review and feedback sessions where project teams, change managers, and stakeholders discuss readiness progress, key risks, and post-release outcomes.
This approach ensures that each release is evaluated from multiple perspectives, minimising disruption and maximising its potential for success.
The above is from Scaledagileframework.com
Developing a Change Cadence that Complements Agile Delivery
SAFe’s principle of “develop on cadence; release on demand” is central to effective agile delivery. For change management practitioners, developing a strong change cadence is equally important. This cadence, or rhythm of activities, aligns with the agile teams’ development cadence and helps build stakeholder momentum, maintain engagement, and reduce surprises.
Here’s how to develop a cadence that works in tandem with agile teams:
Planning Cadence: Hold regular planning sessions to align change activities with upcoming releases and identify readiness gaps. This could be quarterly for major releases or bi-weekly for smaller, iterative releases.
Execution Cadence: Establish a reliable cycle for change interventions, such as training, communication, and stakeholder meetings. This cadence helps stakeholders build expectations and fosters a predictable rhythm in change activities.
Feedback Cadence: Collect feedback at consistent intervals, aligning it with release intervals or sprint reviews. Consistent feedback keeps the change process agile and responsive to evolving needs.
A well-defined change cadence not only prepares users effectively but also reinforces trust and transparency in the change process.
Release on Demand may have originated as a technical concept within SAFe, but its success is deeply tied to how well people, stakeholders, and users are prepared for each release. For change management practitioners, Release on Demand is an opportunity to enhance the broader release process by prioritizing people readiness, orchestrating thoughtful sequencing, and establishing governance that prioritisations user success as much as project outcomes.
By proactively engaging in each of the four stages of Release on Demand—Release, Stabilise and Operate, Measure and Learn, and Adjust—change management can ensure releases are not just technically ready but fully integrated into the people and business context they serve. Embracing this role allows change managers to become essential partners in agile delivery, maximising the impact of each release for end-users, the organisation, and the overall success of the project.
Change management practitioners are often tasked with ensuring that transitions are smooth and successful. However, to truly excel in this role, it’s crucial to embrace a systems thinking approach—an understanding that organisations are complex, interconnected systems where every change can create ripple effects throughout. One of the most potent tools for fostering systems thinking is the use of change data within change portfolio management. Here, we will focus on how change data can build interconnectedness across the organisation, enhance the management of change initiatives, and ultimately improve business results.
Understanding Systems Thinking
The below are some of the core principles in Systems Thinking and how they may be applied to change portfolio management through data and analysis.
Principle 1: Interconnectedness
At the core of systems thinking is the principle of interconnectedness. Organisations are not merely a collection of individual parts; rather, they consist of various components that interact in complex ways. When change is initiated in one area, it can have unintended consequences in another. For instance, a change in the sales strategy might impact customer service processes, employee motivation, and even supply chain operations. By recognising these interconnected relationships, practitioners can make more informed decisions that take the broader organisational context into account.
In fact, change impact assessment is the process of identifying and ascertaining the linkages across the system. With each change, the various impacts across different processes, people working to support those processes and the systems involved in the processes.
Principle 2: Feedback Loops
Another fundamental aspect of systems thinking is the identification and understanding of feedback loops. These loops can be either reinforcing (positive) or balancing (negative). A reinforcing feedback loop occurs when a change in one part of the system leads to further changes in the same direction, creating a cycle of growth or enhancement. For example, an increase in employee training may lead to improved performance, which in turn boosts morale and reduces turnover, further enhancing overall productivity.
Conversely, balancing feedback loops act to stabilize the system. They can dampen the effects of change, preventing extremes from occurring. Recognising these feedback mechanisms allows practitioners to leverage positive feedback loops to enhance desired outcomes while being vigilant against the negative loops that may emerge, which could undermine the change initiatives.
Here is an example of a feedback loop –
Goal: Prevent stagnation or failure by adjusting strategies based on real-time feedback.
Use case: Ensuring that deviations or resistance are managed effectively to keep the change on track.
How it works:
Collect data from employee surveys, performance metrics, and feedback sessions to understand what’s working or not.
Identify points of resistance and take corrective actions (e.g., additional training or clarifying leadership vision).
Example: If employees express frustration with new tools, gather input and refine the rollout to address concerns.
What are key benefits of feedback loops?
Increased adaptability: Ensures the organisation can react to unforeseen challenges during implementation.
Engaged workforce: Employees feel more involved when they see their feedback incorporated into the process.
Sustainable change: Continuous feedback ensures that change efforts stay relevant, preventing them from losing momentum or being abandoned.
Principle 3: Causality
Systems thinking also emphasizes understanding causality—how different components of the organisation influence one another. This perspective is vital in change management, as it shifts the focus from merely addressing symptoms of problems to exploring their root causes. This can be applied throughout the change lifecycle ranging from understanding the impacts across the organisation, through to anticipating resistance and motivation levels to support the change.
Here is an example of applying the principle of causality in systems thinking
Change Initiative: Implementing a New KPI-Based Evaluation System
Initial Cause: Leaders decide to replace the existing subjective performance reviews with measurable KPIs to improve accountability.
Direct Effect: Employees shift their focus to achieving their KPIs.
This change seems positive—employees now have clear, measurable targets to meet.
Ripple Effects Across the System:
Short-term unintended outcome: Employees may begin to focus only on achieving their KPIs, ignoring tasks that are not directly rewarded, such as collaboration or innovation.
Behavioural impact: Some employees might feel micromanaged or disengaged if they view the new system as rigid or unfair.
Team dynamics: Competitive behaviour between employees could increase, reducing collaboration and creating silos.
Long-term Causal Feedback:
Lower collaboration can negatively affect innovation and employee morale, leading to attrition of high performers.
A balancing feedback loop emerges when HR notices a decline in collaboration scores and recommends revising KPIs to include teamwork-related metrics.
Principle 4: Holistic Perspective
Adopting a holistic perspective is crucial in systems thinking. Instead of viewing the organisation as a set of isolated parts, practitioners should consider the organisation as a dynamic whole. This approach enables better problem-solving and decision-making by considering all relevant factors and their interactions. A holistic view facilitates a deeper understanding of how changes in one area may impact others, ultimately leading to more sustainable and effective change initiatives.
For example, An organisation is running several parallel initiatives under a broader digital transformation effort, including:
CRM System Implementation
Agile Ways of Working Initiative
Cloud Migration for Core IT Systems
Employee Upskilling Program on Digital Tools
Application of Holistic Perspective
Identifying Interdependencies
The CRM system needs to integrate with both legacy IT infrastructure and future cloud platforms.
The agile transformation affects how teams work, influencing the success of the CRM project and cloud migration by demanding faster collaboration cycles.
The upskilling program needs to ensure employees are trained not only in new digital tools but also on agile practices and cloud-based platforms.
Avoiding Initiative Silos
Without a holistic view, each project might focus only on its own goals, causing schedule conflicts (e.g., IT resources are overbooked for the cloud migration and CRM deployment).
Teams might experience change fatigue if initiatives are rolled out simultaneously without coordination. For example, employees may struggle to participate in the upskilling program while also meeting deadlines for the agile rollout.
Portfolio-Level Governance and Prioritization
Using a holistic lens, the portfolio management team can sequence projects logically. For example:
First: Migrate critical systems to the cloud to ensure the CRM implementation has a stable foundation.
Second: Begin the agile transformation to align working methods before launching cross-functional CRM initiatives.
Third: Schedule employee upskilling to ensure readiness before key milestones in the CRM and cloud projects.
Optimizing Resources and Reducing Risks
Viewing the portfolio holistically allows management to optimize resource allocation (e.g., sharing skilled IT personnel across cloud and CRM projects efficiently).
By aligning initiatives, the company mitigates the risk of conflicting efforts and reduces change fatigue through coordinated communication and engagement plans.
Principle 4: Emergence
Finally, the concept of emergence in systems thinking highlights how complex behaviours can arise from simple interactions among components. The principle of emergence in systems thinking refers to the idea that when individual elements interact, new patterns or behaviours emerge that were not predictable by examining the parts alone. In change portfolio management, this means that the outcomes of managing multiple change initiatives may be different—often more complex or unexpected—than the sum of each individual change project. Emergent behaviours can create both opportunities and risks.
Scenario: Managing a Sustainability Transformation Portfolio
A large organisation launches several interconnected initiatives to become a more sustainable enterprise:
Carbon Reduction Initiative – Shift to renewable energy and reduce emissions.
Sustainable Supply Chain Project – Engage suppliers on environmental standards.
Green Product Innovation Program – Develop eco-friendly products.
Employee Engagement Initiative – Promote green behaviours among employees.
Application of Emergence
Unexpected Synergies Emerge
Employees participating in the engagement initiative start identifying operational inefficiencies, such as excess waste, leading to additional cost savings.
The green product innovation program creates a culture of experimentation that spills over into other departments, resulting in improved collaboration and faster innovation cycles across the organisation, beyond sustainability-focused efforts.
Emergent Risks and Complex Interactions
Suppliers struggling to meet new sustainability requirements may delay the sustainable supply chain project, impacting both product launches and company operations.
Employees feel overwhelmed by the number of sustainability programs and resist further change, creating unexpected resistance that spreads to unrelated initiatives, such as digital transformation efforts.
New Opportunities Emerge from Interactions
As cross-functional teams work together, new business models emerge. For example, sales and product teams discover that green products appeal to a new customer segment, leading to revenue growth opportunities not originally anticipated in the change portfolio plan.
Collaborations with suppliers in the supply chain project uncover the potential for joint ventures focused on sustainable technology.
It may not be possible to forecast or anticipate all types of employee behaviours and reactions to new changes introduced. However, engaging your stakeholders and involving them in the change process may help you identify these in advance.
The Role of Change Data in Building Systems-Thinking Within Change Portfolio Management
Change portfolio management involves overseeing a collection of change initiatives and ensuring that they align with the organisation’s strategic objectives. The integration of change data into this process can significantly enhance systems thinking capabilities.
Creating a Data-Driven Culture
One of the first steps in leveraging change data is to establish a data-driven culture. Practitioners should promote the importance of data in decision-making processes across the organisation. By providing visibility of the changes that are upcoming, they can empower employees at all levels to utilize change data in their daily work. This cultural shift fosters an environment where data becomes a common language, allowing for clearer communication about changes and their potential impacts. However, do note that different type of employees may require different type of data.
Mapping Change Initiatives
Using change data, organisations can create visual maps of their change initiatives. These maps can illustrate how different initiatives are interconnected and highlight the dependencies between them. For example, a visual representation can show how a new software implementation relies on training programs or how changes in one department may impact others. By visualizing these relationships, practitioners can better assess the potential ripple effects of changes and make more informed decisions.
Monitoring and Analysing Feedback Loops
By actively monitoring change data, organisations can identify and analyse feedback loops in real-time. This ongoing analysis allows practitioners to quickly respond to emerging trends or unintended consequences. For instance, if data shows a decline in employee productivity following a process change, practitioners can investigate and implement corrective actions before the situation worsens. By understanding these feedback loops, organisations can not only react to changes but also proactively shape their outcomes.
Causal Analysis
Incorporating change data into causal analysis enables organisations to identify the root causes of issues. Practitioners can use data analytics to explore the relationships between different components of the organisation, leading to a clearer understanding of how changes impact various outcomes. This data-driven approach allows for more targeted interventions, ensuring that efforts are directed towards addressing the underlying issues rather than merely treating surface-level symptoms.
Holistic Change Portfolio Assessment
When practitioners evaluate their change portfolio, they should adopt a holistic approach that considers the interplay between various initiatives. By analysing change data in aggregate, organisations can identify patterns and trends that may not be visible when examining initiatives in isolation. This holistic assessment allows practitioners to prioritise initiatives that align with broader organisational goals, ultimately leading to more effective change management.
Fostering Collaborative Environments
Change data can also be a catalyst for fostering collaborative environments. By sharing insights and findings from change initiatives, organisations can create a culture of collaboration where teams learn from one another’s experiences. This exchange of information can lead to emergent solutions that drive innovation and improve change outcomes. Additionally, collaborative tools and platforms can be leveraged to facilitate communication and knowledge sharing across departments.
Building Connectedness Across the Organisation
The integration of change data into change portfolio management fosters interconnectedness within the organisation. By emphasising the importance of data and encouraging collaboration, practitioners can create a more cohesive organisational culture that embraces change.
Enhancing Communication
Clear communication is essential for effective change management. Change data provides a foundation for transparent communication about initiatives and their impacts. Practitioners can use data visualizations and reports to communicate progress, challenges, and successes, fostering a sense of shared understanding across the organisation.
Breaking Down Silos
Change data can also help break down silos within the organisation. By sharing data and insights across departments, practitioners can encourage collaboration and foster a sense of unity. This interconnectedness enhances problem-solving capabilities, as diverse teams bring different perspectives to the table, leading to more innovative solutions. Issues may be pre-empted if stakeholders can pick up on impacts that may be missed for example.
Aligning Goals and Objectives
When change initiatives are informed by change data, it becomes easier to align goals and objectives across the organisation. Practitioners can use data to ensure that all initiatives are working towards the same strategic objectives, reducing the likelihood of conflicting priorities. This alignment creates a more focused approach to change management, ultimately leading to improved business results.
Improving Business Results Through Systems Thinking
The application of systems thinking through change data in change portfolio management can lead to substantial improvements in business results. By fostering interconnectedness, enhancing communication, and breaking down silos, organisations can create a more agile and responsive environment.
Increased Agility
Organisations that embrace systems thinking and utilize change data are better equipped to respond to changes in the external environment. By understanding the interconnectedness of their initiatives, practitioners can pivot quickly in response to emerging trends or challenges. This agility is essential in today’s fast-paced business landscape.
Enhanced Employee Engagement
When employees see their work as part of a larger, interconnected system, they are more likely to feel engaged and motivated. By involving employees in the change process and using data to demonstrate the impact of their contributions, organisations can foster a sense of ownership and commitment to change initiatives.
Improved Decision-Making
Systems thinking promotes better decision-making by encouraging practitioners to consider the broader context of their actions. When decisions are informed by change data, organisations can identify potential consequences and make choices that align with their strategic goals. This improved decision-making ultimately leads to more successful change outcomes.
Sustainable Change Initiatives
Finally, the application of systems thinking and change data can lead to more sustainable change initiatives. By focusing on root causes, leveraging feedback loops, and fostering collaboration, organisations can implement changes that are not only effective in the short term but also sustainable over time. This sustainability is crucial for long-term business success.
Change data is a powerful lever that change management practitioners can use to foster systems thinking within their organisations. By recognising the interconnectedness of change initiatives, understanding feedback loops, exploring causality, adopting a holistic perspective, and nurturing environments for emergence, organisations can improve their approach to change management. Through these efforts, practitioners can build connectedness across the organisation, ultimately enhancing how change is managed and driving improved business results. Embracing systems thinking in change portfolio management is not just a best practice; it’s a necessity for organisations seeking to thrive in an ever-evolving business landscape.
Change managers are not just facilitators of change transition; they are strategic partners who must understand and navigate complex organisational landscapes. One key skill that is often under-emphasised in this role is analytical capability. By adopting a strategic consultant’s mindset and employing robust analytical skills, change managers can significantly enhance their effectiveness throughout the project lifecycle. Let’s explore how change managers can leverage analytical skills at each phase of the project lifecycle, emphasising frameworks like MECE and TOSCA to drive successful change initiatives.
The Importance of an Analytical Lens
Change management involves facilitating transitions while ensuring that stakeholders are engaged and informed. However, to do this effectively, change managers must analyse complex data sets, identify patterns, and make informed decisions based on evidence. This analytical lens can be applied through every stage of the project lifecycle: commencement, planning, execution, monitoring, and closure.
Gone are the days when change practitioners are making recommendations ‘from experience’ or based on stakeholder input or feedback. For complex transformation, stakeholders now (especially senior stakeholders) demand a more rigorous, data-driven approach to drive toward solid change outcomes.
1. Project Commencement Phase
At the project commencement phase, the groundwork is laid for the entire change initiative. Change managers need to scan the organizational environment through the lens of impacted stakeholders, gathering relevant information and data.
Example: Consider a company planning to implement a new customer relationship management (CRM) system. The change manager should begin by analysing the existing state of customer interactions, assessing how the change will impact various departments such as sales, marketing, and customer service. This involves conducting stakeholder interviews, reviewing existing performance metrics, and gathering feedback from employees.
Using a MECE (Mutually Exclusive, Collectively Exhaustive) framework, the change manager can categorize stakeholder concerns into distinct groups—such as operational efficiency, user experience, and integration with existing systems—ensuring that all relevant factors are considered. By identifying these categories, the change manager can articulate a clear vision and define the desired end state that resonates with all stakeholders.
The above is from Caseinterview.com
Hypothesis: Sales Team Will Resist the New CRM System Due to Lack of Training and User-Friendliness
Step 1: Identify the Hypothesis
Hypothesis: The sales team will resist the new CRM system because they believe it is not user-friendly and they fear insufficient training.
Step 2: Break Down the Hypothesis into MECE Categories
To validate this hypothesis, we’ll break it down into specific categories that are mutually exclusive and collectively exhaustive. We’ll analyse the reasons behind the resistance in detail.
Categories:
User Experience Issues
Complexity of the Interface
Navigation Difficulties
Feature Overload
Training and Support Concerns
Insufficient Training Programs
Lack of Resources for Ongoing Support
Variability in Learning Styles
Change Management Resistance
Fear of Change in Workflow
Previous Negative Experiences with Technology
Concerns About Impact on Performance Metrics
Step 3: Gather Data for Each Category
Next, we need to collect data for each category to understand the underlying reasons and validate or refute our hypothesis.
Category 1: User Experience Issues
Data Collection:
Conduct usability testing sessions with sales team members.
Administer a survey focusing on user interface preferences and pain points.
Expected Findings:
High rates of confusion navigating the new interface.
Feedback indicating that certain features are not intuitive.
Category 2: Training and Support Concerns
Data Collection:
Survey the sales team about their current training needs and preferences.
Review existing training materials and resources provided.
Expected Findings:
Many team members express a need for more hands-on training sessions.
A lack of available resources for ongoing support after the initial rollout.
Category 3: Change Management Resistance
Data Collection:
Conduct focus groups to discuss fears and concerns regarding the new system.
Analyse historical data on previous technology implementations and employee feedback.
Expected Findings:
Employees voice concerns about how the CRM will change their current workflows.
Negative sentiments stemming from past technology rollouts that were poorly managed.
Step 4: Analyse Data Within Each Category
Now that we have gathered the data, let’s analyse the findings within each MECE category.
Analysis of Findings:
User Experience Issues:
Complexity of the Interface: Usability tests reveal that 70% of sales team members struggle to complete certain tasks in the CRM.
Navigation Difficulties: Survey responses show that 80% find one step of the navigation counterintuitive, leading to frustration.
Training and Support Concerns:
Insufficient Training Programs: Surveys indicate that only 40% of employees feel adequately trained to use this part of the new system.
Lack of Resources for Ongoing Support: Focus groups reveal that team members are unsure where to seek help after the initial training.
Change Management Resistance:
Fear of Change in Workflow: Focus group discussions highlight that 60% of participants fear their productivity will decrease with the new system, at least during the post Go Live period.
Previous Negative Experiences: Historical data shows that past technology rollouts had mediocre adoption rates due to insufficient support, reinforcing current fears.
Step 5: Develop Actionable Recommendations
Based on the analysis of each category, we can create targeted recommendations to address the concerns raised.
Recommendations:
User Experience Issues:
Conduct additional usability testing with iterative feedback loops to refine the CRM interface before full rollout.
Simplify the navigation structure based on user feedback, focusing on the most frequently used features.
Training and Support Concerns:
Develop a comprehensive training program that includes hands-on workshops, tutorials, and easy-to-access online resources.
Establish a dedicated support team to provide ongoing assistance, ensuring team members know whom to contact with questions.
Change Management Resistance:
Implement a change management strategy that includes regular communication about the benefits of the new system, addressing fears and expectations.
Share success stories from pilot programs or early adopters to demonstrate positive outcomes from using the CRM.
By following this detailed step-by-step analysis using the MECE framework, the change manager can thoroughly investigate the hypothesis regarding the sales team’s resistance to the new CRM system. This structured approach ensures that all relevant factors are considered, enabling the development of targeted strategies that address the specific concerns of stakeholders. Ultimately, this increases the likelihood of successful change adoption and enhances overall organizational effectiveness.
Data-Driven Decision Making:
At this stage, change managers should work closely with the project sponsor and project manager to determine effective positioning. A data-driven approach allows the change manager to form a hypothesis about how the change will impact stakeholders. For instance, if data suggests that the sales team is particularly resistant to change, the manager might hypothesize that this resistance stems from a lack of understanding about how the new CRM will enhance their workflow.
2. Planning Phase
Once the project is initiated, the planning phase requires detailed strategy development. Here, analytical skills are essential for conducting stakeholder analysis and impact assessments.
Example: In our CRM implementation scenario, the change manager must analyse the data collected during the commencement phase to identify the specific impacts on different departments. This involves grouping and sorting the data to prioritize which departments require more extensive support during the transition.
Using the TOSCA (Target, Objectives, Strategy, Constraints, Actions) framework provides a structured approach to guide the change management process for the CRM implementation. This framework helps clarify the overall vision and specific steps needed to achieve successful adoption. Below is a detailed exploration of each component:
1. Target
Definition: The target is the overarching goal of the change initiative, articulating the desired end state that the organization aims to achieve.
Application in CRM Implementation:
Target: Improve customer satisfaction and sales efficiency.
This target encapsulates the broader vision for the CRM system. By focusing on enhancing customer satisfaction, the organization aims to create better experiences for clients, which is crucial for retention and loyalty. Improving sales efficiency implies streamlining processes that enable sales teams to work more effectively, allowing them to close deals faster and serve customers better.
2. Objectives
Definition: Objectives are specific, measurable outcomes that the organization intends to achieve within a defined timeframe.
Application in CRM Implementation:
Objectives: Increase customer retention by 20% within a year.
This objective provides a clear metric for success, enabling the organization to track progress over time. By setting a 20% increase in customer retention as a target, the change manager can align training, support, engagement and system adoption with this goal. This objective also allows for measurable evaluation of the CRM’s impact on customer relationships and retention efforts.
3. Strategy
Definition: The strategy outlines the high-level approach the organization will take to achieve the objectives. It serves as a roadmap for implementation.
Application in CRM Implementation:
Strategy: Implement phased training sessions for each department, with tailored support based on the unique impacts identified.
This strategy emphasizes a thoughtful and structured approach to training, recognizing that different departments may face distinct challenges and needs when adapting to the new CRM. By rolling out training in phases, the organization can focus on one department at a time, ensuring that each team receives the specific support they require. Tailoring the training content based on the unique impacts identified earlier in the MECE analysis helps maximize engagement and effectiveness, addressing concerns about usability and fostering greater adoption of the CRM.
4. Constraints
Definition: Constraints are the limitations or challenges that may impact the successful implementation of the strategy. Recognizing these upfront allows for better planning and risk management.
Application in CRM Implementation:
Constraints: Limited budget and time restrictions.
Acknowledging these constraints is critical for the change manager. A limited budget may affect the types of training resources that can be utilized, such as hiring external trainers or investing in advanced learning technologies. Time restrictions might necessitate a more rapid rollout of the CRM system, which could impact the depth of training provided. By recognizing these constraints, the change manager can plan more effectively and prioritize key areas that will deliver the most value within the available resources.
5. Actions
Definition: Actions are the specific steps that will be taken to implement the strategy and achieve the objectives.
Application in CRM Implementation:
Actions: Develop a communication plan that includes regular updates and feedback mechanisms.
This action focuses on the importance of communication throughout the change process. A well-structured communication plan ensures that all stakeholders, particularly the sales team, are kept informed about the implementation timeline, training opportunities, and how their feedback will be incorporated into the process. Regular updates foster transparency and help build trust, while feedback mechanisms (such as surveys or suggestion boxes) allow team members to voice concerns and share their experiences. This two-way communication is essential for addressing issues promptly and reinforcing a culture of collaboration and continuous improvement.
By applying these frameworks, change managers can make informed recommendations that align with organizational objectives. This structured approach helps ensure that all relevant factors are accounted for and that stakeholders feel included in the planning process.
3. Execution Phase
As the project moves into the execution phase, the change manager must remain agile, continually collecting organizational data to confirm or reject the hypotheses formed during the planning stage.
Example: In an agile setting, where iterative processes are key, the change manager should implement mechanisms for ongoing feedback. For instance, after each sprint of CRM implementation, the manager can gather data from users to assess how well the system is being received. Surveys, usage analytics, and focus groups can provide rich insights into user experiences and pain points.
This ongoing data collection allows change managers to adjust their strategies in real-time. If feedback indicates that certain features of the CRM are causing confusion, the change manager can pivot to provide additional training or resources targeted specifically at those areas. This iterative feedback loop is akin to the work of strategic consultants, who continuously assess and refine their approaches based on empirical evidence.
Example in Practice: Imagine a situation where the sales team reports difficulties with the new CRM interface, leading to decreased productivity. The change manager can analyse usage data and user feedback to pinpoint specific issues. This data-driven insight can guide the development of targeted training sessions focusing on the problematic features, thus addressing concerns proactively and fostering user adoption.
4. Monitoring Phase
Monitoring the change initiative is crucial for ensuring long-term success. Change managers need to analyse performance metrics to evaluate the effectiveness of the implementation and its impact on the organization.
Example: For the CRM project, key performance indicators (KPIs) such as sales conversion rates, customer satisfaction scores, and employee engagement levels should be monitored. By employing data visualization tools, change managers can easily communicate these metrics to stakeholders, making it clear how the change initiative is progressing.
A fact-based approach to analysing these metrics helps in making informed decisions about any necessary adjustments. If, for instance, customer satisfaction scores are declining despite an increase in sales, the change manager may need to investigate further. This might involve conducting interviews with customers or analysing customer feedback to identify specific areas for improvement.
Suppose the organization observes a drop in customer satisfaction scores following the CRM implementation. The change manager could work with other stakeholders to conduct a root cause analysis using customer feedback and service interaction data to identify patterns, such as longer response times or unresolved issues. By addressing these specific problems, the change manager can refine the CRM processes and enhance overall service quality.
5. Closure Phase
The closure phase involves reflecting on the outcomes of the change initiative and drawing lessons for future projects. This is where the analytical skills of change managers can shine in assessing the overall impact of the change.
Example: After the CRM system has been fully implemented, the change manager should conduct a comprehensive review of the project along with the project team (retro). This involves analysing both qualitative and quantitative data to evaluate whether the initial objectives were met. Surveys can be distributed to employees to gather feedback on their experiences, while sales data can be analysed to determine the financial impact of the new system.
Using frameworks like MECE can help in categorizing the lessons learned. For instance, feedback could be sorted into categories such as user experience, operational efficiency, and overall satisfaction, allowing the change manager to develop clear recommendations for future initiatives.
Lessons Learned: If the analysis shows that certain departments adapted more successfully than others, the change manager could investigate the factors contributing to this variance. For example, departments that received more personalized support and training may have demonstrated higher adoption rates. This insight can inform strategies for future change initiatives, emphasizing the importance of tailored support based on departmental needs.
Building Relationships with Senior Leaders
In addition to the technical aspects of change management, the ability to communicate effectively with senior leaders is crucial. Seasoned change managers must clearly understand organizational objectives and be able to articulate how the change initiative contributes to these goals.
Example: During discussions with senior leadership, a change manager along with the rest of the project team can present data showing how the CRM system has improved customer retention rates and increased sales. By positioning this information in an easily understandable and rigorous manner, the change manager demonstrates the value of the initiative and its alignment with broader organizational objectives.
Effective communication ensures that leaders remain engaged and supportive throughout the change process, increasing the likelihood of success. By continuously linking the change initiative to organizational goals, change managers can build trust and credibility with stakeholders at all levels.
Leveraging Analytical Frameworks
Throughout the project lifecycle, incorporating structured analytical frameworks can enhance the decision-making process. Here are two key frameworks that change managers can leverage:
MECE Framework
MECE (Mutually Exclusive, Collectively Exhaustive) helps in breaking down complex information into manageable parts without overlap. By ensuring that all categories are covered without redundancy, change managers can identify all relevant factors affecting the change initiative.
TOSCA Framework
TOSCA (Target, Objectives, Strategy, Constraints, Actions) provides a comprehensive roadmap for change initiatives. By clearly defining each component, change managers can develop coherent strategies that align with organizational goals. This framework not only clarifies the change strategy but also ensures that all team members understand their roles in achieving the objectives.
Continuous Learning and Adaptation
Change management is not a static process; it requires continuous learning and adaptation. As organizations evolve, change managers must stay attuned to emerging trends and best practices in the field. This involves seeking feedback, conducting post-project evaluations, and staying updated on analytical tools and methodologies.
Change managers can attend workshops, participate in industry conferences, and engage with professional networks to enhance their analytical skills and learn from peers. By sharing experiences and insights, change managers can refine their approaches and incorporate new strategies that drive successful change.
The Transformative Power of Analytical Skills
The role of a change manager is multifaceted and requires a broad range of skills. However, one skill that stands out as particularly critical is the ability to think analytically. By adopting a strategic consultant’s mindset and applying analytical skills at each phase of the project lifecycle, change managers can significantly enhance their effectiveness.
From project commencement to closure, employing frameworks like MECE and TOSCA allows change managers to approach challenges in a structured way, making informed decisions that drive successful change. Continuous data collection, stakeholder engagement, and effective communication with senior leaders are essential components of this analytical approach.
In an era where organizations must adapt quickly to change, the ability to analyse complex data sets and derive actionable insights will distinguish successful change managers from the rest. Emphasizing this critical skill not only positions change managers as strategic partners within their organizations but also ensures that change initiatives lead to lasting, positive transformations.
As change practitioners, let us elevate our analytical capabilities and drive impactful change with confidence and clarity. By embracing this essential skill, we can navigate the complexities of organizational change and lead our teams toward a successful future.
In the rapidly evolving landscape of financial services, organisations face significant challenges due to regulatory and technological changes. A large financial services corporation has recognised the need for an integrated approach to change management reporting, embedding it within general business reporting to enhance organisational agility and effectiveness. This case study outlines the firm’s journey, challenges faced, solutions implemented, and the resulting value derived from this strategic initiative.
Background
The corporation operates under a defederated model of change management, where change practitioners are distributed across various business units. This structure has led to inconsistent change management practices and reporting, complicating the ability to provide comprehensive insights into organisational change efforts. As regulatory demands and technological advancements have intensified, the need for cohesive change management reporting became paramount.
Challenges
The primary challenges encountered by the centralized change management team included:
Diverse Reporting Preferences: Different stakeholders and divisions within the organization exhibited varying preferences for reporting formats and metrics. This lack of consensus hindered the development of a standardized reporting framework.
Maturity Disparities: Business units displayed varying levels of maturity in their change management practices, with some units showing strong interest while others remained indifferent.
Feedback Variability: Initial attempts to socialize various reporting types received mixed feedback, complicating efforts to establish a unified approach.
Solution Implementation
To address these challenges, the change management team adopted a multi-faceted strategy:
Executive Engagement: The team actively engaged with senior executives to align on the direction for change management reporting. A senior executive cohort was formed to define essential reporting needs and establish a common vision.
Collaboration with Business Intelligence (BI) Team: The change management team partnered with the BI team to integrate change management metrics into existing general business reports. This collaboration ensured that change management insights were included in routine business tracking.
Data Integration: Utilising data from Change Compass facilitated the ongoing production of comprehensive reports that combined operational metrics with change management insights.
Value Realized
The integration of change management reporting into general business reporting yielded several significant benefits:
Increased Leadership Focus: By embedding change metrics within standard business reports, leaders began to prioritize change management as part of their strategic oversight. This shift is expected to enhance readiness and adoption of future changes across the organization.
Proactive Change Support: Business leaders increasingly requested support for change initiatives, indicating a transition from a push model (where support is offered) to a pull model (where support is actively sought).
Enhanced Reporting Consistency: The establishment of a standardized set of reports improved clarity and consistency in how change initiatives were tracked and communicated across business units.
Change management Maturity: Enhancing change management maturity within the business is general done through capability development and coaching. However, this case showcases that embedding change management within general business management is a strategic way to raise awareness, visibility, and through this enhance the business’ efforts to improve the management of change.
This case study illustrates how a large financial services corporation successfully embedded change management reporting into its general business reporting framework. By engaging senior leadership, collaborating with data teams, and standardising metrics, the organisation not only improved its reporting capabilities but also fostered a culture that values proactive engagement with change initiatives. As a result, the firm is better positioned to navigate future changes while ensuring that it meets regulatory demands and capitalizes on technological advancements.
In the realm of organizational change management, the concept of a Single View of Change (SVOC) has become a focal point for experienced change practitioners. This approach aims to provide a comprehensive perspective on the myriad changes occurring within an organization, thereby facilitating informed decision-making among stakeholders. However, while the SVOC is often lauded for its potential to deliver a holistic picture of change impacts, its practical implementation raises several critical questions.
The Allure of a Single View of Change
The SVOC is designed to offer change practitioners a unified lens through which to view all organizational changes—be they strategic, operational, or cultural. By consolidating information about various changes, practitioners hope to present stakeholders with a clear and coherent narrative that captures the overall impact on the organization. This is particularly valuable in environments characterized by rapid change, where stakeholders may struggle to keep track of multiple initiatives.
Concept Illustration: The Change Landscape
Imagine an organization as a bustling city. Each building represents a different initiative or project, while the streets symbolize the pathways through which information flows. In this analogy, the SVOC acts as an aerial view of the city—providing insights into how each building interacts with others and how traffic (information) moves between them. This perspective allows stakeholders to see not just individual projects but also their collective impact on the organization.
The Realities of Implementation
Despite its theoretical appeal, achieving a Single View of All Changes may be unrealistic for many organizations. In practice, organizations often grapple with hundreds of concurrent changes, some of which may be deemed too minor or insignificant to warrant inclusion in a comprehensive overview. The administrative burden associated with capturing and maintaining this data can be substantial, leading some practitioners to question whether the effort is justified. One of the few ways to achieve this is through digital means.
Example: Too Many Changes
Consider a technology firm undergoing multiple changes simultaneously: launching a new product line, implementing an agile methodology, and restructuring its sales team. Each initiative generates its own set of data points—feedback from customers, team performance metrics, and employee satisfaction surveys. If the firm attempts to capture every detail from each initiative for its SVOC, it may end up drowning in data without gaining actionable insights.
So, what information to capture, and the methodology of capturing the information is critical. Again, digital solutions can help to automate the process, which means it can be faster and easier to capture and utilise the information.
The Cost-Benefit Analysis
Organizations must weigh the benefits of creating an SVOC against the costs involved. Practitioners should ask themselves:
What is the purpose of the SVOC?
Who are the primary stakeholders?
What decisions will be informed by this view?
If the answers indicate minimal value for certain changes or stakeholders, it may be more pragmatic to focus on high-impact initiatives rather than attempting to capture every nuance. However, if the organisation’s changes are mainly business-as-usual changes, then leaving this out will mean that the picture is no longer accurate.
To read more about calculating the financial benefits of managing a change portfolio check out this article.
Diverse Stakeholder Needs
Different stakeholders have varying requirements when it comes to understanding change:
Senior Executives: Typically prefer high-level summaries that align with strategic objectives. They seek key insights into risks and mitigations without being bogged down by granular details.
Operational Leaders: Often desire a more detailed view that includes specific impacts on daily operations and resource allocation. They may require insights down to the minute level to effectively manage their teams.
Example: Tailored Reporting
A financial services company might have different reporting needs based on stakeholder roles:
Department Heads receive weekly reports detailing project timelines, resource allocations, and immediate operational impacts.
By tailoring reports in this manner, organizations can ensure that each stakeholder receives relevant information without overwhelming them with unnecessary details.
Visual Communication Strategies
The selection of visuals plays a crucial role in conveying the right message to stakeholders. Effective visual communication should:
Allow for Flexible Drill-Downs
Stakeholders should be able to explore data at varying levels of granularity—aggregating macro-level views or drilling down into specifics as required. For example:
A senior executive might want an overview of change impacts across departments.
An operations manager may wish to drill down into specific team metrics related to a new process implementation.
Facilitate Easy Switching
Different stakeholders may prefer different types of visuals. Providing options for visual switching can enhance engagement and ensure that each stakeholder receives information in their preferred format.
Example: Interactive Dashboards
Using interactive dashboards can allow stakeholders to switch between different visual representations effortlessly. They enable stakeholders to engage with data meaningfully while catering to their individual preferences:
Heat Maps can show areas of high change impact at a glance.
Gantt Charts can provide timelines for specific initiatives.
Pie Charts can illustrate resource allocation across departments (if there are significant quantitative differences across each piece of the pie, or else the pie chart can be incredibly difficult to read for the audience. Check out this article to read more about this).
The Role of Technology
In today’s complex change environments, leveraging technology becomes increasingly critical. The sheer volume of data generated by ongoing changes can overwhelm traditional analysis methods. Here, artificial intelligence (AI) and live forecasting can serve as invaluable tools:
Automation
Utilizing AI can streamline data collection and analysis processes, reducing the need for extensive manual oversight. For instance:
Natural Language Processing (NLP) algorithms can analyze employee feedback from surveys or social media platforms to gauge sentiment regarding ongoing changes.
Automated reporting tools can generate real-time updates on project statuses without requiring manual input from team members.
Forecasting Capabilities
Live forecasting tools can provide real-time insights into potential impacts and outcomes, enabling practitioners to make proactive adjustments. For example:
A manufacturing company might use predictive analytics to forecast how changes in supply chain management will affect production schedules.
A healthcare organization could employ simulation models to assess how new policies will impact patient care delivery.
Example: AI Implementation in Change Management
Consider a global retail chain implementing AI-driven analytics during its digital transformation efforts:
Data Collection: AI tools generates various change data including change impacts, communication plan, stakeholder assessment, etc.
Analysis: Machine learning analyses the data and calls out key data observations, trends, outliers, and patterns.
Reporting: Stakeholders receive tailored reports and dashboards showing an integrated view of what upcoming changes there are, and highlighting key risks and actions required.
This approach not only saves time but also enhances decision-making by providing actionable insights based on real-time data. However, note that currently AI will not be able to do everything. The change practitioner still needs to be able to analyse generated data and amend as needed, prioritise and select key data observations for reporting, and provider editorial oversight on what key messages should go out to the various types of stakeholders.
Understanding Stakeholder Challenges
Change practitioners must develop an acute ability to read their stakeholders’ business challenges and tailor their communications accordingly. This involves:
Tailoring Data Presentations
Adjusting the types of data shared based on stakeholder roles and responsibilities is crucial. For example:
A project manager might need detailed timelines and resource allocations for specific initiatives.
A finance officer may require cost-benefit analyses and benefit realisation forecast linked to adoption rates related to ongoing changes.
Customising Visuals
Selecting visuals that resonate with specific stakeholder concerns while remaining aligned with overarching organizational goals is essential for effective communication. Using storytelling techniques in presentations can help convey complex information more effectively:
Contextualize Data: Start with a narrative that outlines why changes are necessary.
Visualize Impact: Use graphs or infographics to illustrate projected outcomes.
Call-to-Action: Conclude with specific actions required from stakeholders based on insights presented.
By framing data within a narrative context, practitioners can foster greater engagement and understanding among stakeholders.
Trial and error
A lot of your stakeholder may not know what they want. They are not change management experts so they may not be able to tell you exactly what the outputs look like. Often they may tell you at a high level the type of data they are after, but not the specifics.
You need to be able to carefully balance giving them something that will hit the mark, as a ‘test’ (since you may not hit the mark the first time). A bit of trial and error is required in this process as you continually test with your stakeholders what resonates and what gets their attention and drives action.
This can cause a lot of frustration and anxiety for change practitioners. After all, you are doing your very best to deliver something that is requested. But again, your audience does not know exactly what they want. There is an element of you guiding them, but also the other element of directly giving them what they are looking for.
Do note that if you don’t hit the mark too many times you may lose their interest, and therefore the opportunity to present change management data. This means that you may only have a small window of opportunity. Digital tools can help you with selecting the right visuals for the right stakeholders.
Facilitating Governance Forums
Creating spaces where stakeholders can discuss insights derived from change data allows for collaborative decision-making:
Regular Business Meetings: Schedule governance forums where stakeholders review progress on key initiatives.
Interactive Discussions: Encourage open dialogue about challenges faced during implementation.
Action-Oriented Outcomes: Ensure meetings conclude with clear action items based on insights shared.
Addressing Change Fatigue
One significant challenge in managing change is addressing change fatigue, which occurs when employees feel overwhelmed by constant organizational shifts. Symptoms include:
Apathy
Burnout
Increased resistance
To combat this phenomenon, organizations must implement strategies that foster resilience among employees:
Engagement Initiatives
Actively involving employees in the change process allows them to voice concerns and contribute solutions:
Feedback Mechanisms: Implement regular surveys or focus groups where employees can share their thoughts on ongoing changes.
Recognition Programs: Celebrate small wins related to change initiatives to maintain morale.
Transparent Communication
Maintaining open lines of communication regarding what changes are occurring and why they matter helps mitigate feelings of uncertainty among employees:
Regular Updates: Provide frequent updates through newsletters or town hall meetings.
Clear Messaging: Ensure messaging is consistent across all channels to avoid confusion.
Learning and Support
Providing resources that equip employees with the skills needed to navigate changes effectively is vital for reducing resistance:
Skill Development Workshops: Offer training sessions focused on new processes or technologies being implemented.
Mentorship Programs: Pair employees with mentors who have successfully navigated similar changes in the past.
The concept of a Single View of Change holds considerable promise for enhancing stakeholder understanding in dynamic organizational environments. However, its successful implementation hinges on recognizing the diverse needs of stakeholders and tailoring communications accordingly. By leveraging technology and fostering an environment conducive to engagement and support, change practitioners can create a more effective framework for managing organizational change. In summary, while striving for an SVOC may seem aspirational, it is essential for change practitioners to remain pragmatic about its execution—balancing ambition with realism to meet stakeholder needs effectively.
As organizations continue evolving in response to market demands and internal dynamics, understanding how best to communicate change becomes paramount. The Single View of Change offers a powerful toolset; however, it requires thoughtful consideration regarding stakeholder needs, technological integration, and ongoing adaptability in communication strategies. By embracing these principles, organizations not only enhance their capacity for effective change management but also cultivate resilience among their workforce—ultimately positioning themselves for sustained success in an ever-changing landscape.
