Bank Automation News

No products in the cart.

Subscribe
  • News
  • Data
  • Transactions
  • Events
    • Bank Automation Summit
    • Apply to Speak
    • Apply to Demo
  • Podcast
  • WEBINARS
    • On-Demand Webinar: Emerging fintechs: New technologies you need to know now
    • Webinar Library
Log In
No Result
View All Result
  • AI
  • Business Banking
  • Core
  • Cloud
  • Payments
  • Retail Banking
  • Risk & Security
Bank Automation News
  • News
  • Data
  • Transactions
  • Events
    • Bank Automation Summit
    • Apply to Speak
    • Apply to Demo
  • Podcast
  • WEBINARS
    • On-Demand Webinar: Emerging fintechs: New technologies you need to know now
    • Webinar Library
BAN PLUS
Log In
No Result
View All Result
Bank Automation News
No Result
View All Result

The 5 Myths Preventing Bank Fintech Innovation

Simon TaylorbySimon Taylor
May 4, 2015
in Archive
Reading Time: 8 mins read
0
Share on Facebook

Banks are now big complex machines that risk losing sight of why the existed in the first place.  Banks protect your money (take deposits) and in return are able to lend some of that to help the economy grow. Somehow we ended up with organisations employing 100s of thousands of people & riddled with complexity.

Time is passing these organisations by in their current form.  What should really worry you if you’re running a bank is how customers are trending to not recommend you and want to leave.

retention

I read a great quote from Seth Godin this morning:

“…Jefferson, Edison, Ford… most of these radicals would not recognize the institutions that have been built over time.

The question each of us has to answer about the institution we care about is: Does this place exist to maintain and perpetuate the status quo, or am I here to do the work that the radical founder had in mind when we started?

First principles. The quest for growth, or for change, or for justice. The ability, perhaps the desire, to seek out things that feel risky.

All of us are part of organizations that were started by outliers, by radicals, by people who cared more about making a difference than fitting in.” – Seth Godin

There are 5 Myths Preventing Banks from embracing the Fintech revolution

I put it to you that there are a set of beliefs about banking that is holding back the entire industry.  Banks, consultants and their vendors…

  1. We Are Already Very Innovative
  2. We Can’t Use “new” Technology Because it’s Not Secure
  3. Our Future is an “Omni Channel” Strategy
  4. Regulation Prevents Innovation
  5. We Will Become a Tech Company

Let’s challenge some of these beliefs…

Myth 1: We Are Already Very Innovative

For some time bank efforts in innovation have been met with skepticism. David Brear pointed out recently that if you look at the headlines banks are all supposedly spending $1Bn+ each on technology and innovation.

For all of that money there isn’t much to show for it! We hear lots about a mobile app or a venture fund.  Yet when it comes to real measures of success, there is silence. Sure they’ll talk about how many users they have, but how engaged are those users? How profitable?

CapGemeni reported recently that banks digital products aren’t delivering cost savings and as an experience are well below customers expectations.  Fintech disruptors ready to hoover up customers with far better experiences.

In the start-up world there are two key metrics

  1. MAU (sometimes DAU) “Monthly Active Users”,
  2. ARPU “Average Revenue Per User”.

I’ve seen many mobile developments across the European banking sector since 2008 and in that near decade, never once heard these terms inside a bank or it’s vendor community.

Banks desperately want to appear innovative, but getting anything innovative done is very hard for them. As I pointed out in the previous post – Innovation by Committee is not effective. The open secret is that mobile services are table stakes, but to me they’re such a wasted opportunity. Brett King talks about Moven Bank’s mobile only customer acquisition being less than 10% the cost of a bank branch customer acquisition.  Yet banks cannot deliver on the experience customers want in these channels.

Banks are spending billions, not taking cost out and missing consumer expectations

  • What if banks had a mobile only product like Moven?
  • What could they learn about that experience?

Myth 2: We can’t use “new” technology because it’s not secure

Let’s be clear. Security is paramount in banking. The problem here is the perception of security vs the reality. Let’s say you try to
implement Apple TouchID so people can login with their finger print (purely hypothetical – and to prove a point)

Typical security consultant responses include “but Apple devices can be jailbroken” and “the finger prints aren’t stored securely” from people paid £600 a day to point out risks but not offer solutions. (This isn’t exclusively a security consultant concern no doubt there were an army of other risk teams who chimed in too). Raising an objection is seen as “job done” instead of finding a way to make the better experience work.

