Successful change management in financial services: Drive transformation with agility

Successful change management in financial services: Drive transformation with agility

The pressure is relentless. Regulators demand compliance with new directives. Customers expect digital experiences rivalling fintech disruptors. Shareholders want innovation without compromising stability. Meanwhile, legacy infrastructure groans under the weight of systems built for control, not change. Welcome to transformation in financial services, an industry unlike any other.

The financial services sector operates in a category of its own. Unlike retail, manufacturing, or technology, where change initiatives carry significant stakes but primarily affect business performance, transformation in banking, insurance, and wealth management carries existential weight. A failed digital transformation in a retailer costs money. A failed compliance transformation in a bank costs money, reputation, regulatory penalties, customer trust, and potentially shareholder value. This distinction fundamentally reshapes everything about how transformation should be approached, measured, and defended to boards and regulators.

Change Maturity Challenges within The Financial Services Sector

What makes financial services transformation uniquely challenging is not just the volume of regulatory requirements, though that’s substantial. The real complexity lies in the paradox that defines the sector: institutions must simultaneously be risk-averse and innovative, compliant and agile, stable and transformative. This isn’t a contradiction to resolve; it’s a tension to master. And mastering it requires something most change management frameworks don’t adequately address: operational visibility, adoption tracking, and risk-aware decision-making that speaks the language senior leaders actually understand.

Yet here’s what often remains unexamined: financial services organisations exist across a spectrum of change maturity, and that maturity level is a more powerful predictor of transformation success than transformation budget, executive sponsorship, or project management rigour.

At the lower end of the spectrum, organisations treat change management as a project activity. A transformation initiative launches, a change team is assembled, stakeholder engagement campaigns are executed, and when the project concludes, the change team disperses. There’s little infrastructure for tracking whether changes actually stick, adoption curves plateau, or business benefits are realised. Change management is something you do during transformation, not something you measure and manage continuously.

At the mid-range of maturity, organisations begin to recognise that change management affects transformation outcomes. They invest in change management methodologies, train practitioners, and integrate change into project governance. However, change remains primarily qualitative. Adoption is measured through surveys. Stakeholder engagement is tracked through workshop attendance. Compliance is verified through spot-checks. There’s limited integration between change tracking and operational performance monitoring, so leaders often can’t distinguish between transformations that appear to be progressing but are silently failing from those that are genuinely succeeding.

At the highest levels of maturity – where a select group of leading financial services organisations have evolved: Change management becomes an operational discipline powered by integrated data infrastructure. These organisations instrument their transformations to capture real-time adoption metrics that correlate to behavioural change, not just system usage. They track operational performance against baseline as transformations roll out, distinguishing between temporary productivity dips (expected) and structural performance degradation (concerning). They maintain forward-looking compliance risk visibility rather than historical compliance status checks. They track financial impact in real time against business case assumptions. Most critically, they integrate these multiple streams of data into unified dashboards that enable senior leaders to make diagnostic decisions: “Adoption is tracking at 65% in this division. Why? Is it a training gap? A process design issue? Insufficient incentive alignment? Cultural resistance? Poor leadership communication?” Armed with diagnostic data rather than just descriptive metrics, leaders can intervene with precision.

This isn’t theoretical. Leading financial services institutions working with platforms like The Change Compass have achieved remarkable results by institutionalising this data-driven approach to change maturity. These organisations have moved beyond asking “Is our transformation on track?” to asking “What’s driving adoption patterns? Where are the operational risks emerging? How do we know we’re actually achieving the financial returns we projected?” By treating change as a measured, managed discipline with the same rigour applied to financial or operational metrics, they’ve fundamentally improved transformation success rates.

What’s particularly striking about these highly mature organisations is that their leadership in change management often goes unrecognised externally. They don’t shout about their change management capabilities – they’re simply unusually effective at executing large-scale transformations, navigating regulatory complexity with agility, and maintaining stakeholder alignment through extended change journeys. Other sector players notice their results but often attribute success to better technology, better project management, or better luck, rather than recognising it as the product of intentional, systematic investment in change maturity powered by data and business understanding.

The Regulatory Pressure Cooker

Financial services leaders face a compliance landscape that has fundamentally shifted. The cost of compliance for retail and corporate banks has increased by more than 60% compared to pre-financial crisis levels.[1] This isn’t simply a cost line item, it represents a structural constraint on innovation, a drain on resources, and a constant competitive pressure. The EU’s Digital Operational Resilience Act (DORA), evolving consumer protection regulations, anti-money laundering (AML) frameworks, and cybersecurity mandates create an overlapping web of requirements that demand both precision and speed.

What distinguishes financial services from other highly regulated sectors is the pace of regulatory change itself. New rules don’t arrive once every few years; they arrive continuously. Amendments cascade. Interpretations shift. Technology evolves faster than regulatory guidance can address it. The average bank currently spends 40% to 60% of its change budget on regulatory compliance initiatives alone, yet despite this substantial investment, a significant portion remains inefficient due to outdated approaches to implementation (Boston Consulting Group publication titled “When Agile Meets Regulatory Compliance” 2021).

This regulatory pressure creates the first major tension for transformation leaders: how do you drive innovation and modernisation when the majority of resources are consumed by compliance? How do you maintain stakeholder momentum for digital transformation when compliance demands keep arriving? And critically, how do you measure success when regulatory requirements were met but the transformation initiative itself faltered?

Institutions at lower maturity levels often stumble here because they lack integrated visibility into how regulatory changes cascade through their transformation portfolio. They may complete a compliance transformation on schedule, but without visibility into downstream operational impacts, adoption rates, or actual risk remediation, they’re flying blind. More mature organisations build change tracking into their compliance management processes, creating feedback loops that distinguish between compliance completion and genuine compliance behaviour change across the enterprise.

The Agility Paradox

Paradoxically, the same regulatory environment that demands risk-aversion increasingly requires agility. Regulations themselves are becoming more complex and iterative. The European Union’s Markets in Financial Instruments Directive II (MiFID II) began as an 80-page level 1 document. It expanded to more than 5,000 pages at implementation level. Traditional, sequential approaches to regulatory projects fail in this environment because they assume complete requirement certainty, an assumption that’s now unrealistic.

Leading institutions are discovering that agile change management approaches, when properly governed, can reduce IT spending on compliance projects by 20-30% whilst improving on-time delivery (Boston Consulting Group, “When Agile Meets Regulatory Compliance”). Yet many boards and senior leaders remain sceptical. The perception persists that agile methods are incompatible with the stringent governance and control frameworks financial institutions require. That perception is outdated, but it reflects a genuine leadership challenge: how do you embed agility into an institution whose cultural DNA and governance structures were designed for control?

This is where financial services diverges sharply from other sectors. A technology company can run experiments at speed, learning from failures as they occur. A fintech can pivot when market conditions change. A bank cannot. At least, it cannot without regulatory approval, compliance sign-off, and governance board endorsement. Yet this very rigidity – ironically designed to protect stability, often results in slower time-to-market, higher costs, and strategic misalignment when external conditions shift.

The solution lies not in abandoning risk management but in reimagining it. Agile risk management involves developing agile-specific risk assessments and continuous-monitoring programmes that embed compliance checks at every step of delivery, rather than at the end. This transforms risk management from a gate to a guardrail. When properly implemented, cross-functional teams including risk, compliance, and business units can move at pace whilst maintaining the governance rigour the sector demands.

However, this requires a fundamental shift in how financial services leaders think about transformation. Risk and compliance functions must transition from a “second line of defence” mindset, where they audit and approve – to a “design partner” mindset, where they collaborate from day one. Institutions with higher change maturity consistently outperform on this dimension because they’ve embedded risk and compliance perspectives into their change governance from the start, rather than treating these as separate approval gates.

The Cultural Challenge: Risk-Aversion Meets Innovation

Beyond the structural tensions lies a deeper cultural challenge. Financial services institutions have been shaped by risk-aversion. Conservative decision-making. Extensive approval chains. Multiple levels of governance. These practices evolved for good reasons, protecting customer deposits, maintaining market confidence, ensuring regulatory compliance. But they’ve also created institutional muscles that make experimentation difficult.

Yet innovation increasingly demands experimentation. How do you test a new customer journey without rolling it out at some level? How do you validate a new digital channel without risk? How do you innovate in payments, lending, or wealth management without trying approaches that haven’t been tested at scale before?

This isn’t a problem unique to financial services, but it’s more acute here because the cost of failure is higher. When an experiment fails in fintech, you iterate or pivot. When an experiment fails in a bank and affects customer accounts, regulatory reporting, or data security, the consequences cascade across multiple dimensions: customer trust, regulatory relationships, brand reputation, and potentially shareholder value.

Leading institutions are learning to create controlled experimentation frameworks – what might be called “risk-aware innovation.” This involves establishing sandbox environments where new approaches can be tested with limited exposure, clear guardrails, and robust monitoring. It requires explicit governance decisions about what degree of failure is acceptable in pursuit of learning and innovation. Most importantly, it demands transparency about the trade-offs: we’re accepting a marginal increase in risk here to capture an opportunity there, and here’s how we’re mitigating that risk and monitoring it.

