Celent Says

The Impending Insurance Architect Crisis

Benjamin Moreland
Insurance Experts' Forum, March 26, 2012

I was recently talking to a past colleague over lunch and he reminded me of a concern I had a couple of years ago that seems to be descending on insurers in the next 2-5 years. Architects are usually considered valuable internal resources within carriers (for good reason if they are good) along with PMs and BAs. Carriers have been outsourcing more and more development work over the last decade and reducing their internal developer footprint. For many insurers, this has proven a cost effective endeavor, albeit not without its bumps.

In addition, more modern vendor insurance solutions, namely core systems, data mastery (BI, analytics, DW/DM, ETL), case management, BPM, Rules, Portal, etc., have become much more configurable and have enabled business users to take on more of the development and maintenance of these systems. While this has again been viewed as forward progress by analysts and insurers, it again has reduced the IT developer footprint.

The typical career path for most architects in insurance has been developer, senior developer, technical lead, architect, solutions architect, enterprise architect. While different companies may have slightly different names for the stages in the architect career path, and while there have been some exceptions, for the most part, the pipeline for architects has traditionally been from their (or other insurer) development teams. As a developer, one would become very knowledgeable of a carrier's systems, especially with respect to legacy systems. While some insurers may have training programs, most of the learning and knowledge was acquired through project experience and shadowing architects on projects if they were tapped as future architects for the company. Architects for many insurers continue to be the first group assembled to resolve major crises and failures for insurers due to their deep knowledge of the systems and ability to diagnose problems.

Obviously, as the architect pipeline dwindles due to a much-reduced insurance developer pool, the number of available architects will likewise dwindle, but the need will not. Top level architects will be even more necessary going forward as insurers take advantage of Cloud and SaaS solutions as they mature. Knowledge of the impact of using a Cloud/SaaS solution on existing systems and analyzing the risks and benefits will fall squarely on the shoulders of the architects. While this development may make IBM, Oracle, Accenture, TCS, Cognizant and others smile since they have architects, the internal knowledge and insurance industry knowledge will be lacking (maybe not missing, but definitely lacking) and the cost will be high. This will create an opportunity for some one/group, I’m just not sure who at this time.

This blog has been reprinted with permission from Celent.

Benjamin Moreland is a senior analyst in Celent's insurance practice, and can be reached at bmoreland@celent.com.

Readers are encouraged to respond to Ben using the “Add Your Comments” box below.

The opinions posted in this blog do not necessarily reflect those of Insurance Networking News or SourceMedia.

Comments (0)

Be the first to comment on this post using the section below.

Add Your Comments...

Already Registered?

If you have already registered to Insurance Networking News, please use the form below to login. When completed you will immeditely be directed to post a comment.

Forgot your password?

Not Registered?

You must be registered to post a comment. Click here to register.

Blog Archive

The Other Auto Insurance Telematics Shoe Drops

Progressive's decision to charge Snapshot drivers more if their driving data indicates higher risk has started the industry down a road of data-driven adverse selection.

Core Transformation – Configuring in the Rain

The whole point of core transformation is that changes at the micro level can be used as a stimulus for changes at the macro level.

6 Ways to Develop a Productive IT-Business Dialog

Relationship management 101 for keeping IT and business on the same page.

Unified Digital Strategy: Succeeding in the Digital Revolution

A unified digital strategy recognizes that all business strategies and technologies touch the customer in some way and that a one-size-fits-all channel model is obsolete.

Agile and Continuous Delivery in a Regulated Environment

Just because a development team is doing continuous delivery or packaging releases into two-week sprints doesn’t mean that code is being moved to production.

Dealing with the COBOL Brain Drain

Documentation on aging systems often is akin to tribal knowledge, and the potential for things to go bump in the night increases as these environments face generational transition.