security

These objections typically take a possibility and turn that into a probability. Confusing these two is criminal.

Many years ago I once heard an executive for a European bank say “but what does analytics about product usage give me that I don’t already have? – It gives you evidence. Evidence you can use to make a decision. The lack of evidence not only prevents you from moving to TouchID, if you don’t accept that the CAP reader has to stay then your sponsor has to sign up to a £10M risk.

 

When £10M is more than the cost of the entire project by 10x, the security objections mean there’s no way to launch the product, because of a hypothetical paper based exercise.

… rinse and repeat – for every innovation.

Without evidence there is no way to see what small things can make a huge difference to product success. Amazon famously discovered a 0.1% page load time improvement had a significant impact on sales. Having used just about every digital banking product, I wonder how much of that thinking is being applied?

  • What if banks used A/B testing here?
  • Could they take a segment of customers and trial something, and then let the evidence decide if change is required?
  • How could vendors support this?
  • How could the consultants promote this idea?

Myth 3: Our Future is an “Omni Channel” Strategy

It’s well known bank systems are old and resemble spaghetti.

You can’t give a great customer experience on mobile if your core system can’t keep up with the mobile app. This is why innovators are able to offer a better experience. They’re starting from scratch and solving a need end to end.

Over the past decade adding an online “channel” has sort of worked. Online banking, mobile banking were delivered initial results. This lead to a perception that when innovation comes, banks should react by creating a new channel above the core service. Yet as the CapGemeni report states – this game is up.  Digital Channel use has stagnated, and is not delivering cost reductions or better experiences.  It is failing.

Innovation isn’t something you do at the edges. It start’s with the key platforms and works out.

Thinking in channels, suggests the customer experience can be carved off from the core product experience. They are the same thing. It’s the careful union of the core and the digital front end that creates an experience. The term Omni Channel would suggest more investment in the front ends, mobile apps etc.

Problem: That’s creating more spaghetti. Creating more complexity. Creating more cost. Creating a disjointed experience.

Re-architecting the core not only gives your front end so much more capability, it also unleashes innovations that have promised so much but delivered so little like “Big Data”.

  • What will it take to get bankers to accept that the core has to change?
  • Can the amounts bank spend on “tech” be put to better use?

Myth 4: Regulation Prevents Innovation

Banks have had a kicking from regulators in recent years. Approaching the regulator is a tricky thing to do for a bank, the
regulator will tell a bank what the rules are but not how to implement them.

When faced with a spiders web of different regulations the banks react by employing a small army of specialists and ensuring all those
specialists give advice. That advice is then logged in giant spreadsheets to be tracked and traced. Often this means when a new regulation comes out that is designed to support a particular type of customer (small businesses, innovators, money service businesses – take your pick), it actually has the opposite effect. The customer type becomes a “hot topic” and anything in that sector goes under the microscope and is poured over by specialists tracking things on spreadsheets.

The same happens with new products. Banks look at every new idea that crosses their radar as if it’s rolling out a new current account product to the entire customer base. The irony here is it’s not the regulation that’s prevented the innovation (although the lack of guidance from regulators about “how to implement” doesn’t help), it’s how banks react to it. With the only tool they have.

spreadsheets

The irony is forcing everyone to do mandatory training, having committees, councils, Excos, Manco’s and Steerco’s hasn’t actually fixed many of the core problems they’re intended to fix. They make banks feel more effective and provide spreadsheets for the regulators to look at…

The definition of insanity is doing the same thing you did yesterday and expecting a different result.

I believe there is a recognition of this issue in some corners of the industry and regulator community, and some ideas about how to change it. If banks are going to innovate though, they’re going to have to internalise the idea of experimentation.

  • What if banks took ideas like A/B testing of new products to the regulator?
  • What if different ways of bringing new products to market were trialled in small / low risk areas?

Myth 5: We Will Become a Tech Company

This is a noble aim, but at the risk of going against previous advice, perhaps it’s better to embrace Tech in ways that focus on the core of
what banks are good at: banking. If any Tech company spent $1Bn on tech and had so little to show for it, investors would revolt.
Fortunately, banking is a profitable business if you have some scale.   Therefore the question is, how do you maximise that investment to benefit what already bank does?

My own view is banks should focus on being banks but come
into this century digitally.