For senior transformation leaders, this cultural challenge is often the hidden barrier to success. A technically excellent transformation can stall because the institution’s cultural immune system rejects change it perceives as risky. Conversely, a transformation that gets cultural buy-in by positioning itself as “low risk” may lack the ambition required to genuinely transform the organisation.

Notably, this is also where change maturity divergences become most visible. Lower-maturity organisations often treat cultural resistance as an engagement problem to be communicated away. More mature organisations recognise that cultural misalignment signals fundamental tensions between stated strategy and actual incentives, governance structures, and decision rights. The most mature organisations use change data – adoption patterns, stakeholder sentiment, engagement participation, as diagnostic tools to surface these tensions and address them systematically rather than through surface-level communication campaigns.

What Senior Leaders Really Need: Data Insights, Not Narratives

Here’s what often goes unstated in transformation discussions: senior leaders and boards don’t actually care about change management frameworks, adoption curves, or stakeholder engagement scores. What they care about is operational risk and business impact. They need to know: Is this transformation tracking on schedule? Where are the adoption barriers? What’s the actual impact on operational performance? Are we at risk of compliance failures? What’s the return on the investment we’ve made?

This is where many transformation programmes stumble. They’re often sold on change management narratives – compelling stories about the future state, cultural transformation, and employee empowerment. But when senior leadership asks, “What’s our operational status?” or “How do we know adoption is actually happening?” the answers are often too qualitative, too delayed, or too fragmented across systems to be actionable.

In financial services specifically, operational leaders think in terms that are measurably different from other sectors. They think about:

Regulatory Risk: Are we exposed to compliance gaps? Which processes remain unaligned with regulatory requirements? What’s our remediation timeline? What’s the forward-looking compliance risk as systems migrate and processes change?

Operational Performance Degradation: Digital transformations often produce a J-curve impact – performance gets worse before it gets better as teams adopt new processes. How steep is that curve? How long will degradation persist? What’s acceptable and what signals we need to intervene?

Adoption Velocity: Not just whether people are using new systems, but at what pace and with what proficiency. Which user groups are adopting fastest? Where are the holdouts? Which processes are being bypassed or manual-workarounded? Which features are underutilised?

Financial Impact: Cost savings from process efficiency. Revenue impact from faster time-to-market on new products. Reduction in remediation and rework costs. These need to be tracked not prospectively but in real time, so boards can assess actual ROI against business case projections.

Risk Incident Frequency: Are transformation activities introducing new operational risks? Is error rates increasing? Are compliance incidents rising? Are there early warning signals suggesting system instability or process breakdowns?

This is the data infrastructure many transformation programmes lack. They track adoption at a process level, but not operational performance at the transaction or customer level. They monitor compliance status historically, but not forward-looking compliance risk as changes roll out. They measure project milestones, but not business impact metrics that correlate to shareholder value.

Without this data, senior leaders operate from narrative and intuition rather than evidence. They can’t distinguish between a transformation that’s genuinely tracking well but communicated poorly from a transformation that appears to be on track but is actually masking emerging operational risks. This distinction is critical in financial services, where the cost of discovering operational problems at go-live rather than during implementation is exponentially higher.

How Change Management Software Supports Transformation

The shift toward data-driven change maturity requires fundamental reimagining of how change management is orchestrated. Leading financial services institutions are moving toward integrated platforms that provide real-time visibility into transformation performance across multiple dimensions simultaneously. Unlike traditional change management approaches that rely on periodic surveys, workshops, and engagement tracking, modern change management software instruments transformations to capture continuous, actionable data.

Effective change management software provides the infrastructure to capture and analyse:

Change management metrics and success measurement: Real-time dashboards tracking whether transformations are delivering on their intended outcomes. This goes beyond change management KPIs focused on activity metrics (how many people trained, how many workshops completed) to outcome metrics that correlate to actual business impact and adoption velocity.

Change monitoring and readiness assessment: Continuous monitoring of the organisational readiness for change, identifying which departments, teams, and individuals are ready to adopt new ways of working versus those requiring targeted support. Readiness for change models built into software platforms enable proactive intervention rather than reactive problem-solving after go-live.

Change management tracking and change analysis: Real-time visibility into where transformations stand operationally, financially, and from a compliance and risk perspective. Change management tracking systems that integrate with operational data provide diagnostic signals about what’s driving adoption patterns, where process gaps exist, and which interventions will be most effective.

Change management performance metrics and analytics: Integrated change management analytics that correlate adoption patterns with operational performance, compliance risk, and financial outcomes. These analytics answer critical questions: “We achieved 75% adoption in this division. Is that sufficient? How is operational performance tracking relative to baseline? Are compliance risks elevated as adoption occurs?”

Change management strategy alignment and change initiative orchestration: Platforms that connect individual change initiatives to broader transformation strategies, enabling leaders to understand how multiple concurrent changes interact, compound, or conflict. This is critical in financial services where organisations often juggle dozens of regulatory compliance changes, technology transformations, and process improvements simultaneously.

Change assessment and change management challenges identification: Sophisticated change assessment capabilities that surface emerging barriers early: Skills gaps, process misalignments, governance mismatches, stakeholder resistance, so leaders can intervene before they become critical blockers.

When integrated, this creates what might be called a transformation control tower – a unified view of where the transformation stands operationally, financially, and from a compliance and risk perspective. More importantly, it enables diagnostic analysis: “Adoption is tracking at 65% in this division. Why? Is it a training gap? A process design issue? Insufficient incentive alignment? Cultural resistance to change? Poor leadership communication?” Armed with diagnostic data rather than just descriptive metrics, transformation leaders can intervene with precision rather than generalised solutions.

The critical distinction in highly mature organisations is that they don’t treat change management software as a “nice to have” project reporting capability. Rather, they embed change data into the operating rhythm of the business. Change management success metrics feed into monthly leadership reviews. Change monitoring alerts surface automatically when adoption thresholds are breached. Compliance risk is assessed continuously rather than episodically. Financial impact tracking happens in real time, allowing course correction when actual performance diverges from projections. This represents a fundamental shift: change management tools and techniques are no longer about communicating and engaging during transformation; they’re about managing transformation as a continuous operational discipline.

In financial services specifically, this transforms how organisations approach the core tensions around regulatory compliance, agile delivery, and innovation. Change management software that provides integrated visibility into adoption patterns, operational performance, and compliance risk allows institutions to make evidence-based decisions about resource allocation, risk tolerance, and intervention timing. When a regulatory compliance change is rolling out, leaders can see in real time whether actual behaviour is changing or whether people are performing workarounds. When agile teams are experimenting with new delivery approaches, leaders have visibility into whether the controlled experimentation is introducing unacceptable risk or whether the risk envelope is being properly managed. When cultural transformation is underway, leaders can track sentiment changes, engagement patterns, and behavioural adoption rather than relying on post-implementation surveys that arrive months after critical decisions were made.

The most important insight from leading financial services institutions implementing advanced change management software is this: the software isn’t valuable because it’s smart. It’s valuable because it makes visible what’s traditionally been invisible and enables decision-making based on evidence rather than intuition or outdated frameworks.

Building Change Maturity Through Systems Thinking

Leading financial services institutions are moving toward platforms that provide real-time visibility into transformation performance across multiple dimensions simultaneously. They’re instrumenting their transformations to capture:

Adoption metrics that go beyond system login frequency to measure whether people are actually using processes correctly and achieving intended outcomes.

Operational metrics that track performance against baseline—speed, accuracy, error rates, compliance violations—as transformation rolls out and adoption occurs.

Risk metrics that provide forward-looking signals about compliance exposure, process gaps, and operational vulnerabilities introduced by transformation activities.

Financial metrics that track actual cost and revenue impact compared to transformation business case assumptions.

Sentiment and engagement data that provides early warning signals about adoption barriers, cultural resistance, or leadership alignment challenges.

The systems-based approach to change maturity, where change management data, decision-making infrastructure, and engagement strategies are integrated into the business operating model rather than existing as parallel activities, is what distinguishes the highest-performing organisations from the rest. It’s not just about having better data; it’s about embedding that data into how decisions actually get made.

In financial services, this data infrastructure serves an additional critical function: it builds credibility with regulators. When regulators ask about a major transformation, they want to know not just that it’s progressing, but that the institution has genuine visibility into operational risk and compliance impact. Real-time transformation metrics demonstrate that senior leadership isn’t simply hoping a transformation succeeds; it’s actively monitoring and managing it.

Financial Services: Setting Industry Standards

The institutions at the highest end of change maturity, particularly several leading financial services organisations working with The Change Compass, have become examples not just within their own sector but across industries. Their ability to embed change management data into business decision-making, coupled with their systematic development of change maturity through integrated platforms and systems thinking, sets a benchmark that other sectors increasingly aspire to.

