The short version
Insurance has come to believe it cannot do technology-driven transformation. The belief is wrong, and it is expensive.
Almost every firm has a programme in its history that ran late, cost too much or delivered something nobody wanted. The lesson usually drawn is that insurance is different: too complex, too regulated, too bespoke. Meanwhile its leaders watch other industries rebuild themselves around technology, and feel left behind.
Insurance is not too complex to change. It has delivered change through separate teams with separate goals: business and technology, the firm and its supplier, the change team and the people who do the work. Without a shared goal they lose sight of the win-win, and become adversaries.
The firms that succeed change who does the work, and how. They build one team from the first day, with one shared goal: business and technology people together, led by someone accountable for the outcome. We have seen this deliver better outcomes during the programme itself, owned by the people who rely on it, and a platform whose value keeps growing after go-live.
Where the myth comes from
The myth rests on real experience, which is why it is hard to shift. A board that has funded two disappointing programmes is not being irrational when it doubts a third.
The mistake is in the lesson drawn. The usual explanations are that the market is unique, the products are bespoke and the legacy runs too deep. Each is partly true, and none is the reason. Other complex, regulated industries carry the same burdens and have still changed how they work.
The cost of the myth is caution. Firms lower their ambition, under-invest and hand the risk to a supplier. That makes the next disappointment more likely, and the myth stronger.
Why programmes fail, or deliver the wrong thing
Programmes fail in two ways. Some fail to deliver: they run late, cost more than planned or are stopped. Others deliver what was specified and still miss, because the business expected something else and only found out at the end.
The second kind is the more common and the less discussed. Nobody reports it as a failure, but the workarounds return, the old spreadsheets survive and the business case is never met.
One cause sits behind both: the teams involved do not share a goal.
A programme brings together business and technology, the firm and its supplier, and the change team and the people who do the work. Each arrives with a goal of its own. Before long, each feels that the others want something different. They lose sight of the win-win, and become adversaries.
It shows in three ways.
- The supplier owns the knowledge. The integrator builds, the client watches, and the understanding of how the platform works leaves with the contract.
- The business is consulted, not involved. Underwriters, brokers and claims handlers give requirements at the start and test at the end. In between, decisions are made without them.
- Assurance arrives without authority. An independent review tells the board the programme is in trouble. It does not change who is doing the work, so the trouble continues.
Assurance still matters. But a board that only hears what is wrong has paid for a diagnosis, and still needs someone to carry out the treatment.
A go-live that hides the problem
One insurer we have seen set out to replace its underwriting platform. Its IT department was measured on go-live and budget. Project managers were making technical decisions, and engineering discipline was missing.
There was no shared goal for what the new platform was meant to achieve, only a number of uncoordinated opinions. So the new platform came to mimic the old one. It was laid on top of the legacy system, and tied to it at every part of the underwriting lifecycle. The architecture and the roadmap could never have delivered the outcomes the business really wanted.
A go-live on those terms can be reported as a success. It hides the fact that the wider change, the kind that sticks, has not happened.
The fix began with a vision of what the platform needed to be, and with true engineering discipline. Delivery leadership was asked to focus on just that. The insurer then put three leaders in a box, each with one job.
- Product: build the right thing.
- Engineering and architecture: build it right.
- Delivery: build it fast.
The result was a new architecture, a new product vision and roadmap, and truly agile, cross-functional delivery, with underwriters and the wider users engaged throughout. The difference was night and day.
The team you need
The team is small, senior and mixed. Every role below is accountable for an outcome, not for a document.
| Role | What they are accountable for | Where they should come from |
|---|---|---|
| Executive sponsor | The business outcome, and removing what blocks it | The client's executive team |
| Delivery lead | The plan, the suppliers and the pace | Bind at first, then a client successor |
| Business owner for each value stream | What the platform must do, and adoption by their teams | The client: a respected underwriter, broker, claims or finance lead |
| Product manager | Turning what the business owner needs into a product that is built, released and adopted | Bind at first, while the discipline is built within the client |
| Architect | A design that holds together and can change later | Bind or the client, never the supplier alone |
| Data lead | Definitions, ownership and quality of the data the platform depends on | The client, with Bind support |
| Engineering and configuration team | Building, testing and releasing the platform | Client staff and partners, working as one team |
| Change lead | Skills, communication and new ways of working | The client, with Bind support |
Product management is a discipline in its own right, and many firms have not yet seen it done properly. The product manager is the business owner's hands: someone with deep competence in delivering technology product, who works for the business owner and with the engineers every day. A business owner without one is asked to do a specialist job in their spare time. We bring the discipline at first, and build it within the client, so that it stays when we leave.
Two rules matter more than the list. Client people hold the roles that must outlast the programme. And nobody is on the team part time in name only: a business owner with no time to give is a vacancy.
How the team works
How the team works decides whether the platform keeps its value. Four habits make the difference.
- Deliver in small, usable steps. Something real reaches users every few weeks, so problems surface early and confidence builds.
- Decide close to the work. The business owner and the delivery lead settle most questions the same day, without waiting for a committee.
- Measure outcomes, not activity. Progress is judged by what has changed for underwriters, brokers and claims handlers, such as time to quote or items rekeyed.
- Keep the team together. The people who build the platform stay to run and improve it, so knowledge accumulates and is not handed over and lost.
None of this needs new vocabulary. It is how cloud platforms are designed to be run: improved continuously, by a standing team, funded as a capability.
From delivery to a lasting operating model
The handover is designed at the start and happens in stages.
- Mobilise. Bind leads. We agree the outcome, name the team and fill the gaps with our own people and partners.
- Deliver the first value stream. Bind leads, with client successors working alongside each of our roles.
- Shift the lead. Client people take the lead roles. Bind moves to coaching and assurance.
- Run and improve. The client team owns the platform and its roadmap. Funding moves from a programme budget to a standing one.
- Step back. Bind leaves, or stays for a few days a month as a senior second opinion.
The test of success is simple: a year after go-live, the platform is better than on the day it launched, and the client team made it so.
Questions for the executive team
- What did we conclude from our last disappointing programme, and was it the right lesson?
- Who on our own staff could explain how the new platform works, without the supplier in the room?
- Which named business leaders are giving real time to the programme each week?
- When did something usable last reach the people who will use it?
- What happens to the team, and to the budget, on the day after go-live?
- If our independent reviewer says the programme is off track, who has the authority and the capacity to fix it?
How Bind helps
We work as an implementation partner: we build the team, lead it through the step change and leave you able to run it.
- Implementation partner: we build and lead the team that delivers the change, working to agreed outcomes.
- Operating model: the structure, funding and habits that keep a platform improving after go-live.
- Interim and fractional leadership: a CIO or senior technology leader embedded in your executive team while successors are developed.