I’ve been a proponent for a long time that banks need to focus on making their core platforms as easy to integrate with as possible and less on “bundling” value. The fear here is the 1990s thinking that being a “wholesale bank” is the same as being commoditised and will erode revenue and margins. The inverse is also true, this is the path to volume and precisely how banks can take advantage of the wave of Fintech Innovators.  Fintech innovators will migrate to the easiest to use bank platform.

BBVA and Credit Agricole have app stores now, but these are just scratching the surface of what’s possible. The bank as a platform allows the bank to focus on what’s really important: managing the liquidity. Innovators will do the front end far better than a bank can ever and take the banking sectors products to new markets and new verticals.

The icing on the cake of thinking as a wholesale platform business is that your retail (both to consumer and corporate) parts of the bank would have a much more flexible set of choices for how to build out the customer experience. Fintech is a giant opportunity not being taken advantage of. The fintech disruptors are now doing the individual products better than the banks can. I think this is a good thing. They all ultimately need a bank behind the scenes, but are able to offer better, more targeted customer experiences.

The game is attracting deposits and liquidity.  Learn from tech companies, but aspire to be a great bank.

  • What if banks focussed on their core and stopped trying to be Apple?
  • Is volume and opening up to 3rd party innovation a strategy banks are missing?

Take Aways

  • Banks aren’t doing innovation right but they could if they just focus on what they’re good at
  • Challenging for usability has to come from the very top. It’s a board level issue.
  • There is no excuse, core platform investment is now mission critical.
  • Experimentation will help manage new customer segments
  • But don’t try to be a tech company – be a bank that embraces some good tech company ideas

I speculate that by investing in the core, many of the usability and security concerns would be eased. The key here is culture. Culture eats strategy. Knowing when to not use miles of spreadsheets and when to experiment is what will unblock the user experience woes they currently suffer from.

What are your thoughts?

– See more at: http://www.sytaylor.net/2015/05/04/the-5-myths-preventing-bank-fintech-innovation/#sthash.wbQ5zdCo.dpuf

Tags: innovationIT
Previous Post

My LendingTree Nears 1 Million Users, Launches iOS App

Next Post

Paytm is finally turning the mobile wallet dream into reality – in India

Related Posts

Image by CanStock
Archive

Blend Labs integrates acquisition’s mortgage automation process

August 20, 2021
Photo by CanStock
Archive

Chilean fintech looks for slice of giant money transfers market

August 5, 2021
Image by CanStock
Risk & Security

Listen: How banks can protect themselves against cybersecurity risks

August 3, 2021
Next Post

Paytm is finally turning the mobile wallet dream into reality – in India

Please login to join discussion

Stay Informed with Our Newsletters

EMERGING FINTECH DIRECTORY

Emerging Fintech Directory

The Buzz Podcast

RETAIL BANKING

Huntington Bank’s new branch in Spartanburg

Huntington Bank resolves outage

May 7, 2025
bank

Barclays, Banco Santander, Lloyds plan product expansion

May 5, 2025
satisfactiin

Online banks lead FIs in customer satisfaction

May 2, 2025

SPONSORED

Just Released! 2025 Strategy Benchmark

May 1, 2025

Leverage Treasury Management to Turn Fraud Prevention Into a Strategic, Revenue-Generating Opportunity

April 1, 2025

A growth mindset in banking requires AI

March 27, 2025
  • About Us
  • Help Center
  • Contact Us
  • Privacy Terms
  • ADA Compliance
  • Advertise

 Manage Cookie Consent

Connect

twitter linkedin podcast podcast podcast
© 2025 Royal Media
No Result
View All Result
  • NEWS
    • All News
    • AI
    • Business Banking
    • Core
    • Cloud
    • Payments
    • Retail Banking
    • Risk & Security
  • DATA
  • TRANSACTIONS
  • EVENTS
    • Bank Automation Summit
  • PODCAST
  • WEBINARS
    • Upcoming Webinar
    • Webinar Library
  • SUBSCRIBE
  • Log In / Account

Welcome Back!

Login to your account below

Forgotten Password?

Retrieve your password

Please enter your username or email address to reset your password.

Log In
No Result
View All Result
  • NEWS
    • All News
    • AI
    • Business Banking
    • Core
    • Cloud
    • Payments
    • Retail Banking
    • Risk & Security
  • DATA
  • TRANSACTIONS
  • EVENTS
    • Bank Automation Summit
  • PODCAST
  • WEBINARS
    • Upcoming Webinar
    • Webinar Library
  • SUBSCRIBE
  • Log In / Account