These organisations have stopped trying to choose between risk-aversion and innovation. Instead, they’ve designed transformation approaches that embed risk management, compliance oversight, and governance into the rhythm of change rather than treating these as separate, sequential activities. They’ve instrumentalised their transformations to provide the operational visibility that financial services leaders demand and regulators expect. They’ve created cultural frameworks that position controlled experimentation and measured risk-taking as core capabilities rather than exceptions to risk-management doctrine.

What distinguishes these highly mature organisations is their recognition that change maturity isn’t an outcome of better training or more comprehensive change methodologies. Rather, it’s a product of intentional investment in systems that make change visible, measurable, and manageable as an operational discipline. These systems, platforms that integrate change management frameworks, adoption tracking, operational performance monitoring, compliance risk assessment, and financial impact analysis into a unified data infrastructure – become the foundation upon which genuine change maturity is built.

The organisations leading this charge have recognised that every transformation is also a data problem. The challenge isn’t just managing change; it’s creating the infrastructure to understand change in real time, with the granularity and speed that senior financial services leaders require. When adoption tracking integrates with operational performance data, when compliance risk monitoring links to adoption patterns, when financial impact analysis is informed by real-time adoption and performance metrics, the result is a fundamentally different quality of transformation management than traditional change management approaches can deliver.

Building the Transformation Your Industry Deserves

The transformation landscape in financial services has fundamentally shifted. It’s no longer sufficient to deliver a project on time and on budget. Success now requires delivering a project that moves adoption curves at pace, maintains operational performance through transition, manages regulatory compliance proactively, demonstrates clear financial returns, and positions the organisation for the next round of transformation. The institutions that will thrive are those that treat transformation not as a project delivery challenge but as an operational management challenge – one that demands real-time visibility, diagnostic capability, and decision-making infrastructure that translates transformation data into actionable insights.

Critically, this shift requires recognition that change maturity levels vary dramatically across the financial services sector. Some organisations remain in the lower maturity zones, treating change management as a project overlay. Others have built mid-level maturity, integrating change into project governance but lacking integrated data infrastructure. And a select group of leading institutions have recognised that genuine change maturity emerges from systematic investment in data platforms, business understanding, and decision-making infrastructure that embeds change into how the organisation actually operates.

The cost of getting this wrong is substantial. Major transformation failures in financial services cost tens and sometimes hundreds of millions in direct costs, opportunity costs, regulatory remediation, and customer attrition. The cost of getting it right, where transformations move at pace, adoption accelerates, compliance is maintained, and financial returns are delivered – is equally substantial in the other direction: cost savings from process efficiency, revenue acceleration from time-to-market advantage, risk mitigation that protects brand and regulatory relationships, and organisational capability that enables the next wave of transformation.

Digital transformation platforms purpose-built for financial services change management, platforms like The Change Compass – are increasingly central to this approach. These platforms provide the integrated data infrastructure that transforms senior leaders’ understanding of transformation progress from narrative and intuition to evidence and diagnostic insight. They make visible what’s traditionally been invisible: the real adoption curves, the operational performance impact, the compliance risk in real time, and the financial returns actually being achieved.

What’s particularly noteworthy is how some leading financial services clients have leveraged these platforms to build systemic change maturity, embedding change data into business decision-making, developing change capabilities through data-driven feedback loops, and creating the operational disciplines that enable consistent transformation success. These organisations have moved beyond simply tracking transformation progress to building genuine change maturity as an operational competency powered by continuous data collection, analysis, and decision-making integration.

By providing this visibility and infrastructure, these platforms enable the kind of proactive management that allows financial services institutions to navigate the paradox of being simultaneously risk-averse and innovative, compliant and agile, stable and transformative. The institutions that master transformation in financial services will be those that recognise change maturity as a strategic capability requiring systematic investment in data infrastructure and business understanding. Those that use that infrastructure to make decisions, intervene with precision, and continuously optimise as circumstances evolve. That’s the transformation approach financial services deserves—and the one that will define competitive advantage for the decade ahead.


Frequently Asked Questions: Financial Services Transformation and Change Management

What is the biggest barrier to transformation success in financial services?

Most financial services transformations fail not because of strategy or technology, but because change management is treated as a project activity rather than an operational discipline. Without real-time visibility into adoption, compliance risk, operational performance, and financial impact, senior leaders rely on narratives instead of evidence. This creates blind spots that hide adoption barriers and compliance gaps until after go-live, when correcting problems becomes exponentially more expensive.

What are the three levels of change maturity?

Level 1 (Project-Centric): Change treated as project overlay. Limited tracking of adoption or business impact. Problems surface at go-live.

Level 2 (Governance-Integrated): Change embedded in project governance. Adoption tracked qualitatively through surveys. Limited connection to operational performance metrics.

Level 3 (Data-Driven Operations): Change as continuous operational discipline. Real-time visibility into adoption velocity, compliance risk, operational performance, and financial ROI enables precision interventions and documented ROI.

Why does regulatory compliance dominate financial services change budgets?

Financial services institutions spend 40-60% of their total change budget on regulatory compliance initiatives. However, much of this investment is wasted due to outdated, sequential implementation approaches. When properly governed, agile change management approaches can reduce IT spending on compliance projects by 20-30% whilst improving on-time delivery is the key is embedding compliance into iterative delivery rather than treating it as a final gate.

What metrics should financial services leaders track for transformation success?

Stop tracking activity metrics (workshop attendance, email opens). Instead, track:

  • Adoption Velocity: Pace and proficiency of actual process usage, not system logins
  • Regulatory Risk: Forward-looking compliance exposure as adoption occurs
  • Operational Performance: Real-time impact on efficiency, accuracy, error rates against baseline
  • Financial Impact: Actual cost savings and revenue versus business case projections
  • Risk Incidents: New operational risks introduced by transformation activities

Without integrated data linking these metrics, leadership decisions remain guesswork rather than evidence-based.

How do leading financial services institutions balance innovation with risk-aversion?

They’ve stopped trying to choose. Instead, leading institutions build controlled experimentation frameworks with embedded risk monitoring—sandbox environments where new approaches are tested with limited exposure, clear guardrails, and robust monitoring. This transforms risk management from a blocker into a guardrail, enabling measured risk-taking and innovation within defined parameters. This is how the most mature firms navigate regulatory intensity while accelerating innovation.

What is the cost of poor change management?

Major transformation failures in financial services cost tens to hundreds of millions in direct costs, opportunity costs, regulatory remediation, and customer attrition. The difference between a lower-maturity organisation (treating change as a checkbox) and a higher-maturity organisation (with data-driven change discipline) can represent tens of millions in wasted spend, regulatory exposure, or competitive advantage. Strong change maturity enables cost savings, revenue acceleration, risk mitigation, and organisational capability.

How does change management software solve transformation visibility gaps?

Purpose-built change management platforms create a transformation control tower with unified visibility into adoption, compliance, operational performance, and financial impact in real time. Rather than discovering problems weeks after they occur, leaders see adoption stalls immediately and can diagnose why (training gap? process design issue? incentive misalignment?). This enables precision interventions instead of generalised solutions, transforming change management from reactive firefighting to proactive, data-driven orchestration.

program implement planning

program implement planning

A Guide on Integrating Change Management with Scaled Agile for Seamless Product Delivery – Part 1

A Guide on Integrating Change Management with Scaled Agile for Seamless Product Delivery – Part 1

by | Agile, Guides, Uncategorized

The need for organizations to remain flexible and responsive to market demands has never been more critical, and scaled agile (SAFe) provide the framework to achieve this. Integrating change management work with SAFe is essential for seamless product delivery but yet is not clearly articulated in literature. However, for agile product delivery to be successful, it must be supported by robust change management work steps.  Those that not ensures that all stakeholders are aligned and engaged throughout the process and also that the consecutive changes delivered are adopted. Let’s explore how change managers can effectively integrate their approaches with scaled agile methodologies to enhance product delivery.

Understanding the Intersection of Change Management and Agile

Change management and agile methodologies both aim to facilitate successful project outcomes, but they approach this goal from different angles. Change management focuses on the people side of change, ensuring that stakeholders are prepared, equipped, and supported throughout the transition through to benefit realisation. Agile methodologies, on the other hand, emphasize iterative development, continuous feedback, and rapid adaptation to change.  

Whilst SAFe acknowledges the importance of managing the people side of change and leading the change, it does not spell out how exactly this work should be integrated with the methodology in a detailed manner. References to change tends to be at a high level and focuses on communication and readiness activities.

What are key call outs of the SAFe methodology:

1) Lean-Agile Principles: SAFe is grounded in Lean-Agile principles such as building incrementally with fast, integrated learning cycles, basing milestones on objective evaluation, and making value flow without interruptions. These principles help ensure continuous improvement and adaptability​

2) Organizational Agility: To remain competitive, enterprises must be agile. SAFe enhances organizational agility by fostering Lean-thinking people and Agile teams, promoting strategic agility, and implementing Lean business operations​

