This case describes a large-scale organizational change effort within a complex insurance environment responsible for developing and operating multiple digital products. The initiative emerged from a growing need to improve responsiveness, quality, and adaptability in product delivery. The organization had already experimented with agile practices in isolated teams, which generated encouraging results. These early successes created momentum for expanding agile ways of working across a much larger portion of the organization. However, the transition from localized experimentation to broad adoption introduced significant complexity. The transformation ultimately evolved toward a large-scale product development model, though it was not always explicitly labeled or intentionally designed as such. Instead, the organization progressed through a combination of experimentation, necessity, and reactive decision-making, often learning through friction rather than careful planning.
At the outset, the organization followed a traditional functional model, where work was divided into specialized departments such as design, development, and testing. These units operated largely independently, with coordination occurring through formal processes and management layers. Responsibilities were fragmented across multiple roles, each focused on a narrow domain. Testing, for example, was largely separated from development and handled externally, creating long feedback cycles and limited shared ownership of quality. The structure also included numerous supporting functions such as architecture, release coordination, and operations, each acting as an additional layer in the delivery pipeline. This resulted in a system where work moved sequentially through different groups rather than being owned end-to-end by a single team. Leadership attempted to introduce agile practices by replicating team-level structures across the organization. However, this replication did not fundamentally alter the underlying system. Instead, it created multiple isolated teams, each with its own backlog and priorities, reinforcing fragmentation rather than resolving it.
The organization encountered several systemic issues that limited its ability to deliver effectively. One of the most significant challenges was the persistence of component-based thinking. Teams were aligned to technical layers rather than customer-facing outcomes, making it difficult to deliver complete features without extensive coordination. Another issue was the proliferation of roles and responsibilities that diluted accountability. Multiple individuals were involved in defining, prioritizing, and validating work, often leading to confusion and delays. The initial attempt to scale agile practices without addressing structural constraints resulted in what could be described as superficial adoption. Teams followed certain rituals, but the underlying dynamics of handoffs, dependencies, and centralized control remained unchanged. Additionally, there was limited alignment between different parts of the organization. Some groups operated under agile principles, while others continued to follow traditional approaches, creating friction at their interfaces. A lack of strong organizational sponsorship further complicated the situation. Without consistent support from higher levels, the transformation lacked coherence and direction, leaving teams to navigate change largely on their own.
The shift toward a more integrated model emerged as a response to the limitations of the initial approach. Rather than continuing to replicate team-level practices, the organization began to rethink how work was structured across the entire system. A central element of the transformation was the introduction of broader product-oriented structures. Work was reorganized around larger domains of functionality, enabling teams to focus on delivering complete outcomes rather than isolated components. Another important aspect was the consolidation of work into a shared backlog. This created a more unified view of priorities and reduced the fragmentation caused by multiple independent queues of work. The transformation also introduced new coordination mechanisms designed to support alignment across teams while maintaining a degree of autonomy. These mechanisms aimed to balance the need for shared direction with the flexibility required for teams to adapt locally. Although these changes reflected established large-scale agile principles, they were not always applied systematically. Instead, they were introduced incrementally, often in response to immediate challenges.
The journey toward a new organizational model was uneven and at times turbulent. Early attempts at change were characterized by broad, top-down restructuring that affected many teams simultaneously. This created confusion and instability, as individuals struggled to adapt to new roles and expectations. Over time, the organization began to adopt a more iterative approach. Learning from earlier missteps, efforts were made to involve teams more directly in shaping their structures and ways of working. This shift toward greater participation helped build confidence and engagement. Despite these improvements, the transformation faced ongoing challenges. Limited investment in education and training made it difficult for individuals to fully understand the new model. As a result, practices were sometimes applied inconsistently or misunderstood. The presence of external constraints, such as organizational boundaries and legacy processes, further complicated implementation. These factors limited the extent to which changes could be fully realized. Coaching support played a role in guiding the transformation, but its impact was constrained by the broader organizational context. Progress was made, but it required continuous effort and adaptation.
One of the most notable changes was the move toward greater team autonomy. Teams began to take on more responsibility for managing their work, reducing reliance on centralized coordination. Roles evolved as well. Individuals who had previously acted as intermediaries between business and technical functions shifted toward more strategic responsibilities, while teams assumed greater ownership of execution. The introduction of larger organizational groupings enabled a more coherent structure, allowing teams to collaborate more effectively around shared goals. This reduced some of the fragmentation that had characterized the earlier state. Culturally, there was a visible shift toward increased engagement and ownership. As teams became more involved in decision-making, they developed a stronger sense of responsibility for outcomes. However, not all aspects of the organization evolved at the same pace. Certain structural elements remained unchanged, creating tension between the new way of working and existing constraints.
The transformation led to several meaningful improvements, even if the overall journey remained incomplete. One of the most significant outcomes was a noticeable increase in product quality. The organization experienced fewer issues after releases, indicating stronger alignment between development and testing activities. Teams were able to deliver functionality more reliably, with improved predictability in their output. This was supported by better collaboration and a clearer understanding of user needs. The shift toward cross-functional collaboration also reduced the number of defects and improved the overall stability of the system. Problems were identified and addressed earlier in the development process, rather than after release. In addition, there was a marked improvement in how teams interacted with stakeholders. Communication became more direct and effective, leading to better alignment between business objectives and technical implementation. Despite these gains, some challenges persisted. Organizational inconsistencies and external constraints continued to limit the full realization of the intended model.
A central lesson from this case is that scaling agile practices requires more than replicating team-level structures. Without addressing underlying organizational design, such efforts are likely to produce limited results. The importance of aligning structure with desired outcomes is another key takeaway. Teams must be organized in a way that enables them to deliver complete value independently, rather than relying on extensive coordination. The case also highlights the risks of large, simultaneous changes. Broad transformations can create instability if not supported by sufficient preparation, education, and involvement from those affected. Another important insight is the role of organizational support. Without alignment across different levels of the organization, even well-intentioned changes can struggle to gain traction. Finally, the experience underscores the value of continuous learning. Progress was achieved not through a single, well-defined plan, but through ongoing experimentation and adaptation.
This case presents a nuanced view of large-scale organizational change, illustrating both the potential benefits and the inherent challenges. The initial state was characterized by fragmentation, specialization, and indirect communication, all of which hindered effective product delivery. Efforts to improve the situation began with localized experimentation but quickly expanded into broader organizational change. While early attempts were imperfect and sometimes disruptive, they created the conditions for deeper transformation. By gradually shifting toward a more integrated, product-oriented structure, the organization achieved improvements in quality, collaboration, and delivery reliability. However, the journey also revealed the difficulty of sustaining change in the absence of consistent organizational alignment. Ultimately, the case reinforces a fundamental principle: meaningful transformation requires changes not only in practices but also in structure, culture, and leadership. Without addressing these interconnected elements, improvements are likely to remain partial and fragile.