THIS WEBSITE USES COOKIES

We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “I CONSENT”, you consent to the use of ALL the cookies.

Cookie settingsI CONSENT

Review our Cookie Policies
.
Manage Cookie Consent

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
CookieDurationDescription
__cfruidsessionCloudflare sets this cookie to identify trusted web traffic.
__RequestVerificationTokensessionThis cookie is set by web application built in ASP.NET MVC Technologies. This is an anti-forgery cookie used for preventing cross site request forgery attacks.
_abck1 yearThis cookie is used to detect and defend when a client attempt to replay a cookie.This cookie manages the interaction with online bots and takes the appropriate actions.
34f6831605sessionGeneral purpose platform session cookie, used by sites written in JSP. Usually used to maintain an anonymous user session by the server.
a64cedc0bfsessionGeneral purpose platform session cookie, used by sites written in JSP. Usually used to maintain an anonymous user session by the server.
ak_bmsc2 hoursThis cookie is used by Akamai to optimize site security by distinguishing between humans and bots
ARRAffinitysessionARRAffinity cookie is set by Azure app service, and allows the service to choose the right instance established by a user to deliver subsequent requests made by that user.
ARRAffinitySameSitesessionThis cookie is set by Windows Azure cloud, and is used for load balancing to make sure the visitor page requests are routed to the same server in any browsing session.
AWSELBsessionAssociated with Amazon Web Services and created by Elastic Load Balancing, AWSELB cookie is used to manage sticky sessions across production servers.
bm_sz4 hoursThis cookie is set by the provider Akamai Bot Manager. This cookie is used to manage the interaction with the online bots. It also helps in fraud preventions
cf_ob_infopastThe cf_ob_info cookie is set by Cloudflare to provide information on HTTP Status Code returned by the origin web server, the Ray ID of the original failed request and the data center serving the traffic.
cf_use_obpastCloudflare sets this cookie to improve page load times and to disallow any security restrictions based on the visitor's IP address.
CONCRETE5sessionThis cookie is set by the provider Concrete5 web content management system. This is a necessary cookie used for maintaining the user session between pages.
connect.sid1 monthThis cookie is used for authentication and for secure log-in. It registers the log-in information.
cookielawinfo-checkbox-advertisement1 yearSet by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .
cookielawinfo-checkbox-analytics11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional11 monthsThe cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
cookiesession11 yearThis cookie is set by the Fortinet firewall. This cookie is used for protecting the website from abuse.
crmcsrsessionGeneral purpose platform session cookie, used by sites written in JSP. Usually used to maintain an anonymous user session by the server.
ep20130 minutesThis cookie is set by Wufoo for load balancing, site traffic and preventing site abuse.
JSESSIONIDsessionThe JSESSIONID cookie is used by New Relic to store a session identifier so that New Relic can monitor session counts for an application.
LS_CSRF_TOKENsessionCloudflare sets this cookie to track users’ activities across multiple websites. It expires once the browser is closed.
PHPSESSIDsessionThis cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookies and is deleted when all the browser windows are closed.
sxa_sitesessionThis cookie is used to identify the webiste visitor's session state across page requests on server.
ts3 yearsPayPal sets this cookie to enable secure transactions through PayPal.
ts_c3 yearsPayPal sets this cookie to make safe payments through PayPal.
viewed_cookie_policy11 monthsThe cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
wordpress_test_cookiesessionThis cookie is used to check if the cookies are enabled on the users' browser.
Functional
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
CookieDurationDescription
__cf_bm30 minutesThis cookie, set by Cloudflare, is used to support Cloudflare Bot Management.
_zcsr_tmpsessionZoho sets this cookie for the login function on the website.
663a60c55dsessionThis cookie is related to Zoho (Customer Service) Chatbox
bcookie2 yearsLinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID.
bscookie2 yearsLinkedIn sets this cookie to store performed actions on the website.
e188bc05fesessionThis cookie is set in relation to Zoho Campaigns
geosessionThis cookie is used for identifying the geographical location by country of the user.
iamcsrsessionZoho (Customer Support) sets this cookie and is used for tracking visitors (for performance purposes)
langsessionLinkedIn sets this cookie to remember a user's language setting.
languagesessionThis cookie is used to store the language preference of the user.
lidc1 dayLinkedIn sets the lidc cookie to facilitate data center selection.
optimizelyEndUserId1 yearOptimizely uses this cookie to store a visitor's unique identifier which is a combination of a timestamp and a random number. Different variations of web parts are shown to users that optimizes the website's user experience.
tableau_localesessionTableau uses this cookie to determine the preferred language and country-setting of the visitor - This allows the website to show content most relevant to that region and language.
UserMatchHistory1 monthLinkedIn sets this cookie for LinkedIn Ads ID syncing.
Performance
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
CookieDurationDescription
AWSELBCORS20 minutesThis cookie is used by Elastic Load Balancing from Amazon Web Services to effectively balance load on the servers.
Analytics
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
CookieDurationDescription
__gads1 year 24 daysThe __gads cookie, set by Google, is stored under DoubleClick domain and tracks the number of times users see an advert, measures the success of the campaign and calculates its revenue. This cookie can only be read from the domain they are set on and will not track any data while browsing through other sites.
_ga2 yearsThe _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.
_gcl_au3 monthsProvided by Google Tag Manager to experiment advertisement efficiency of websites using their services.
_gid1 dayInstalled by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.
ajs_anonymous_idneverThis cookie is set by Segment to count the number of people who visit a certain site by tracking if they have visited before.
ajs_group_idneverThis cookie is set by Segment to track visitor usage and events within the website.
ajs_user_idneverThis cookie is set by Segment to help track visitor usage, events, target marketing, and also measure application performance and stability.
browser_id5 yearsThis cookie is used for identifying the visitor browser on re-visit to the website.
CONSENT2 yearsYouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.
sid1 yearThe sid cookie contains digitally signed and encrypted records of a user’s Google account ID and most recent sign-in time.
uid1 yearThis is a Google UserID cookie that tracks users across various website segments.
vuid2 yearsVimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website.
WMF-Last-Access1 month 21 hours 5 minutesThis cookie is used to calculate unique devices accessing the website.
Advertisement
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
CookieDurationDescription
_dc_gtm_UA-1038974-41 minuteUsed to help identify the visitors by either age, gender, or interests by DoubleClick - Google Tag Manager.
_fbp3 monthsThis cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website.
_pxhdpastUsed by Zoominfo to enhance customer data.
fr3 monthsFacebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin.
IDE1 year 24 daysGoogle DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile.
test_cookie15 minutesThe test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies.
VISITOR_INFO1_LIVE5 months 27 daysA cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.
YSCsessionYSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.
yt-remote-connected-devicesneverYouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
yt-remote-device-idneverYouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
yt.innertube::nextIdneverThis cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen.
yt.innertube::requestsneverThis cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen.
Others
Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.
CookieDurationDescription
049fc2ef5beb27056b07d9e4c4d13fd3sessionNo description
akaalb_http_misc_subssessionNo description
AnalyticsSyncHistory1 monthNo description
BIGipServermsocu-web-2-rr.webfarm.ms.com.10882sessionNo description
bm_misessionNo description available.
CX_4061522881 yearNo description
DCID20 minutesNo description
debugneverNo description available.
DrupalVisitorMobilesessionNo description available.
ep2033 monthsNo description available.
frbatlanta#langsessionNo description
geo_info1 yearNo description available.
GoogleAdServingTestsessionNo description
li_gc2 yearsNo description
loglevelneverNo description available.
loom_anon_commentsessionNo description available.
loom_referral_videosessionNo description
mkjs_group_idneverNo description available.
mkjs_user_idneverNo description available.
MorganStanley.ClientServ.Common.IPZipAccess.IPZipCookie.DEFAULT_COOKIE_NAMEpastNo description
NSC_us_nbsl-83+63+21+25-91sessionNo description
nyt-a1 yearThis cookie is set by the provider New York Times. This cookie is used for saving the user preferences. It is used in context with video and audio content.
nyt-gdpr6 hoursNo description available.
nyt-purr1 yearNo description available.
OCC_Encrypted_CookiesessionNo description
polleverywhere_session_id14 daysNo description
ppnet_2020sessionNo description available.
ppnet_2777sessionNo description available.
reuters-geosessionNo description
shell#langsessionNo description
smcx_0_last_shown_atsessionNo description available.
tableau_public_negotiated_localesessionNo description available.
vary1 monthNo description
www#langsessionNo description
X-Vive-CountrysessionNo description
xn_uuid1 monthNo description
Save & Accept
Powered by CookieYes Logo