3)  Lean Portfolio Management: Aligns strategy and execution by applying Lean and systems thinking. It includes strategy and investment funding, Agile portfolio operations, and Lean governance to ensure that the portfolio is aligned and funded to meet business goals​

4)  Continuous Learning Culture: Encourages a set of values and practices that promote ongoing learning and improvement. This culture is crucial for adapting to changes and fostering innovation within the organization​ 

5) Agile Teams: Agile teams in SAFe operate using methods like SAFe Scrum or SAFe Team Kanban. These teams are responsible for understanding customer needs, planning their work, and delivering value continuously through iterative processes​ 

6)  Built-in Quality: Emphasizes the importance of quality at all stages of development. Practices include shift-left testing, peer reviews, and automation to ensure high standards and reduce defects early in the process​ 

7)  Value Stream Management (VSM): Focuses on optimizing the flow of value across the entire portfolio. VSM helps organizations improve their value delivery processes by managing and monitoring value streams effectively​ (Scaled Agile Framework)​.

8) Lean-Agile Leadership: Leaders play a critical role in fostering a Lean-Agile mindset. They must model the values and principles of SAFe, provide guidance, and create an environment that supports Agile teams and continuous improvement​

9)  Decentralized Decision-Making: Promotes faster value delivery by empowering teams to make decisions locally. This reduces delays, enhances product development flow, and fosters innovation​ 

10)  Customer-Centric Approach: Agile teams are encouraged to maintain close collaboration with customers to understand their needs better and ensure that solutions deliver real value. Techniques like direct customer interaction and feedback loops are essential​ 

Below is a diagram from Scaled Agile Frameworks on key elements of a scaled agile product delivery framework.

Agile-Style Deliverable Artefacts

To support agile product delivery, change managers need to create agile-style deliverable artefacts early in the product delivery cycle. These artefacts serve as essential tools for aligning the team, stakeholders, and the overall change initiative with agile principles.  They are significantly ‘lighter’ in volume and more succinct in focusing on key analysis points that determine approaches and actions required to plan and implement the change.

Change artefact 1: Change Canvas

An Agile Change Canvas is a strategic tool designed to plan, manage, and communicate change initiatives effectively within an organization. It begins with basic identification details such as the Project NameBusiness Owner, and Author. This section ensures clear accountability and ownership from the outset.

The Change Vision & Objectives outlines the overarching project objectives and intended outcomes of the project. This architecture vision acts as a guiding star, ensuring all actions align with the desired future state of the organization. Following this, Core Challenges are identified to highlight potential obstacles that could impede progress. Recognizing these challenges early allows for proactive mitigation strategies.

Stakeholder Impacts analyses how different stakeholders will be affected by the change. This includes assessing both the positive and negative impacts on employees, customers, and shareholders, ensuring that their concerns are addressed and their needs met. 

The Key Milestones section, presented in a table format, outlines significant checkpoints in the project timeline, often represented in Gantt charts. Each milestone is associated with a particular function, ensuring that progress is measurable and trackable. Similarly, the Resources section details the necessary financial, human, and technological resources required to implement the change, ensuring that the project scope statement is adequately supported.

Why Change section provides the rationale behind the need for change, which could include market demands, competitive pressures, or internal inefficiencies. This section justifies the project’s existence and urgency. Complementarily, What Will Change (WWC) describes the specific changes to be implemented, including processes, technologies, behaviours, and structures, offering a clear picture of the project’s scope.

Key Metrics are identified to measure the success of the change initiative. These metrics are both quantitative and qualitative, providing a comprehensive view of the project’s impact. Change Interventions listed in a table format, detail specific actions or initiatives designed to facilitate the change, ensuring a structured approach to implementation.

To foster a culture of innovation and adaptation, Change Experiments are proposed. These pilot programs test aspects of the change in a controlled environment before full-scale implementation. Finally, Change Risks identifies potential risks associated with the change and outlines strategies for mitigating these risks, ensuring that the project can navigate potential pitfalls effectively.

By incorporating these elements, the Agile Change Canvas provides a comprehensive framework for managing change initiatives, ensuring that all critical aspects are considered, planned for, and communicated effectively to stakeholders.

For a template of the Change Canvas check it out here.

Change artefact 2: Kanban boards of Changes

Using a Kanban board for change management activities provides a visual and dynamic method for tracking, prioritizing, and managing the flow of work while implementing changes. A Kanban board typically consists of columns that represent different stages of work, such as “To Do,” “In Progress,” and “Done.” For change management, additional columns might include “Proposed Changes,” “Under Review,” “Implementation Planning,” and “Monitoring.”

Whilst most change practitioners are used to kanban boards In working with various change management activities, there is opportunity to use kanban to plan and prioritise a series of agile-style changes and the associated change activities with each change.  These ‘change cards’ within the kanban board presents a clear way to visualise a series of changes across the ‘delivery train’ where the project team continuously delivers pieces of change.

Prioritizing Change Management Activities

  1. Visualizing Workflow:
  2. Proposed Changes: This column lists all suggested changes, each represented by a card detailing the change’s purpose, impacted areas, and expected benefits.
  3. Under Review: Changes move here once they are being evaluated for feasibility, risks, and alignment with project goals.
  4. Implementation Planning: Approved changes are further detailed, including resource allocation, timelines, and specific tasks needed for implementation.
  5. In Progress: Changes that are actively being worked on are tracked here, showing current status and any blockers encountered.
  6. Monitoring: Recently implemented changes are monitored to ensure they are delivering the expected outcomes and to identify any issues early.
  7. Done: Fully implemented and stabilized changes are moved here, marking their successful completion.
  8. Setting Priorities:
  9. Value and Impact: In conjunction with the project team prioritize changes based on their potential value and impact. High-value changes that significantly improve project outcomes or stakeholder satisfaction should be addressed first.  From a change perspective, the input here is about the readiness of the stakeholder to receive the change, and what timing and work is required to get there.
  10. Urgency and Dependencies: Changes that unblock other work or are time-sensitive should be prioritized. Dependencies between changes must be mapped to ensure logical sequencing.  For example, work required to lift capability/leadership or readiness may be critical dependencies, without which the change cannot be delivered successfully.
  11. Feasibility and Risk: Assess the feasibility and risks associated with each change. High-risk assessment of changes might require more careful planning and monitoring but should not necessarily be deprioritized if their impact is critical.  The change input here is the people impact for the impacted stakeholders with other changes not just within this project/program, but with the overall portfolio or even outside the portfolio (including business-driven changes).
  12. Proposed Changes: This column lists all suggested changes, each represented by a card detailing the change’s purpose, impacted areas, and expected benefits.
  13. Under Review: Changes move here once they are being evaluated for feasibility, risks, and alignment with project goals.
  14. Implementation Planning: Approved changes are further detailed, including resource allocation, timelines, and specific tasks needed for implementation.
  15. In Progress: Changes that are actively being worked on are tracked here, showing current status and any blockers encountered.
  16. Monitoring: Recently implemented changes are monitored to ensure they are delivering the expected outcomes and to identify any issues early.
  17. Done: Fully implemented and stabilized changes are moved here, marking their successful completion.
  18. Value and Impact: In conjunction with the project team prioritize changes based on their potential value and impact. High-value changes that significantly improve project outcomes or stakeholder satisfaction should be addressed first.  From a change perspective, the input here is about the readiness of the stakeholder to receive the change, and what timing and work is required to get there.
  19. Urgency and Dependencies: Changes that unblock other work or are time-sensitive should be prioritized. Dependencies between changes must be mapped to ensure logical sequencing.  For example, work required to lift capability/leadership or readiness may be critical dependencies, without which the change cannot be delivered successfully.
  20. Feasibility and Risk: Assess the feasibility and risks associated with each change. High-risk changes might require more careful planning and monitoring but should not necessarily be deprioritized if their impact is critical.  The change input here is the people impact for the impacted stakeholders with other changes not just within this project/program, but with the overall portfolio or even outside the portfolio (including business-driven changes).

Ordering Change Planning and Implementation

Collaborative Planning:

Engage stakeholders and team members in planning sessions to discuss and agree on the priority of changes. This collaborative approach ensures that all perspectives are considered and that there is buy-in from those affected by the changes.  This includes change champions.

Regular Review and Adaptation:

The Kanban board should be regularly reviewed and updated, within the change team and within the project team. During these reviews, re-prioritize changes based on new information, shifting project needs, and feedback from implemented changes. This iterative approach aligns with Agile principles of flexibility and continuous improvement.

Limit Work in Progress (WIP):

To avoid overloading the change team and ensure focus, limit the number of changes in progress at any given time. This constraint encourages the team to complete current tasks before taking on new ones, promoting a steady and manageable workflow.

