Delivering business value by evolving to straight-through processing

In the last 20 years, the way customers interact with businesses has changed considerably, moving from paper to the apparently all-pervasive electronic mechanisms of e-mail, Web, Facebook, Twitter and mobile.

In the last 20 years, the way that IT has designed systems to solve business problems has changed considerably, moving away from monolithic mainframes acting as a single version of the truth to all your business data, to a multitude of systems that have overlapping, and hopefully consistent, versions of the truth.

In the last 20 years, the way that customer support teams operate has changed considerably, with more requests, from more channels, for more products, supported on more systems with quicker turnaround.

In the last 20 years, the role of solutions such as AWD have also changed, moving from a document-centric world and routing-scanned documents around the organisation, to - in some cases - a paperless world with end-to-end digital fulfilment of a customer's request.

In this evolved and evolving customer, operational and technology landscape, many businesses are facing the challenge of transitioning from a world where they have had control of which business processes are available through each channel, to a world where customers want the flexibility to choose all business processes through all channels. Business sponsors now face the challenge of being able to satisfy customer demands, while reconciling the business desire to optimise the investment required to deliver and minimise the ongoing operational expense.

To achieve higher adoption rates for the customer self-service proposition, the marketing department needs all business processes available on the Web in order to be able to consistently signpost the channel in the product marketing material. The challenge this creates for IT is how to make business processes available for all products in both a timely and cost-effective manner, given the difficulties of integration with legacy business systems. IT also needs to try to balance perfect data capture for all product variations with the ease of use for the customer.

From a cost/benefit perspective, these competing demands lead to a heavily front-loaded IT delivery timescale and cost against the back-loaded potential benefit of reduced operational costs through high take-up of customer self-service. With the all-encompassing constraint of in-year return on investment, a business leader needs either to make a strategic leap of faith, or find a way to better align the delivery costs with business benefit. Business process management solutions such as AWD10 have also evolved, providing a way to better align the delivery costs associated with customer self-service with the customer experience and operational benefits derived from the increased take-up of customer self-service.

Like great architecture, an IT system is a child of its time. And while it is possible to change a building's facade, the structures used to form its backbone will remain fundamentally aligned with the period in which it was developed. In IT, these structures have historically focused on the constraints imposed by the availability (or economic limitation) of memory, storage, processing power, or network connectivity. While mainframe-based systems have many good qualities, 'ease of use' is rarely the phrase that falls off anybody's lips.

The organisational coping mechanism for complex user and systems interactions has been to train the customer services team on how to use the administration systems. This has led to days of training to understand the nuances of a particular system, and then more training to cope with the 5% of the policies or accounts administered by the other legacy systems in the business. The variation in implementing business rules over time creates the greatest challenge of achieving perfect data capture. The biggest variation takes place when product definitions or administration platforms go through a more radical step-change or replacement, rather than through evolutionary progression.

As the rules and variation by product or system increase in complexity, the more difficult it becomes to meet the ease of use as well as the perfect data capture criteria for customers. A business decision needs to be made on when to target perfect customer data capture in order to achieve the required reduction in servicing costs through automation or semi-automation of the process, versus which products or processes will most likely have lower customer take-up. This will therefore be a more pragmatic business investment, as it will have a lower upfront cost by using more human workflow and not trying to implement perfect data.

The multiple legacy policy or account administration systems an organisation has are commonly aligned with products sold for a specific period. Once sold in the retail banking, life, pensions, and wealth management arena, the products can have a life cycle that is upwards of 20 years. Migrating all of the policies or accounts from a 15-year-old system for a product no longer sold is unlikely to make economic sense. The IT systems of 15 years ago were only just beginning to become open for integration, therefore businesses are also faced with updating information on systems that are difficult to integrate through any mechanism but screen scrape.

This creates a challenge in that a system that can easily have between 10% and 30% of your book of business has the most complex user interface and a data structure that is not easy to use through modern Web services. AWD can help change the approach by not forcing businesses to integrate everything at one time, and as a result, change the cost/benefit equation to achieve self-service on the Web without having the incumbent costs associated with perfect data capture and complete integration.

For business processes that have either a high cost of integration or an unclear expected take-up, it would be more pragmatic to capture the request online and then use AWD to route the customer's request to a person to actually complete the process. As the customer demand for the process becomes clearer, and recorded in AWD monitoring at an activity level, it becomes easier to target specific integration opportunities that demonstrate the in-year return on investment, while leaving some parts of the process as tasks for people to pick up.

Being able to separate the challenge of achieving a perfect customer-based data capture from the integration costs of automated updates to all your existing systems affords businesses the opportunity to change cost/benefit on cross-over points.

As you explore the process challenges related to customer self-service, it is important to remember that AWD has been re-architected and now manages the new process problems along with the old ones you already know that it can manage.

For more information click here