Strategy is not a framework

Ask a room of insurance leaders whether their organization has a cloud, data or artificial intelligence strategy, and almost every hand goes up. Ask whether those strategies are delivering at the pace they expected, and the room goes quiet.

That gap points to a misunderstanding that derails more initiatives than any technology choice. We tend to treat strategy as if it were the framework for getting work done. It is not. Strategy is a stage within a framework. It sets direction and sequences priorities, but on its own, it does not build anything. The framework is execution, and strategy is the first step inside it.

We have seen this firsthand: a core longshore underwriting platform program scoped for 18 months, three years in, with no working product and the lead architect heading for the door. The strategy was sound. The slides were approved. What was missing was the framework to turn direction into sequenced, reliable delivery.

The reason this matters now is that the work has changed shape. Most organizations have already committed to the cloud or AI, and technology can support what they want to do. Progress stalls instead on three quieter problems: how to organize the work, how to sequence it and what to preserve along the way. The details vary by carrier, but that underlying challenge does not, and it is exactly what an execution framework solves. In practice it unfolds across three phases. They overlap, but the order matters.

Phase 1: Strategic planning

Execution starts with a focused form of strategy. Not an open-ended assessment, but a defined effort that produces decisions teams can act on quickly.

The first priority is governance alignment. Who owns the applications and data, what quality standards it must meet, and how it will support not just today's reporting but tomorrow's AI use cases.

From there, the work shifts to enablement planning. Which use cases come first, what outcomes they must deliver and how progress will be measured. This is where the stalled platform is recovered, by sequencing the highest-risk work first rather than the easiest, grounding each use case in measurable return-on-investment impact, and pairing a short 90-day plan with a longer roadmap. That early visibility is what sustains executive support and keeps the program moving.

Phase 2: Technical standards and automation

Once priorities are clear, the work moves to how it gets done, and this is where many organizations struggle. Without clear standards, cloud environments drift. Different teams adopt different patterns, and over time, the new environment starts to resemble the one it replaced.

The answer is to define standards once and automate them upfront. Infrastructure-as-code templates turn standards into something teams inherit rather than interpret. When a team provisions a new pipeline or application, security policies, access controls, cost tagging and monitoring are already in place. They start from a known baseline instead of designing from scratch.

This is also the quiet answer to a question many leaders get wrong: whether governance must come at the cost of speed. The opposite holds. The more you build standards and automation early, the faster the work scales, because governance and compliance travel inside the templates by default rather than resting on each team to get it right by hand.

Phase 3: Enablement and adoption at scale

In the engagements we have led, the final phase is where the framework is pressure tested. Teams begin adopting the platform and migrating workloads, and they do not do it evenly. Some need only advisory guidance, others hands-on support, and a few need the work led for them. The structure can vary. What cannot vary is consistency. Every team works from the same templates, standards, and governance model.

We worked with a group benefits operation processing tens of billions in annual premiums through fragmented stored procedures, plagued by deadlocks, and dependent on subject matter experts for nearly every run. What changed it was not a single tool. It was a modern design, the same standards and automation built into the path, and a deliberate handoff of ownership. Failures dropped, expert intervention fell away, and reliability improved several times over. The shift was structural, not heroic, and it shows how the phases connect. The standards set in phase two are what make adoption and ownership transfer clean here.

None of this requires a new strategy. It requires treating strategy as the opening move in a longer sequence, one where governance comes before scale, standards come before adoption, and meaning is preserved before anything is migrated.

The organizations that move well are not the ones with the boldest plans. They are the ones who understood, early, that the plan was never the framework. So, the next time the question is whether you have a strategy, it may be worth asking a sharper one. What is the execution framework that will carry it, and is it built yet?

© Entire contents copyright 2026 by InsuranceNewsNet.com Inc. All rights reserved. No part of this article may be reprinted without the expressed written consent from InsuranceNewsNet.com.

Justin Goff is the Director of Technical Delivery at Hylaine, a technology consulting firm that works with property/casualty, life/annuity, health and specialty insurers. Contact him at [email protected].