Use Metrics and Feedback:

  1. Utilize metrics such as cycle time (how long a change takes to move from start to finish, from awareness to engagement to eventual adoption) and work with the project team on the throughput (how many changes are completed in a specific timeframe) to assess the efficiency of the change management process.  For example, based on the size and complexity of each discrete piece of change delivered, how long did this take and what was the deviance from actual time period planned? Feedback from these metrics should inform decisions about prioritization and process adjustments.
  2. Engage stakeholders and team members in planning sessions to discuss and agree on the priority of changes. This collaborative approach ensures that all perspectives are considered and that there is buy-in from those affected by the changes.  This includes change champions.
  3. The Kanban board should be regularly reviewed and updated, within the change team and within the project team. During these reviews, re-prioritize changes based on new information, shifting project needs, and feedback from implemented changes. This iterative approach aligns with Agile principles of flexibility and continuous improvement.
  4. To avoid overloading the change team and ensure focus, limit the number of changes in progress at any given time. This constraint encourages the team to complete current tasks before taking on new ones, promoting a steady and manageable workflow.
  5. Utilize metrics such as cycle time (how long a change takes to move from start to finish, from awareness to engagement to eventual adoption) and work with the project team on the throughput (how many changes are completed in a specific timeframe) to assess the efficiency of the change management process.  For example, based on the size and complexity of each discrete piece of change delivered, how long did this take and what was the deviance from actual time period planned? Feedback from these metrics should inform decisions about prioritization and process adjustments.

Benefits of Using Kanban for Change Management

Implementing a Kanban board for change management in Agile projects offers several benefits:

  1. Transparency: Everyone involved can see the status of change activities, leading to better communication and coordination.
  2. Flexibility: The board can be easily adjusted to reflect changing priorities and project dynamics.
  3. Focus: Limiting WIP helps the team maintain focus and reduces the risk of burnout and task switching.
  4. Continuous Improvement: Regular reviews and adaptations promote a culture of continuous improvement, ensuring that change management processes evolve and improve over time.

Change artefact example 3: Change Impact Assessment

A Change Impact Assessment (CIA) is an essential component in managing organizational change, particularly in agile projects where the focus is on iterative and incremental improvements. The assessment helps to understand the scope and magnitude of the change, identify affected stakeholders, and plan interventions to manage impacts effectively.  An agile-friendly CIA is more summarised, and gets to the heart of what the impact is, who is impacted, how, to what extent, and when.

Below are the core elements of a change impact assessment, with a comparison to traditional methods:

1. Identifying the Impacts

Agile Approach: In scaled agile projects, the impact identification is ongoing and iterative. Each sprint or iteration is reviewed to assess the impacts of delivered changes. This dynamic approach ensures that emerging impacts are quickly recognized and addressed.

Traditional Approach: Impact identification is typically conducted at the beginning of the project, with periodic reviews. This method can be less responsive to new impacts discovered during the project lifecycle.

2. Stakeholder Identification and Analysis

Agile Approach: Continuous stakeholder engagement is crucial. Stakeholders are regularly consulted, and their feedback is integrated into the process. Agile methods ensure that stakeholders’ changing needs and concerns are promptly addressed.

Traditional Approach: Stakeholder analysis is often conducted early in the project, with limited ongoing engagement. This can result in less adaptability to stakeholders’ evolving requirements.

3. Extent and Nature of Impacts

Agile Approach: The extent of impacts is assessed incrementally, considering the cumulative effect of changes over multiple iterations. This allows for a nuanced understanding of how impacts evolve over time.

Traditional Approach: Typically focuses on a comprehensive initial assessment, with less emphasis on the evolution of impacts throughout the project.

4. Timing of Impacts

Agile Approach: Timing is aligned with the iterative delivery schedule. The impacts are mapped to specific iterations or sprints, allowing for precise planning and mitigation.

Traditional Approach: Timing is generally assessed at the project level, which can make it harder to pinpoint when specific impacts will occur during the project lifecycle.

Typical Sections of an Agile Change Impact Assessment

  1. Impact Overview:
  2. Explanation: Summarizes the nature and scope of the change, providing a high-level view of the anticipated impacts.
  3. Agile Twist: Updated regularly with each iteration to reflect new findings and emerging impacts.
  4. Stakeholder Impact Analysis:
  5. Explanation: Identifies who will be affected by the change and how. It details the extent of the impact on different stakeholder groups.
  6. Agile Twist: Involves continuous stakeholder feedback and updates to capture evolving impacts.
  7. Impact Extent and Nature:
  8. Explanation: Describes the extent (e.g., minor, moderate, significant) and nature (e.g., process, technology, cultural) of the impacts.
  9. Agile Twist: Assessed incrementally, considering both immediate and long-term impacts across iterations.
  10. Impact Timing:
  11. Explanation: Specifies when the impacts are expected to occur, mapped to the project timeline.
  12. Agile Twist: Aligned with sprint or iteration schedules, allowing for detailed timing predictions.
  13. Mitigation Strategies:
  14. Explanation: Outlines plans to manage and mitigate identified impacts.
  15. Agile Twist: Adaptive strategies that are refined continuously based on iteration reviews and stakeholder feedback.
  16. Monitoring and Review:
  17. Explanation: Describes how the impacts will be monitored and reviewed throughout the project.
  18. Agile Twist: Continuous monitoring with iteration-end reviews to ensure timely identification and management of impacts.
  19. Explanation: Summarizes the nature and scope of the change, providing a high-level view of the anticipated impacts.
  20. Agile Twist: Updated regularly with each iteration to reflect new findings and emerging impacts.
  21. Explanation: Identifies who will be affected by the change and how. It details the extent of the impact on different stakeholder groups.
  22. Agile Twist: Involves continuous stakeholder feedback and updates to capture evolving impacts.
  23. Explanation: Describes the extent (e.g., minor, moderate, significant) and nature (e.g., process, technology, cultural) of the impacts.
  24. Agile Twist: Assessed incrementally, considering both immediate and long-term impacts across iterations.
  25. Explanation: Specifies when the impacts are expected to occur, mapped to the project timeline.
  26. Agile Twist: Aligned with sprint or iteration schedules, allowing for detailed timing predictions.
  27. Explanation: Outlines plans to manage and mitigate identified impacts.
  28. Agile Twist: Adaptive strategies that are refined continuously based on iteration reviews and stakeholder feedback.
  29. Explanation: Describes how the impacts will be monitored and reviewed throughout the project.
  30. Agile Twist: Continuous monitoring with iteration-end reviews to ensure timely identification and management of impacts.

To read more about agile tools for change managers, check out Five Agile Change Tool Kits.

Stakeholder Engagement in a Scaled Agile Environment

Planning and designing stakeholder engagement activities in a scaled agile environment requires a dynamic, iterative approach that contrasts significantly with traditional, non-agile methods. In SAFe, the focus is on continuous collaboration, transparency, and adaptability, ensuring that stakeholders are actively involved throughout the project lifecycle.

Iterative and Continuous Engagement

Scaled Agile Approach: Stakeholder engagement is an ongoing process. Agile frameworks emphasize regular touchpoints, such as sprint reviews, planning meetings, and daily stand-ups, where stakeholders can provide feedback and stay informed about progress. These frequent interactions ensure that stakeholder input is continuously integrated, enabling swift adjustments and alignment with evolving needs. This iterative approach fosters a collaborative environment where stakeholders feel valued and engaged throughout the project.  Engagement rhythms and processes should also be established not just at a project, but program, portfolio and enterprise levels as required.

Non-Agile Approach: Traditional methodologies often involve stakeholder engagement at fixed points in the project timeline, such as during initial requirements gathering, major milestone reviews, and final project delivery. This approach can lead to periods of limited communication and delayed feedback, which may result in misaligned expectations and missed opportunities for timely course corrections.

Flexibility and Adaptation

Scaled Agile Approach: Agile projects embrace change, allowing stakeholder engagement activities to be flexible and adaptive. As project requirements evolve, the engagement strategy can be adjusted to address new priorities or challenges. This flexibility ensures that stakeholder needs are consistently met, and any concerns are promptly addressed. Agile frameworks encourage a culture of openness and continuous improvement, where stakeholder feedback directly influences the direction of the project.  Change managers need to ensure that stakeholder understand this fully, and have the skills to work within this context, not just with the project team but in leading their teams through change, when ‘the change’ may be constantly shifting.

Non-Agile Approach: In contrast, traditional approaches tend to follow a rigid engagement plan that is set at the project’s outset. While this provides a clear structure, it can be less responsive to changing stakeholder needs or external conditions. Adjusting the engagement strategy mid-project can be challenging and may require significant effort, leading to delays and potential dissatisfaction among stakeholders.

Collaborative Tools and Techniques

Scaled Agile Approach: Agile environments leverage a variety of collaborative tools and techniques to enhance stakeholder engagement. Digital platforms such as Jira, Confluence, and Miro facilitate real-time collaboration, transparency, and documentation. Agile ceremonies, such as retrospectives and demos, provide structured opportunities for stakeholders to participate and contribute. These tools and techniques help maintain a high level of engagement and ensure that stakeholders have a clear view of project progress and challenges.

Non-Agile Approach: Traditional methods might rely more heavily on formal documentation and periodic reports for stakeholder communication. While these methods ensure thorough documentation, they can sometimes create barriers to real-time collaboration and immediate feedback. Meetings and reviews are often scheduled infrequently, which can lead to less dynamic interaction compared to agile practices.

