- Forrester Councils
- Councils Overview
- log in
Posted by Jost Hoppermann on February 18, 2010
The mobile channel is increasingly relevant in business strategies, application architectures and applications of financial services firms. Consequently, we are all aware that the headline represents a strong exaggeration. So, why this statement? Is there any substance in it that application architects, application developers, and enterprise architects need to consider? Interactions with a number of banks indicate that the answer is yes. I have recently talked to a number of executives on the IT and business side of banks about Forrester’s research on banking and banking architecture of the future – often with the report Financial Services Of The Future: Collaborative Competition Will Be The Norm (one of a series of reports) being the anchor point. One of my key questions to the banking executives: “How do you use channels today and how do you plan to use them in the future?”
One of these executives is Alex Twigg, the then Head of Delivery & Operations UBank (he got promoted a few days ago). A division of National Australia Bank, Ubank (ubank.com.au) is an Internet only bank. It started in November 2008 with a single product, term-deposits, but soon added a savings product and is working on additional products. Today, UBank has already become one of the most successful deposits institutions in Australia. In addition to a competitive cost structure and offering customers online account opening, UBank also offers customers unique ways to interact with the bank including:
The bottom line:UBank continued success depends upon channel innovations.
Conspicuously absent from UBank’s channel interaction is mobile. When I asked Alex about this, he told me that UBank may come up with a mobile banking solution in the future, but for now, he has a significant question mark over investing heavily in the mobile channel. This statement surprised me given the innovative culture at UBank and the fact that there are already mobile-only banks, for example Jibun Bank in Japan. Alex explained his reasoning. He believes that rapid device evolution and bandwidth availability will quickly eliminate the need for device specific platforms resulting in the convergence of the mobile and internet channels, so the mobile channel can be used as if it were just a flavor of the Internet channel on top of different network layers. Therefore, his focus is on the challenges to deliver new products and solutions – not on a single channel (the mobile channel) which is good for a variety of apps for different classes of smart phones including the iPhone as well as other mobile approaches such as phone browsers on top of UMTS and even WAP (yes, WAP is still out there).
Channel Innovation Requires A Channel Agnostic Architecture
The core of Alex’ statement is that banks need seamless delivery of products and services across a variety of channels. The business should not be put in a situation to care about the technology capabilities or deficiencies of a given channel when deciding on product/channel alignment. Multichannel applications and architecture today need to take care of the different behavior of channels to provide a basis for the full emergence of ubiquitous banking (Intelligent Devices Will Drive Ubiquitous Banking). Bank executives involved in application development and delivery as well as architecture need to ensure that their applications don’t support any individual channel, but consist of a layered approach isolating channels and business functionality. App dev and delivery staff needs to:
With this approach, a bank’s business decisions will become independent from channels that may or may not be used for a given product or service: The mobile channel won’t exist anymore. As soon as we will see more convergence of channel technology, the need for this kind of multichannel approach will become smaller and smaller.
Lead BT Transformation
Develop customer-obsessed strategies to drive growth »
Forrester's CX Index
Predict how actions to improve CX will affect revenue performance.
Measure the customer experiences that matter most »