Lessons from Insurtech change projects

We were killing it for our clients... right up until we nearly crashed the entire project. Here's why... 👉 Tailored software project? ✅ Tight deadline? ✅ Multiple clients at the same time? ✅ A hyper-focused "client comes first" mindset? 100%! Unfortunately, that focus was SO intense that we nearly created a major bottleneck with another key stakeholder nearing capacity, with deadlines missed on an existing task that was essential for our client's launch feature, almost throwing the entire project off track! Missed dependencies nearly blew the whole scope wide open! Realizing the potential scope impact, I swiftly conducted a stakeholder evaluation. The findings revealed the strain on our key contractor. Lesson learned - it's not just about customers; all stakeholders matter! I reshaped our strategy, incorporating key stakeholder constraints into the plan. Communication became key – sharing customer requirements and aligning with stakeholders transformed our approach. 👍 The result? Successful project delivery achieved within budget and on time, with the following three lessons learned to share: 1️⃣ Stakeholder identification isn't a "do it once" task. Ongoing evaluation catches hiccups BEFORE they become disasters. 2️⃣ "Client Satisfaction" tunnel vision is a real "bad" risk. It's stakeholders (Plural, internal and external!) - each has requirements that make or break our outcomes. 3️⃣ Project Management IS dynamic communication. Sharing how client changes impacted others gave us room to re-plan and hit even those aggressive goals. Have you ever been so client-focused that you risked the whole project? Share your lessons learned (we all have some!) below 👇

Lessons from a Global Insurance Leader Leadership in insurance isn’t about having all the answers—it’s about navigating complexity, uncertainty, and transformation with clarity and purpose. One moment that shaped my perspective happened while leading a transformation initiative across multiple markets, including France and LatAm. Each region had vastly different regulatory pressures, tech maturity, and cultural expectations. What worked in Germany fell flat in Brazil. What seemed efficient in the UK felt abrupt in Japan. The breakthrough? I stopped trying to implement one solution globally—and started listening more deeply to each local team. We co-created region-specific strategies that aligned with broader goals but respected local nuance. Results improved. So did morale. That experience taught me: true leadership means adapting your approach while staying anchored in shared values. If you’ve led across borders, I’d love to hear—what’s one lesson global insurance leadership has taught you? #InsuranceLeadership #GlobalStrategy #InsuranceTransformation #CultureInBusiness #CommercialLines #EmergingMarkets #InsuranceInsights

A mid-sized carrier spent millions on tech modernization and still failed. Here’s why. They had the tech. They had the budget. What they didn’t have? Leadership alignment. No cultural shift. No accountability. No real change. The truth is, most insurance transformations don’t fail because of the software, they fail because the C-suite treats modernization like an IT project instead of what it truly is: a leadership reckoning. McKinsey says fewer than 30% of digital transformations succeed. In insurance? The failure rate’s even higher. Modernization is not a software rollout. It’s a leadership reckoning. If your C-suite isn’t unified, your culture isn’t change-ready, and no one owns outcomes… no amount of code will save you. 👉 Before your next big initiative, ask: are we ready to lead, or just ready to buy? #leadershipdevelopment #digitaltransformation #InsuranceInnovation #changemanagement

How we saved a client $15M/year by migrating their core claims system in-house (...and the surprising twist we discovered) Everyone loves a good cost-saving story, but this migration taught us a valuable lesson about expecting the unexpected. Here's what happened: 1️⃣ The Initial Plan — Client wanted to move their claims management system from a vendor data center to their private data center. Seemed like a straightforward infrastructure project. 2️⃣ The Reality Check — Quarter way in, we discovered this wasn't just about moving servers. We needed significant application rewrites and optimization. 3️⃣ The Challenge — Managing 11 different environments (most systems only have 3-4), while keeping every teams productive throughout the migration. What made this project unique: ✅ No team could afford downtime ✅ Each environment needed the same smooth transition as production ✅ Application rewrites became just as crucial as infrastructure changes The Results: • Completed the entire migration in 9 months • Achieved $15M annual cost savings • Gave client better development control • Improved application optimization Key Lesson: Even "simple" infrastructure projects can hide complex application challenges. Success comes from being adaptable and managing all moving pieces. And yes, we did this during COVID! 🎯