Planning Stakeholder Engagement Activities

  1. Regular Touchpoints: Schedule frequent meetings and reviews to ensure continuous stakeholder involvement. Examples include sprint reviews, iteration planning meetings, and daily stand-ups.  Business-led rhythm that enable the dissemination and engagement of updates to teams is also critical.
  2. Flexible Engagement Plans: Develop engagement strategies that can be easily adapted based on stakeholder feedback and changing project requirements.
  3. Use of Collaborative Tools: Implement digital tools that facilitate real-time collaboration and transparency. Tools like Jira and Confluence can help keep stakeholders informed and involved.  Non-digital engagement tools may also be leveraged to fully engage with stakeholders, beyond one-way push communication.  Assessment needs to be made of the openness and ability to engage regarding the change through the chosen channels.
  4. Active Feedback Loops: Establish mechanisms for collecting and integrating stakeholder feedback continuously. This can be done through retrospectives, surveys, and informal check-ins.
  5. Clear Communication Channels: Maintain open and clear communication channels to ensure that stakeholders can easily provide input and receive updates on project progress.

As mentioned previously, the change approach, including engagement approaches, need to take into account the broader organisational context of program, portfolio and enterprise levels.  This may mean mapping out the various channels and how they can be used for different changes, stakeholders and organisational levels.

Supporting Agile Delivery Cadence

To align change management activities with agile delivery cadence, it’s essential to integrate them into the core agile events, such as PI (Program Increment) planning and demos. Here’s how:

PI Planning

PI planning, or program increment planning, is a critical event in the agile framework, where teams come together in the PI planning process to plan and commit to a set of objectives for the next increment. During PI planning sessions or PI planning events (including team breakouts), ensure that change management considerations are part of the discussion. This involves:

– Including Change Management Objectives within PI objectives and program vision: Ensure that change management objectives and organizational readiness are included in the PI planning agenda as a critical part of project management. This helps align the change activities with the overall delivery goals.

– Identifying Change Risks and Dependencies: Identify any dependencies related to the change initiative that may impact the delivery schedule and the overall agile release train. This ensures that potential risks are addressed early and do not disrupt the delivery process.  Common considerations include the various people change impacts across the program and how they intersect or overlap

– Engaging Stakeholders: Involve key stakeholders in the PI planning sessions. This ensures that not just product managers but business stakeholders understand the change objectives and are committed to supporting the change initiative during the implementation process.  PI planning is also a great opportunity to assess and see in action the level of engagement, support and potential leadership skills of key stakeholders to reach the common goals and business benefits.

Demos

Demos are an opportunity to showcase the progress of the agile teams and gather feedback from stakeholders as a part of the iteration plans and sprint planning. Use demos to communicate the benefits and progress of change initiatives within the entire agile release train. Engaging stakeholders in these demos can help them see the value and stay committed to the implementation plan. Here’s how:

– Highlighting Change Benefits: During demos, highlight the benefits of the change initiative and how it supports the overall product delivery goals. This helps stakeholders understand the value of the change and its impact on the project.

– Gathering Feedback: Use demos as an opportunity to gather feedback and user stories from stakeholders. This helps identify any concerns or areas for improvement and ensures that the change initiative remains aligned with stakeholder needs.

– Showcasing Progress: Showcase the progress of the change initiative during demos. This provides stakeholders with a clear understanding of how the change is evolving and the positive impact it is having on the project.

By embedding change management activities into these agile ceremonies, change managers can ensure that change initiatives are aligned with the delivery schedule and maintain stakeholder buy-in.

Implementing Change Activities as Small Experiments

One of the key principles of agile is to work in small increments and learn quickly. Change management activities can adopt this approach by implementing small experiments, such as:

Messaging

Test different communication messages to see which resonates best with stakeholders. Gather feedback and refine the messaging based on reactions. This iterative approach ensures that the communication strategy is effective and supports the change initiative. Consider the following:

– A/B Testing: Use A/B testing to evaluate different messages. This involves sending two variations of a message to different stakeholder groups and comparing the responses to determine which one is more effective.

– Feedback Collection: Collect feedback from stakeholders on the messaging. This can be done through surveys, focus groups, or informal conversations.

– Message Refinement: Refine the messaging based on the feedback received. This ensures that the communication remains relevant and impactful.

Stakeholder Involvement

Experiment with various levels of stakeholder involvement to determine the most effective way to engage them. Use these insights to inform future engagement and risk management strategies and your overall implementation strategy. Here’s how:

– Pilot Programs: Implement pilot programs with small groups of stakeholders to test different involvement strategies. This provides valuable insights into what works best and helps refine the engagement approach.

– Engagement Metrics: Track engagement metrics to evaluate the effectiveness of different involvement strategies. This includes participation rates, feedback quality, and overall stakeholder satisfaction.

– Iterative Adjustments: Make iterative adjustments to the involvement strategies based on the insights gained. This ensures that stakeholder engagement remains effective and aligned with the change initiative.

By treating change activities as experiments, change managers can adapt quickly to what works best, ensuring a smoother integration with the agile delivery process.

Best Practices for Integrating Change Management with Agile

Successfully integrating change management with agile methodologies requires a strategic approach. Here are some best practices to consider:

Foster Collaboration

Encourage collaboration between change managers and agile teams, as well as key business stakeholders within the business context. This helps ensure that different disciplines and functions are aligned and working towards the same goals. Consider the following strategies:

– Joint Planning Sessions: Conduct joint planning sessions to align change management activities with agile delivery approaches and schedules. This ensures that both disciplines are working towards the same objectives.

– Regular Communication: Establish regular communication channels between change managers and agile teams. This helps keep everyone informed and ensures that any issues or concerns are addressed promptly.  Specifically focus on various agile roles such as UX (user experience), business analysis, testing, and portfolio management.  There are key intersections of change work and each of these disciplines, beyond general project planning and coordination.

The below is an example of a portfolio level adoption dashboard from The Change Compass.

Enterprise change management dashboard

Change Data-Driven Insights is absolutely a Must-have for SAFe

In SAFe, change management driven by data insights is critical to ensure that changes are not only effective but also efficient and sustainable. Data-driven change management leverages quantitative and qualitative data to guide decisions, optimize processes, and align strategic goals across the organization. By incorporating metrics and analytics, organizations can gain a comprehensive understanding of the impact and progress of change initiatives, allowing for timely adjustments and informed decision-making.

At the portfolio level within a SAFe setting, data-driven insights are essential for prioritizing initiatives and allocating resources effectively.  More than this, change data including stakeholder capability, readiness and impact levels can be critical to determine when releases should happen, the priority of releases, and the sequencing of releases.

Ill-prepared or insufficiently skilled stakeholders may require longer time to adapt to the change.  Also, looking beyond the project itself, by understanding the overall change landscape for the impacted stakeholders, change releases may need to be chunked and packaged accordingly to maximise adoption success.

Key attention should also be paid to the impact on business performance of impacted stakeholders, not just from a change volume perspective, but also from a strategy perspective in terms of how best to reduce risk of performance disruptions.  Is it through exemplary middle leadership?  Or frontline engagement?  Or the power of change champions embedded across the business?

At the enterprise level, data-driven change management enables organizations to scale agile practices consistently and coherently across the entire team across multiple portfolios. This involves the use of enterprise-level dashboards and analytics tools that provide a holistic view of the organization’s agile transformation. Key performance indicators (KPIs) such as employee impact data, adoption rates, readiness metrics and productivity metrics help leaders assess the effectiveness of change initiatives and identify areas that require additional support or intervention. For instance, tracking the adoption rate of agile practices across different departments can highlight areas where additional training or coaching is needed to ensure consistent implementation.

Integrating change management with scaled agile methodologies is essential for seamless product delivery in today’s dynamic business environment. By creating agile-style deliverable artefacts early, continuously adapting engagement activities, supporting agile delivery cadence, and implementing change activities as small experiments, measure change progress and outcomes, change managers can effectively support agile product delivery. This integration not only enhances the success of change initiatives but also ensures that product delivery is seamless and aligned with organizational goals and the strategic plan.

By fostering collaboration, embracing agile principles, and using data-driven insights, change managers can create a cohesive strategy that maximizes the benefits of both change management and agile methodologies. This holistic approach ensures that change initiatives are successful, stakeholders are engaged, and product delivery is efficient and effective.

To read more about Change Measurement, check out our library of articles here.

Chat to us to find out more about how to leverage the power of a change measurement platform to sustain your single source of truth to support your scaled agile organisation.

  1. Change Management in the Digital Age: Leveraging AI, Data, and Automation for Strategic Impact
  2. Rethinking Change Management Maturity—Why Traditional Capability-Building Falls Short
  3. How organisational change management software drives adoption
  4. Building Change Portfolio Literacy in Senior Leaders: A Practical Guide
  5. 7 Common Assumptions About Managing Multiple Changes That Are Wrong

Why change management is omitted from agile methodology

Why change management is omitted from agile methodology

