Achieving Organizational Agility in a Major Insurance Firm

Executive Summary

The insurance sector is facing increasing pressure. Customer expectations are evolving rapidly, regulatory pressures are intensifying, and digital-native competitors are setting new standards for responsiveness and efficiency. Legacy operating models, siloed organization, hierarchical decision-making, waterfall-based delivery have left insurers wrestling to keep pace. Legacy models amplified risk instead of managing it. 

NextAgile joined forces with a top insurance company to shatter this pattern. The goal: scale agility, increase predictability, and build real cross-functional teamwork. With pilots, POD-based organization, role-based training, governance designs, and Spotify-based scaling, the company revolutionized how scores of teams produced value. Agility was positioned as an operating model shift, not a delivery experiment.

The outcomes were concrete: smaller handover latencies, quicker decision-making, tighter accountability, open dashboards for leaders, and cultural transformation towards a “one-team” culture. This white paper describes the challenges encountered, the phasewise transformation strategy, the achievements realized, and important lessons for other businesses pursuing enterprise agility. Transparency became the foundation for trust and speed.

Problem Definition

1. Business Context & Challenges

The client, a large insurance company with several business and technology functions, was experiencing systemic delivery issues. The challenges were structural, not individual performance issues:

• Siloed, hierarchical organizations: Business, IT, vendors, and compliance functions operated in silos. Dependencies and conflicting priorities hindered delivery. Escalations were addressed more through relationships than defined ownership. Dependencies multiplied while accountability diluted.
• Weak ownership and responsibility: When several functions were engaged, no one actually “owned” results. Teams buck-passed rather than fixing blockers.  Escalations replaced empowered decision-making.
• Low visibility and gaps in governance: Leadership did not have trustworthy dashboards or measures. Dependencies, bottlenecks, and speed were opaque. Risk management was reactive, not proactive. Risks surfaced late, when options were already limited.
• Legacy delivery models: Old-fashioned, waterfall-like SDLC with much documentation and hand-offs. Loops of feedback took long, hindering responsiveness. Feedback latency directly impacted customer and regulatory responsiveness.
• Remote work stress: COVID-forcings dispersed work revealed shortcomings in teamwork and meeting discipline. Time-boxing and formal feedback did not exist. Distributed work exposed the absence of disciplined collaboration norms.

The net result was inevitable: delayed value delivery, disappointed stakeholders, ineffective collaboration, and a lack of responsiveness to customer or regulatory requirements. Delivery friction became the organization’s default state.

2. Strategic Objectives

Objectives were defined to reset ownership, speed, and trust. To turn this around, the client established precise strategic results:

• Increase certainty in execution by detailing ownership, minimizing dependency slowdowns, and harmonizing priorities.
• Create a “one-team” culture within business, IT, vendors, and compliance.
• Improve visibility and transparency through governance structures, dashboards, and quantifiable KPIs.
• Shorten feedback loops to drive greater adaptability and minimize rework.
• Establish cultural readiness for agility, with internal champions and communities of practice.

Each objective reinforced execution certainty and regulatory confidence.

Analysis: What We Did & Why It Mattered?

Transformation was approached as a system change, not isolated initiatives. NextAgile created and led a phased, structured Agile Transformational journey.

Phase 1: Agility Assessment & Pilot Initiatives

What We Did:

• Located and initiated pilot PODs (~50 members) to pilot agile ways of working in digital program initiatives. Pilots created psychological safety for experimentation.
• Delivered awareness and training to 80+ employees, including Scrum Masters, Product Owners, and stakeholders. Shared vocabulary reduced misalignment across roles.
• Scoped out transformation issues through baseline maturity surveys and role mapping. Data replaced assumptions in diagnosing change needs.

Why It Mattered?:

• Pilots facilitated safe experimentation while showcasing quick wins.
• Agile Training developed common language and awareness among leadership and teams.
• Early alignment generated legitimacy for scaling.

Credibility was built through visible delivery, not promises.

Phase 2: Framework & Process Design

What We Did?:

• Developed POD-based operating model, taking inspiration from the Spotify model for scaling. PODs collapsed silos into outcome-oriented teams.
• Established governance procedures for discovery, prioritization, risk management, and business metric alignment. Governance shifted from escalation to enablement.
• Implemented agile ceremonies with time-boxing and outcome-based agendas.Time-boxing enforced decision discipline.
• Deployed tooling (Jira dashboards, RAG reports, RAID logs, velocity charts) to build transparency. Dashboards converted conversations from opinion to evidence.
• Established an Agile Community of 70+ members and a 7-member Core Committee to spearhead transformation. Ownership of agility moved inside the organization.

Why It Mattered?:

• PODs eliminated inter-functional dependencies and built shared accountability.
• Governance and tooling allowed leadership visibility and data-driven decisions.
• Communities of practice planted internal champions and long-term ownership.

Structural alignment unlocked behavioral change.

Phase 3: Coaching, Execution & Scaling

What We Did?:

• Provided hands-on coaching across functions, bringing new ways of working to life in live digital programs. Coaching translated intent into execution habits.
• Set up regular showcases/demos to leadership to show value delivery. Visible progress reinforced leadership confidence.
• Implemented Scrum of Scrums and inter-POD forums for dependency management. Dependencies were managed proactively rather than reactively.
• Made Agility Health Assessments to track adoption and course-correct. Measurement enabled timely course correction.

Why It Mattered?:

• Coaching made adoption not only theoretical but practical, in real delivery contexts.
• Demonstrated built leadership trust and long-term buy-in.
• Health checks established feedback loops for ongoing improvement.

Adoption accelerated when leaders saw real outcomes.

Phase 4: Sustaining & Embedding Change

What We Did?:

• Built an “Agile Playbook” and Agile Ready Reckoner for role-based direction. Consistency was achieved without enforcing rigidity.
• Streamlined documentation – moving from heavy req docs to knowledge bases, outcome-based brainstorming, and quicker validation cycles. Compliance was preserved while speed improved.
• Improved meeting discipline and remote collaboration practices. Collaboration became intentional rather than habitual.
• Resolved role responsibilities and decision rights to avoid confusion. Decision latency dropped as ownership solidified.

Why It Mattered?:

• Playbooks and advice ensured consistency but not dogma.
• Lightweight documentation maintained compliance but enhanced flexibility.
• Cultural embedding minimized dependency on third-party consultants.

Sustainability replaced consultant dependency.

Solution & Outcomes

Outcomes validated the Agile transformation strategy. The change achieved structural and cultural transformation.

Outcome Area	What Changed	Impact / Value Delivered
Cross-functional Collaboration	PODs created across business, IT, vendors, compliance.	Improved handover speed, quicker decision-making, more ownership. Accountability moved closer to execution.
Transparency & Visibility	Dashboards, RAID logs, RAG reports, velocity & burndown charts used.	Leadership gained real-time visibility of risks, dependencies, and delivery status. Leadership shifted from reactive to anticipatory governance.
Faster Feedback & Responsiveness	Time-boxed ceremonies, showcases, and iterative delivery cycles.	Faster course correction, less rework, better stakeholder trust. Learning cycles shortened across programs.
Governance & Role Clarity	Agile governance committees, clarified RACI, documented responsibilities.	Less ambiguity, clearer ownership, better alignment between leadership & delivery. Decision paths became explicit and predictable.
Cultural Shift & Internal Capability	Agile Community (70+) and Core Committee (7) stood up; playbooks built.	Sustained agility practices, less reliance on external consultants. Agility became part of the organizational identity.

Key Success Factors

Patterns repeated across successful change initiatives.

• Pilot-first approach: Early wins established confidence and momentum. Early wins reduced resistance.
• POD model adoption: Cross-functional responsibility cut dependency bottlenecks. Cross-functional ownership minimized delays.
• Governance + tooling integration: Visibility and metrics gained leadership confidence.Data transparency anchored leadership trust.
• Communities of practice: Internal champions facilitated cultural change. Change champions accelerated adoption organically.
• Hands-on coaching: Hands-on guidance made agile stick in delivery situations. Practice embedded learning faster than training alone.

Risks, Challenges & Mitigation

Anticipating risks prevented regression.

Challenge	Risk	Mitigation
Resistance to change	Teams fall back on old ways; leadership makes Agile optional.	Awareness sessions, leadership showcases, rejoice in early wins. Change became socially reinforced.
Compliance vs agility trade-offs	Risk of under-documentation in regulated setup.	Lightweight but compliant documentation, outcome-based knowledge bases. Regulation and agility were treated as complementary.
Scaling PODs within enterprise	Alignment and communication overhead escalate.	Inter-POD forums, Scrum of Scrums, governance committees, playbooks. Coordination scaled without central bottlenecks.
Over-formalization of Spotify model	Risk of dogmatic adoption misfitting culture.	Context-specific Spotify elements, adapted with flexible frameworks. Context guided adoption, not frameworks.

Recommendations for Sustained Agility

Sustained agility requires deliberate reinforcement.

• Institutionalize coach-the-coach: Develop internal agile coaches to maintain adoption. Internal capability ensured continuity.
• Continuous agile maturity assessments: Utilize Agility Health Checks at regular intervals to improve adoption. Measurement guided evolution, not policing.
• Cross-POD communities of practice: Scale learning without losing autonomy across teams. Learning scales faster than mandates.
• Regulatory-aligned agility: Periodically adjust documentation practices to address compliance requirements. Compliance remained a design constraint, not a blocker.
• Leadership engagement: Maintain consistent showcases, dashboards, and leadership forums. Visibility kept momentum alive.
• Engineering & automation focus: Enhance CI/CD, testing automation for long-term agility. Technical excellence amplified business agility.

Conclusion

Agility in the insurance industry isn’t a nicety, it’s a matter of survival. This change demonstrated that even within a complicated, regulated landscape, insurers can establish speed, flexibility, and teamwork. Regulation does not preclude responsiveness.

Through the introduction of POD-based delivery, the injection of agile governance, increased visibility, and cultural readiness, NextAgile assisted this client in attaining execution certainty, greater ownership, and real-time delivery transparency. Structure and culture evolved together.

For insurance and other regulated industry leaders, the message is clear: begin small with impactful pilots, invest in cross-functional collaboration, and construct governance arrangements that increase visibility without inhibiting agility.

Agile transformation is not only about frameworks, it’s about people, culture, and long-term leadership commitment. With the right mindset, agility is not just a mode of working, but a competitive edge. Agility ultimately becomes a leadership discipline.

If your organisation is facing agile transformation challenges or you are struggling to bring cadence, rigor and discipline in your agile practices, NextAgile consulting can help you co‑create and implement a practical agile transformation roadmap.​ Do reach out to us at consult@nextagile.ai and we would be happy to explore more.