Consultants' Corner

How to Achieve the Speed Needed to Deliver

Dennis Sullivan
Insurance Experts' Forum, December 24, 2012

I’m sitting on a plane reviewing two projects, one looking at a new product launch and the other rolling out a new service delivery model. In both cases, implementation must be done sooner rather than later. Thinking about recent articles across a variety of industries, from fast food to financial services and even manufacturing, it seems that anything worthwhile has a component of speed attached to its success. Yes, there are other components, but apparently, speed is a critical one in many business situations.

Speed is everywhere: Speed to market, speed of delivery, speed of answer, speed of payment. When will the new processes be in place and how quickly can you get that system change installed so the agents can use it?

In business, quick action plays the dominant variable in many situations, and a cumbersome, bureaucratic approval or decision-making process can often thwart speed. It delays implementation and reduces momentum, and sometimes that means interest or, more importantly, funding. Yet, any experience dealing with change in the financial services industry teaches that speed is a critical component in all successful implementations. Speed in processing is equally important—minimizing the time between a customer request or transaction and the company’s delivery of service means a better, cheaper process and a happier customer.

I just completed a new application for a banking relationship with my individual health plan. I got an approved application with a new account number as soon as I logged back onto my e-mail—I was shocked. That’s a simple example, but their speed in approval and assigning an account number was almost instant. I’m impressed.

What stands in the way of speed? A lot of things can prevent speed of implementation. For example, does your review process require multiple sign-offs and multiple levels of approval before you can get started? To speed things up, are your funding and resource levels roughed out in advance so operations people can move from evaluation and redesign to execution without a hitch?

“How fast can we move once we have a plan?” should be one of the first questions answered by any implementation team. While you are racing off to your next business meeting, trying to catch that last commuter train, or speeding to get to your son’s Little League game, think about how you can build speed of delivery into your next project.

Speed can be the differentiator between success and failure. Make sure your current projects and implementations are positioned for speed as well as quality, cost, and functionality. It will make a big difference where it counts—market share and customer satisfaction.

Dennis Sullivan is chairman and CEO at The Nolan Company, a management consulting firm specializing in the insurance industry.

 Readers are encouraged to respond to Dennis at dennis_sullivan@renolan.com, or 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.