Agile methodology is fast becoming the ‘norm’ when it comes to project methodology. There are strong benefits promised of faster development time, the ability to morph with changing requirements, less time required to implement the solution, and a better ability to meet project objectives through continuous improvement. There aren’t too many organisations that do not use some form of agile project methodology in how they manage initiatives.

What started out as a way of developing software has evolved into the accepted methodology for managing projects. A scan of literature available on the internet shows a significant outline of the various roles, including the product owner and the development team, and their importance to stakeholders, including end users, in the agile project methodology process. Most roles are clearly outlined and accounted for. There are clear roles established for the business owner, the project manager, the scrum master, developers, testing and quality, product manager, architect, human-centred designer, and even IT operations.

However, there is a glaring gap. What about the role of the change manager?

A review of literature available through project management organisations such as APM (Association of Project Management) and PMI (Project Management Institute) showed glaring omission of the role of the change manager or change management practitioners from agile methodology. The same is also true for Scaled Agile Frameworks where there is a brief mention of the importance of change management in the agile approach, but no mention of the role of the change manager/practitioner.

Is it that there are less projects requiring change managers?

The evidence is against this hypothesis. Jobs in change management are plentiful, with data on ‘Indeed’ online employment portals pulling up over 38,000 job postings. On top of this, there is an increasing number of jobs posted. According to the U.S. Bureau of Labor Statistics, “management analytics” which includes change management, is projected to have a 14% growth rate between 2018 and 2028. In Australia, the ‘Seek’ employment platform projected change management job growth to be at 15% growth in the next 5 years.

Is it that agile methodology is more for technical projects and therefore the omission of change managers?

The agile approach and agile manifesto can be used for a range of different projects, but not all projects. There is certainly evidence of agile project methodology used by software developers in a wide range of industries from financial services, government, non-profit, pharmaceuticals, utilities, and retail industries. The agile methodology is commonly cited for being better for projects where the outcome is not clearly known and where the end change has a level of uniqueness. There are times, though, when waterfall methodology is more appropriate, depending on the situation.

However, it is not true that agile methodology is only used for more technical projects. Even for projects where the focus is not on technical development, agile approaches are used widely. Agile changes have been used for re-organisation exercises. Here is an example from the Business Agility Institute. Executive teams also use agile means to manage various strategic initiatives that are not technical. Agile approaches are even applied to managing church initiatives.

What is the likely reason for the clear omission of change management in the agile methodology?

Organisations in charge of documenting agile methodology are mainly focused on project management and software development. If we take the examples of PMI and APMG, both are project management associations, and both are focused on the project management perspectives of agile, particularly in complex environments. The portion on organizational change management is a specialism of project management. It could be that these organisations have not sufficiently developed agile change management methodology to integrate with agile project management.

Organisations in charge of documenting agile methodology are mainly focused on project management and software development, and not include the agile change management process. If we take the examples of PMI and APMG, both are project management associations, and both are focused on the project management perspectives of agile. The portion on organizational change management is a specialism of project management. It could be that these organisations have not sufficiently developed agile change management methodology to integrate with agile project management.

Even at Scaled Agile, which is about applying agile across the organisation, the omission of the role of change managers is still the case. Frameworks from Scaled Agile are quite detailed and rigorous. All aspects of the roles of various organisational members, including scrum teams, are clearly outlined. Even the role of IT departments in DevOps are clearly spelled out to support agile. But not the role of change managers. Again, this could be due to those at Scaled Agile not having a change management background, and therefore not being able to articulate the various role detail.

However, there are some very critical roles that change practitioners play not only at project level, but at program, epic, and organisational levels. Without the right change management support the following are key risks when organisations are working at SaFe (scaled agile) level:

  1. Change sequencing to maximise adoption across the change portfolio
  2. Packaging change to achieve optimal change adoption, e.g. in terms of integrating communications and learning interventions across projects
  3. Establishing business unit based change champions that can support multiple projects and can help piece together different changes for impacted employees
  4. Identify and manage potential change saturation and change fatigue

There are some attempts at closing the gap to document agile change management approaches as a part of the change management process. However, most are conceptual, high level, and not sufficiently detailed to provide clear guidance and practical application for the change practitioner. On the other hand, the work of change management in agile projects should not only be clear for the change practitioner but also be clear for the project manager and other project members.

To access practical agile playbooks visit our agile playbook resources.

What’s the problem of omitting the role of change managers from agile methodologies?

1. The role of change management could easily be omitted. Particularly for less experienced project managers who are starting out in agile. The risk could be that change management is omitted from the project altogether since it is not called out as a clear role

2. Change practitioners and agile practitioners are not clear with the roles they play and therefore are not sufficiently involved in driving and supporting the project in the right way. Since there is not a clear set of guidelines and agile principles methodology for change practitioners, it is common to see varying approaches in how change managers support agile projects within the current business environment, with some still using a similar approach as to supporting traditional change management and waterfall projects which may not be appropriate.

3. Agile projects are not successful because change management work is not sufficiently incorporated into agile processes, particularly in the context of digital transformation. With change management roles not spelt out, the project executes the change without critical change management foundations, and therefore, by embracing agile thinking, it is at the risk of not achieving the adoption, adaptation, and benefit realisation targeted.

What should we do about this?

1. Encourage change management associations such as CMI and ACMP to invest in detailing agile change management methodology in a way that sets standards and guidelines for change management skills practitioners to follow.

2. Influence and work with APMG, PMI and Scaled Agile to include explicitly the role of change managers and agile change management methodology.

Change management is emerging to be a strong discipline that executives are starting to recognise as critical to successful change. The role of change practitioners should be stated explicitly and recognised clearly. Change managers should not have to tip-toe in maneuvering their place in supporting agile change projects, nor should they need to convince other project team members of their place throughout various agile routines and methodology phases. It is now time for the change community to drive this and achieve the recognition that it deserves.

The Peeling the Onion Protocol: Key to Change Management

The Peeling the Onion Protocol: Key to Change Management

Change management, much like peeling an onion, involves uncovering multiple layers before reaching the core. Each layer peeled back in the journey of planning and implementing change reveals new insights about the organization and the stakeholders impacted by the change. This process is essential to understanding the full scope of the change, adapting strategies accordingly, and ensuring successful implementation. By examining the various facets of an organization, such as leadership capability, operational practices, and cultural traits, we can better navigate the complexities of change management. Let’s explore the analogy of peeling an onion in change management and some practical insights for transforming change outcomes.

What is the peeling the onion protocol and how does it work?

The Peeling the Onion Protocol is a change management strategy that involves gradually uncovering layers of resistance within an organization. By systematically addressing concerns and facilitating open dialogue, this protocol fosters understanding and acceptance of change, ultimately leading to smoother transitions and enhanced collaboration among team members.

Peeling the layers – each layer reveals a different facet of the organisation and how they may or may not be conducive to supporting the change.  Here are some ‘layers’ you may want to examine.

Leadership and Managerial Capability in Managing Change

Effective change management begins with strong leadership. Leaders and managers play a crucial role in guiding the organization through the transition. Peeling back this layer reveals whether leaders are equipped with the necessary skills, knowledge, and attitudes to drive change. It also highlights their ability to inspire and mobilize their teams, communicate the vision effectively, and manage resistance. Assessing leadership capability is fundamental, as inadequate leadership can hinder the entire change process.

Operational and Business Practices

