Northbridge Mutual: A Technology Refresh Labelled a Digital Strategy
Northbridge Mutual is a 140-year-old property insurer with $3.2bn in premiums, 2,400 staff and a policy administration system written in COBOL in 1987. Run activities consume 78% of the $210m annual IT budget, leaving $46m discretionary. Digital channels produce 9% of new business; the board has publicly committed to 30% within 24 months and to cutting claims cycle time from 14 days to 3. The CIO's plan, 'IT Strategy 2025-2027', is a technology refresh: migrate to cloud, replace the policy administration system, and launch a customer portal. The newly appointed chief digital officer argues this is not a digital strategy and that the firm has confused digitising existing processes with changing its value proposition. The CEO must settle the direction in six weeks, when the first $60m tranche goes to the board, and wants to know which executive is right and what the organisation should actually do.
1. Distinguish an IT strategy from a digital strategy, and judge whether the CIO's plan qualifies as either. Justify your judgement against the specific content of the plan.
Read the worked answer
An IT strategy explains how technology will be delivered and operated in support of a chosen direction: platforms, sourcing, architecture, service management, cost. A digital strategy explains how digital capability changes what the organisation offers, to whom, and how it captures value - new propositions, channels, revenue models, and the capabilities and operating model needed to sustain them. They are complementary, not hierarchical.
Applying that test: cloud migration and policy administration replacement are enablers. They are necessary - with 78% of budget consumed by run, the $46m discretionary pool cannot fund much else - but they do not say which customer segments Northbridge will prioritise, what proposition it offers brokers and policyholders, how 30% digital new business will actually be won, or how value is captured. A customer portal is a channel feature, not a value proposition. The CDO is therefore substantially right: this is an IT strategy with a digital aspiration attached.
The CIO is also partly right, and that matters. A digital strategy that ignores the COBOL platform and the run/change imbalance is unimplementable; a three-day claims promise cannot sit on a batch system whose data model encodes 14-day cycle times. The correct move is not to discard the plan but to re-frame it: state the strategic outcomes first (target segments, propositions, channel mix, claims promise), derive the enabling platform roadmap from them, and mark explicitly which elements are bets and which are foundations. The board should approve outcomes and tranche funding against evidence, not a three-year technology slate.
2. The CEO wants alignment in six weeks. Identify the stakeholder groups whose agreement is essential, what each needs from the strategy, and how you would structure the engagement to reach a decision in that window.
Read the worked answer
Essential stakeholders and their distinct needs: the board (capital, public-commitment credibility, risk appetite); the CEO (a direction, and cover for reversing or re-scoping the 30% pledge if the evidence does not support it); the CFO (a benefits case, the run/change ratio, cost-to-serve by channel); the CIO (feasibility and sequencing, plus protection from scope creep); the CDO (proposition and segment choices); underwriting and pricing (risk selection consequences of digital straight-through); distribution, since the book is broker-dominated and a direct digital push is a channel-conflict decision, not a marketing one; claims operations (the 3-day promise must be designed, not announced); and risk/compliance, which owns cloud outsourcing notification and operational resilience evidence.
Six-week structure: week 1, evidence review and outcome framing with the executive team - outcomes, not a plan document. Weeks 2-3, structured interviews plus two working sessions to generate and test segment and proposition hypotheses. Week 4, affordability and sequencing stress test with the CFO and CIO. Week 5, board pre-read and a decision rehearsal with the CEO. Week 6, board decision on strategic outcomes and first tranche.
Two disciplines make this work: a single one-page strategy summary so parallel documents cannot compete, and an explicit stop-list. Most alignment failures are caused by refusing to say what will no longer be funded.
3. Replacing the policy administration system will absorb most discretionary funding for 18 months. Recommend how Northbridge should sequence the first 12 months so digital progress is visible without destabilising the core.
Read the worked answer
The obvious plan - run the platform replacement, the portal and the 30% digital target simultaneously on $46m - delivers none of them. Sequencing should protect the core programme while creating visible, low-regret digital movement.
First, ring-fence the policy administration programme with a fixed budget, a named business owner and a hard no-new-scope rule, and run it as a product with claims and underwriting embedded rather than as an IT delivery.
Second, carve out a protected slice of discretionary spend - roughly 15-20%, so $7-9m - for two or three thin-slice bets deliberately outside the platform's critical path: straight-through triage for one low-complexity peril, and digital quote-and-bind for one broker segment. These generate learning and evidence for the next funding round.
Third, attack the real constraint: 78% run spend. A five-point reduction releases about $10m a year of digital capacity and is a strategic lever, not a cost exercise.
Fourth, build an API layer so channel work is decoupled from the core and is not blocked by a two-year migration.
Finally, measure leading indicators - quote-to-bind drop-off, claims touches per case, cost per policy, broker adoption - rather than channel share alone, and set formal stage gates at 6 and 12 months. The risk being managed is portfolio over-extension, not lack of ambition.