New Year, New Policy Administration Solution – 2017 Revisit

Written by Anne Kraske on January 10th, 2017

In 2015, we put out a blog with a similar title to get you thinking about some key considerations for a “resolution” to retire your outdated legacy policy administration solution and to replace it with a shiny, modern solution.

While all that advice is still pertinent (and can be found here), 2017 brings more for you to consider and to pay attention to when contemplating a replacement policy administration solution.

1. It’s not always a legacy solution that needs replacement

Wait…what?!   Yup, it doesn’t get a lot of press because there are many pressures to try to cover up or ride out failing implementations, but sometimes an initial replacement solution doesn’t work out. Don’t be hasty (there are always challenges to work through in an implementation), but be careful not to throw good money after bad. Go back and look at the 2015 blog. Does your problematic solution have those features? If not, it may be time to replace it with a solution that does. If you are in this situation, look for a vendor willing to demonstrate how they can quickly catch up to your product need and surmount the issues the problematic solution could not.

2. Customizations in data, not code

In 2015, we talked about “no-code” configuration. For 2017, we want to make it extremely clear what we mean: configured product customizations (rules such as question, coverage, and page applicability; answer options; service call triggers, payload, and integrations; etc.) should be stored in data, not written in code. Why is this valuable to you? A new release of your vendor’s software should require no re-work of your product customizations. If your customizations are in data, such as they are with Adaptik, they don’t. If they are in code –especially extensions of the vendor’s code, you are likely in for a lot of rework with every release.

3. Small implementation team footprint

Bigger definitely means a bigger (sometimes astronomical) bill, but does not correlate to a better implementation or solution. Look for a solution vendor that does not require a large team. The rates for the smaller team may be higher, but the overall price-tag and outcome will likely be better.

4. Good partner

Look past the marketing and into the actual customer experiences. Is the vendor you’re considering one that customers note is a “great partner”? A great partner can make you happy and successful with your choice even through inevitable challenges.

May your New Year be happy and fruitful and should you embark on a replacement project for your policy administration solution, may these blogs help you be successful!