The next layer involves examining the organization’s operational and business practices. This includes evaluating current workflows, processes, and systems to identify areas that may need adjustment or improvement. Understanding how daily operations align with the proposed changes helps in anticipating potential disruptions and devising strategies to minimize them. Are existing practices consistent with the end state of the change? Are existing practices consistent? (or NA?) Why or why not? This layer also involves identifying key performance indicators (KPIs) that can measure the success of the change initiatives (https://thechangecompass.com/how-to-manage-a-multitude-of-change-initiatives-including-enterprise-wide/).

Change Governance Practices and Structure

Change governance refers to the frameworks and structures in place to manage and oversee change initiatives. Having the right governance structure ensures that the right oversight and decision making is setup to steer the change to success. Peeling back this layer involves assessing the effectiveness of existing governance mechanisms, such as steering committees, decision-making protocols, and accountability structures. Strong change governance ensures that change initiatives are well-coordinated, resources are allocated appropriately, and progress is monitored consistently. Weak governance, on the other hand, can lead to confusion, misalignment, and failure to achieve desired outcomes.

Key questions to ask here include such as:

  1. Is there sufficient governance bodies in place at different levels of the organisation to support change?
  2. Are there too many governance bodies?
  3. Are decision-making processes clear and effective?
  4. Are the right stakeholders involved in the relevant decision-making areas?

Engagement Channels

Effective engagement is critical in change management.  This is more than just communication. This layer focuses on the channels and methods used to engage with stakeholders throughout the change process. Evaluating engagement channels helps in understanding how information is disseminated, feedback is collected, and concerns are addressed. It also highlights the effectiveness of internal communications and the role of external communications in managing stakeholder expectations and perceptions. What channels are most effective for what audience groups? Are there any gaps for engaging with all groups of stakeholders? (beyond just blasting emails or messages).

Change Champion Network

Change champions are resignated individuals within the organization who advocate for and support the change initiatives. Peeling back this layer involves identifying and empowering these champions. It also includes assessing their influence, credibility, and ability to motivate others. A strong network of change champions can facilitate smoother transitions by promoting buy-in, addressing resistance, and reinforcing positive behaviors. With the right nurturing and experience, an organisation-wide change champion network can act to support a myriad of change initiatives.

System and Process Maturity

The maturity of systems and processes within an organization significantly impacts the success of change initiatives. This layer involves evaluating the current state of technological systems, process automation, and data management practices. Mature systems and processes provide a solid foundation for implementing changes efficiently and effectively. Conversely, immature systems may require significant upgrades or overhauls to support the desired changes.

Change Management Maturity

Change management maturity refers to the organization’s overall capability to manage change. Peeling back this layer involves assessing the maturity of change management practices, methodologies, and tools. Organizations with mature change management capabilities have established frameworks, experienced practitioners, and a culture that embraces change. In contrast, organizations with low maturity may struggle with inconsistencies, resistance, and a lack of structured approaches.

To read more about improving change management maturity visit our article – A Comprehensive Guide to Elevating Change Management Maturity.

Resources and Capacity

This layer examines the availability of resources and capacity to support change initiatives. It includes assessing the organization’s financial resources, human capital, and physical infrastructure. Adequate resources and capacity are essential for executing change plans, overcoming obstacles, and sustaining momentum. Insufficient resources can lead to delays, reduced quality, and increased stress on employees. This does not just include the resources required within the project itself, it points more to the impacted stakeholders and if they have the resources and capacity required to undergo the change.

Culture and Behavioral Traits

Organizational culture and behavioral traits play a significant role in how change is perceived and adopted. Peeling back this layer involves understanding the underlying values, beliefs, and behaviors that influence how employees respond to change. It also includes identifying cultural strengths that can be leveraged and cultural barriers that need to be addressed. A supportive culture fosters resilience, adaptability, and a positive attitude towards change.

Specifically:

  1. Do existing behaviours and practices support the change end state?
  2. Are there potentially inconsistent behaviours comparing the end state and the current state?
  3. Beyond the specific behaviours required in the change initiative itself, how are these in alignment with broader cultural practices?

Key Takeaways from the Onion Analogy in Change Management

1. Each Layer Needs to Be Peeled Before Another Layer Can Be Peeled

The process of discovering and understanding the complexities of change cannot be rushed. Each layer provides valuable insights and learning opportunities that prepare the organization for the next layer of discovery. Skipping layers or rushing through the process can lead to incomplete assessments, overlooked challenges, and ineffective solutions. Patience and persistence are crucial for a thorough and successful change management journey.

Assessing and understanding each layer can take time. Data, both quantitative and qualitative, may be required to truly understand what each layer means and how it implicates the change.

2. How the Onion Appears May Not Be What It Is at Its Core

Initial perceptions of the organization may not reflect its true state. It takes time and effort to uncover the deeper issues, strengths, and opportunities. This requires a willingness to look beyond surface-level indicators and delve into the core aspects of the organization. Attention to detail and a commitment to uncovering the truth are essential for developing accurate and effective change strategies.

For example:

  1. Are publically communicated and reinforced messages acted on?
  2. Do leaders practice what they preach?
  3. Do stakeholders commit to decisions already made? Or do they ignore it?
  4. Is there clear alignment between different layers of the organisation? How is this done?

3. You May Discover Rotten Parts That Need to Be Replaced

During the process of peeling back layers, you may encounter parts of the organization that are severely inadequate or dysfunctional. These “rotten” parts may need to be replaced or significantly improved before the change can proceed. This could involve overhauling critical capabilities, restructuring teams, or implementing new systems. Recognizing and addressing these issues promptly is essential for ensuring the overall health and success of the organization.

You may find, for example:

  1. Stakeholders that are adamant to block the change for various reasons
  2. Teams that simply do not have the right skills or attitude to transition to the required state
  3. Processes that are simply outdated or convoluted, so much that end state targets cannot be achieved
  4. Systems that are outdated and do not provide the right insights to support the end state

4. Different Types of Onions and Organizations

Just as there are different types of onions, organizations vary in size, complexity, and nature. Assessing the complexity of the change at the outset helps in determining the time, effort, and resources required to peel back the layers. A comprehensive understanding of the organization’s unique characteristics allows for tailored change management strategies that address specific needs and challenges.

Practical Steps for Applying the Onion Analogy in Change Management

Step 1: Initial Assessment and Planning

Begin by conducting a thorough initial assessment of the organization. This involves gathering data, engaging with key stakeholders, and understanding the current state of affairs. Develop a comprehensive change management plan that outlines the objectives, scope, and timelines for each layer of the onion. This plan should also identify key metrics for measuring success and mechanisms for tracking progress.

Step 2: Assess Leadership and Managerial Capability

Evaluate the capability of leaders and managers to drive change. This includes assessing their skills, experience, and attitudes towards change. Provide training and support where needed to enhance their ability to lead effectively. Strong leadership is foundational to the success of any change initiative.

Step 3: Examine Operational and Business Practices

Analyze current workflows, processes, and systems to identify areas that may require adjustment. Engage with employees at all levels to gather insights and understand potential bottlenecks. Develop strategies to streamline operations and ensure alignment with the change objectives.

Step 4: Review Change Governance Practices

Assess the existing governance structures and practices in place to manage change initiatives. Ensure that there are clear decision-making protocols, accountability mechanisms, and regular progress reviews. Strengthen governance frameworks as needed to support effective change management.

Step 5: Evaluate Engagement Channels

Review the channels and methods used to communicate with stakeholders. Ensure that there are effective mechanisms for disseminating information, collecting feedback, and addressing concerns. Enhance engagement strategies to foster transparency, trust, and collaboration.

Step 6: Identify and Empower Change Champions

Identify individuals within the organization who can serve as change champions. Empower them with the necessary tools, resources, and support to advocate for the change initiatives. Leverage their influence and credibility to promote buy-in and address resistance.

Step 7: Assess System and Process Maturity

Evaluate the maturity of technological systems and processes. Identify areas that require upgrades or improvements to support the change. Invest in the necessary infrastructure and tools to ensure seamless implementation.

Step 8: Assess Change Management Maturity

Conduct a maturity assessment of the organization’s change management capabilities. Identify gaps and areas for improvement. Develop and implement strategies to enhance change management practices, methodologies, and tools.

Step 9: Review Resources and Capacity

Evaluate the availability of resources and capacity to support the change initiatives. Ensure that there are adequate financial, human, and physical resources to execute the change plans. Address any resource constraints proactively to prevent delays and disruptions.

Step 10: Understand Culture and Behavioral Traits

Conduct a cultural assessment to understand the underlying values, beliefs, and behaviors that influence how employees respond to change. Identify cultural strengths that can be leveraged and barriers that need to be addressed. Develop strategies to foster a supportive culture that embraces change.

To read more about driving behavioural change check out The ultimate guide to behaviour change.

The analogy of peeling an onion provides a powerful framework for understanding and managing change within an organization. Each layer peeled back reveals new insights and learning opportunities that are essential for successful change management. By carefully examining the various facets of the organization, such as leadership capability, operational practices, and cultural traits, organizations can navigate the complexities of change more effectively.

Patience, persistence, and attention to detail are key to uncovering the true state of the organization and developing tailored strategies that address specific needs and challenges. Ultimately, the journey of peeling the onion in change management leads to a deeper understanding, better preparation, and more successful change outcomes.

Why ‘Release on Demand’ is the Hidden Key to Agile Success (and How Change Management Can Drive It)

Why ‘Release on Demand’ is the Hidden Key to Agile Success (and How Change Management Can Drive It)

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:

  1. Release – Delivering the product or change to users.
  2. Stabilise and Operate – Ensuring the release is operationally sound and running smoothly.
  3. Measure and Learn – Assessing the release’s impact and learning from the results.
  4. 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:

  1. Collect feedback from end-users and support staff on initial challenges and address these promptly.
  2. 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:

  1. Conducting surveys, interviews, or focus groups to gauge user and stakeholder sentiment.
  2. Monitoring adoption rates and identifying any training gaps or knowledge shortfalls.
  3. 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:

  1. Refining future communication and training plans based on user feedback.
  2. Addressing any gaps in stakeholder support or sponsorship.
  3. 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

FFor 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 and continuous integration.

Here are some tips to help change managers get the timing right:

  1. Analyze stakeholder engagement levels: Regularly assess how engaged and ready stakeholders are, tailoring messaging and interventions based on their feedback and sentiment.
  2. 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.
  3. 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.

Expanding Release Governance Beyond Technical Focus

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:

  1. Establish clear communication channels with project teams and product owners to ensure people readiness factors are consistently part of release discussions.
  2. 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.
  3. 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.