We are currently QA (Quality and Assurance) and testing processes for our new PI version of SCOUT and an implementation for a new Carrier client.  It's a somewhat complicated process and absolutely crucial for the success and adoption of the software.  I just came across an article that does a pretty good job of explaining what it takes to implement new software in an insurance environment.

 Highlights:

Step 1: Establish priorities. Identify the critical, most used, end-to-end business transaction pathways within the enterprise portfolio for the application.

Step 2: Develop the Architecture. Create an automation test architecture using the appropriate functional test tools. Make sure that the architecture supports the automated test script processing, while minimizing test script coding.

Step 3: Develop Test Case Templates. The templates are used for automating the application. Identify the key fields to vary in using data parameterization.

Step 4: Move the Data. Identify a full data migration solution from the legacy system, based on the necessary elements of the new application..

Step 5: Execute. Build and automate as many of the end-to-end test transactions for the application as possible, within the iteration’s user acceptance testing (UAT) schedules. Then, execute the test scripts (automated test cases) during UAT, report defects, and maintain a testing status dashboard for project status results.

This is a pretty good road map, but there are always exceptions depending on the environment.  We strive to set expectations with every customer and make the transition as smooth as possible.

Check out the icons on these buttons in the 2011 Ford Explorer.  Any idea what they are for?

I came across this article from Insurance and Technology that describes, "UIs need to be crafted not only to meet the task at hand but also the type of user." Really?

QUOTE: In developing the various UIs within its product set, StoneRiver has identified three different personas:

• the internal insurance professional or administrator;
• the external customer, including agents; and
• the systems administrator.

Aren't all of these just people and aren't they all using the same application?

QUOTE: For example, internal insurance professionals understand the concepts and terminology of insurance, Griffin explains. They are looking for speed and efficiency and can deal with more complexity.

So insurance "professionals" understand the insurance we buy better than we do or are superior in their processing capabilities?  Complexity = speed and efficiency?

Now, we didn't hire a Human Factor Specialist to design our UI, but I also don't think we need to complicate things with 3 (or more) different UIs.  Sure, different users have access to different screens and information in the application, but do they each need a custom design?   I'm not trying to pile on the company mentioned in this article and truth be told, I'm the litmus test for new features and layouts for SCOUT.  If I can't figure out how to use it we go back to the drawing board. 

Required training is minimal, barriers to entry low, adoption rates high.  We promise not to make our client's lives more complicatied.  Quite the opposite.

Managing state license information for vendor companies and their employees is a full-time job for some people at our Carrier clients.  To lighten these folk's workload and make their lives easier we've designed portals for vendors to upload license information themselves.  Information includes Investigation licenses for the company, each employee and in some cases our clients want to track driver's license, vehicle registration and insurance information and expiration dates.  This format has been a great help to our Carrier clients and we've tuned the application over the past year.

Recently, we've been talking to some large PI companies that have to manage company and hundreds of employee licenses in several states.  They to (may) employ one person who's full-time job is managing renewals, new investigators, and other compliance issues related to state licensing.  So we are taking components from our Vendor Management Platform and applying them to a "License Management" module for our new release.  I've included a mock-up below.

Feedback is encouraged.

We had another great demo today with a mid-sized Investigation company out of NY.  Dave and I personally went though the demo with the client in about 1/2 hr via WebEx.  We can't wait for the new release due out late Spring/Early Summer and to have demo videos available online and on demand.  It's not that we don't like talking to potential customers, it's just that we want to talk to MORE potential users.  Investigators are busy and keep odd hours and getting them to commit to a scheduled demo is very difficult.  So we'll do what we do best and make their lives easier and let them experience SCOUT at their convenience. 

COMING SOON to the SCOUT website:

1) Demo Videos on demand

2) Tiered pricing information

3) 15 day FREE TRIAL

4) Sign up and use capabilities