<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for Banking 4 Tomorrow</title>
	<atom:link href="http://www.banking4tomorrow.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.banking4tomorrow.com</link>
	<description>The blog to launch the new book from Brett King BANK 2.0</description>
	<lastBuildDate>Sat, 18 Feb 2012 05:00:14 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Respect the crowd &#8211; don&#8217;t shut them out by Respect the Crowd &#8211; Don&#8217;t Shut Them Out &#171; J.D. Power Banking Blog</title>
		<link>http://www.banking4tomorrow.com/2012/02/respect-the-crowd-dont-shut-them-out/comment-page-1/#comment-176900</link>
		<dc:creator>Respect the Crowd &#8211; Don&#8217;t Shut Them Out &#171; J.D. Power Banking Blog</dc:creator>
		<pubDate>Sat, 18 Feb 2012 05:00:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.banking4tomorrow.com/?p=1389#comment-176900</guid>
		<description>[...] Source: Brett King, Banking4Tomorrow. Read the full post. [...]</description>
		<content:encoded><![CDATA[<p>[...] Source: Brett King, Banking4Tomorrow. Read the full post. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on About the Author by Auto Power Blogs</title>
		<link>http://www.banking4tomorrow.com/author/comment-page-1/#comment-174256</link>
		<dc:creator>Auto Power Blogs</dc:creator>
		<pubDate>Fri, 10 Feb 2012 02:37:42 +0000</pubDate>
		<guid isPermaLink="false">http://banki.onlinefactor.com.au/?page_id=7#comment-174256</guid>
		<description>[...] Huffington Post (Business News), Internet Evolution and on his website, www.Banking4Tomorrow.com. Brett King currently advises top global financial institutions and has also been featured as an industry [...]</description>
		<content:encoded><![CDATA[<p>[...] Huffington Post (Business News), Internet Evolution and on his website, <a href="http://www.Banking4Tomorrow.com" rel="nofollow">http://www.Banking4Tomorrow.com</a>. Brett King currently advises top global financial institutions and has also been featured as an industry [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Would SOPA/PIPA kill Internet Banking? by David Gerbino &#124; US Community Banker</title>
		<link>http://www.banking4tomorrow.com/2012/01/would-sopapipa-kill-internet-banking/comment-page-1/#comment-165766</link>
		<dc:creator>David Gerbino &#124; US Community Banker</dc:creator>
		<pubDate>Thu, 19 Jan 2012 11:51:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.banking4tomorrow.com/?p=1359#comment-165766</guid>
		<description>Brett, fantastic job explaining the perils of PIPA and SOPA. I like the fact you used bank examples.

These two pieces of legislation are dangerous. If copyright holders want to go after copyright violators, they should just simply use law enforcement and due process. If foreign governments do not provide the proper laws to protect copyright holders, pressure should be put on them to add that protection.</description>
		<content:encoded><![CDATA[<p>Brett, fantastic job explaining the perils of PIPA and SOPA. I like the fact you used bank examples.</p>
<p>These two pieces of legislation are dangerous. If copyright holders want to go after copyright violators, they should just simply use law enforcement and due process. If foreign governments do not provide the proper laws to protect copyright holders, pressure should be put on them to add that protection.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why snail mail is dying, and taking your identity with it&#8230; by brettking</title>
		<link>http://www.banking4tomorrow.com/2011/12/why-snail-mail-is-dying-and-taking-your-identity-with-it/comment-page-1/#comment-165539</link>
		<dc:creator>brettking</dc:creator>
		<pubDate>Wed, 18 Jan 2012 20:18:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.banking4tomorrow.com/?p=1332#comment-165539</guid>
		<description>Martin,

I&#039;m cool with having an address on a customer profile, and even occasionally couriering or mailing you stuff like a new debit card (although in the future we&#039;ll just be downloading debit cards to our mobile wallet). However, that doesn&#039;t mean that your address is essential for IDV.

BK</description>
		<content:encoded><![CDATA[<p>Martin,</p>
<p>I&#8217;m cool with having an address on a customer profile, and even occasionally couriering or mailing you stuff like a new debit card (although in the future we&#8217;ll just be downloading debit cards to our mobile wallet). However, that doesn&#8217;t mean that your address is essential for IDV.</p>
<p>BK</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why snail mail is dying, and taking your identity with it&#8230; by Martin</title>
		<link>http://www.banking4tomorrow.com/2011/12/why-snail-mail-is-dying-and-taking-your-identity-with-it/comment-page-1/#comment-165533</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Wed, 18 Jan 2012 19:58:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.banking4tomorrow.com/?p=1332#comment-165533</guid>
		<description>So how is the bank supposed to be able to send you a replacement debit card?</description>
		<content:encoded><![CDATA[<p>So how is the bank supposed to be able to send you a replacement debit card?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Would SOPA/PIPA kill Internet Banking? by Paul Lee</title>
		<link>http://www.banking4tomorrow.com/2012/01/would-sopapipa-kill-internet-banking/comment-page-1/#comment-165353</link>
		<dc:creator>Paul Lee</dc:creator>
		<pubDate>Wed, 18 Jan 2012 10:25:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.banking4tomorrow.com/?p=1359#comment-165353</guid>
		<description>SOPA gives power to idiots to control everyone on the Internet. The proof of stupidity is in the nature of te proposal itself.</description>
		<content:encoded><![CDATA[<p>SOPA gives power to idiots to control everyone on the Internet. The proof of stupidity is in the nature of te proposal itself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The upside and downside to the digital shift by Brett King</title>
		<link>http://www.banking4tomorrow.com/2012/01/the-upside-and-downside-to-the-digital-shift/comment-page-1/#comment-165144</link>
		<dc:creator>Brett King</dc:creator>
		<pubDate>Tue, 17 Jan 2012 20:27:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.banking4tomorrow.com/?p=1336#comment-165144</guid>
		<description>Ron,

I&#039;m a big fan of contract-based (or output-based) budgeting for this reason.

It was interesting to see TD&#039;s approach to handling this problem. They appointed the &#039;manager&#039; who was holding the branch budgets, to head up digital - then told him to go find budget. A pretty practical solution IMHO

BK</description>
		<content:encoded><![CDATA[<p>Ron,</p>
<p>I&#8217;m a big fan of contract-based (or output-based) budgeting for this reason.</p>
<p>It was interesting to see TD&#8217;s approach to handling this problem. They appointed the &#8216;manager&#8217; who was holding the branch budgets, to head up digital &#8211; then told him to go find budget. A pretty practical solution IMHO</p>
<p>BK</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The upside and downside to the digital shift by Ron Shevlin</title>
		<link>http://www.banking4tomorrow.com/2012/01/the-upside-and-downside-to-the-digital-shift/comment-page-1/#comment-165139</link>
		<dc:creator>Ron Shevlin</dc:creator>
		<pubDate>Tue, 17 Jan 2012 20:02:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.banking4tomorrow.com/?p=1336#comment-165139</guid>
		<description>Totally agree with the sentiment, but will quibble over one word: Inertia. I don’t see the problem as inertia, I see it as POLITICS.

When you give a manager a budget, s/he will do things: 1) Attempt to prove that the return on that investment (budget) is really high, and 2) Attempt to ensure that next year’s budget goes up (or at least not down).

These might not really be mutually exclusive points as #1 is used to accomplish #2.

Any new channel suffers from having to steal budget away from existing channels. Or, more accurately, from stealing budget away from the MANAGERS who run those existing channels. And that’s a whole easier said than done.

My solution would be to take the more successful managers from existing channels and put them in charge of the new channels. I wouldn’t buy the BS that they “don’t understand the new channels” blah blah blah.</description>
		<content:encoded><![CDATA[<p>Totally agree with the sentiment, but will quibble over one word: Inertia. I don’t see the problem as inertia, I see it as POLITICS.</p>
<p>When you give a manager a budget, s/he will do things: 1) Attempt to prove that the return on that investment (budget) is really high, and 2) Attempt to ensure that next year’s budget goes up (or at least not down).</p>
<p>These might not really be mutually exclusive points as #1 is used to accomplish #2.</p>
<p>Any new channel suffers from having to steal budget away from existing channels. Or, more accurately, from stealing budget away from the MANAGERS who run those existing channels. And that’s a whole easier said than done.</p>
<p>My solution would be to take the more successful managers from existing channels and put them in charge of the new channels. I wouldn’t buy the BS that they “don’t understand the new channels” blah blah blah.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The upside and downside to the digital shift by Neil Robinson</title>
		<link>http://www.banking4tomorrow.com/2012/01/the-upside-and-downside-to-the-digital-shift/comment-page-1/#comment-164980</link>
		<dc:creator>Neil Robinson</dc:creator>
		<pubDate>Tue, 17 Jan 2012 10:30:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.banking4tomorrow.com/?p=1336#comment-164980</guid>
		<description>Thanks Brett - that&#039;s clarified things enormously and now provides a far more focussed argument - which, ironically, reinforces both our positions!

Am I right in saying that your main objection with legacy architectures is the form filling, resulting duplification and capacity for mistakes and costs associated with that?

OK - get rid of the paper. If its not necessary for digital banking, why should it be needed for a branch?

Just give the induction staff (those opening the account) an iPad/whatever and let them fill it on on behalf of the customer. Their familiarity with the process (unlike the customer) will speed it through and provide an opportunity for up-selling. Why do I feel there is such an opportunity?

Now I have to put my psychological hat on. 

When you give a customer a chance to think during any process, they will start to think out loud. That&#039;s an incontrovertible fact. Let me tell you about doctors in general practice - bear with me!

Many doctors find that a patient will visit them with a problem. while they&#039;re writing the prescription or waiting for the patient to get dressed, the patient will say &quot;oh by the way, I&#039;ve also got this lump/rash/pain etc&quot;.

This is so common, it actually has a medical name - doorknob syndrome - Google it to see the results.

I&#039;m lucky enough to have spent time on both sides of the banking fence - working along side front-line staff in branches as I waited to get access to the systems I was about to install, fix or upgrade where I couldn&#039;t help but overhear the conversations and on the digital side where the flow and click rate were key.

What your readers may not realise - but I&#039;m sure you will - is that in on-line or phone banking, customer contact times are measured in seconds per month and strenuous efforts are made to reduce that. Many a time I&#039;ve had my backside kicked for a system that was slow or not running at the optimum - believe me, its not something you forget. Barclays once fired their ATM director for the simply mistake of getting a date change wrong one weekend that took the ATM&#039;s offline!

But my key point is that for a digital bank to make money it has to sell things that are sold from left field - door-knob syndrome sales - yet digital is absolutely not optimised to do that. Particularly not local app-based digital. Retail on-line is about minimising clicks to cart. Conventional retail is the diametric opposite - its about slowing the customer down as much as possible to keep them in store while they think or impulse (door knob) buy.

Every bricks-and-mortar retail environment offers side-sells. Buy a car and where you sit while the process completes and look around you. You&#039;ll see the floor mats, accessories, clothing. Porsche is the greatest exponent of this. Go and check out a Porsche showroom. I defy you not to buy something you never went in for! 

Your greatest challenge is to deal with that disparity. I&#039;m sure you can fix that, but I&#039;m worried that&#039;s not in any of your published discussions.

Again, this will be something you&#039;re aware of, but your readers may not. Check the site that you contributed to,

 http://engagementbanking.sapient.com/

And click the &quot;role of the branch&quot; tab, tab 3. The chart shows the customer engagement value matrix - you&#039;ll see my point. Digital is low, branch is high. 

In summary, I absolutely agree with you that the legacy processes are terrible and should be re-vamped to use the technology now available. Paper is a ridiculous concept and has no place in any modern commercial environment. Believe me, I know I also worked on the IBM AS/400 systems in one bank that managed the vast paper storage facilities for all that paperwork!

But to sweep away the entire legacy environment because the forms sometimes get filled in wrong is a bit like throwing out the baby with the bath water!

I&#039;d recommend that along with all your web and UX developers, you get some retail psychology people in before you burn too much start-up capital on cool-looking but ultimately ineffective digital front ends.</description>
		<content:encoded><![CDATA[<p>Thanks Brett &#8211; that&#8217;s clarified things enormously and now provides a far more focussed argument &#8211; which, ironically, reinforces both our positions!</p>
<p>Am I right in saying that your main objection with legacy architectures is the form filling, resulting duplification and capacity for mistakes and costs associated with that?</p>
<p>OK &#8211; get rid of the paper. If its not necessary for digital banking, why should it be needed for a branch?</p>
<p>Just give the induction staff (those opening the account) an iPad/whatever and let them fill it on on behalf of the customer. Their familiarity with the process (unlike the customer) will speed it through and provide an opportunity for up-selling. Why do I feel there is such an opportunity?</p>
<p>Now I have to put my psychological hat on. </p>
<p>When you give a customer a chance to think during any process, they will start to think out loud. That&#8217;s an incontrovertible fact. Let me tell you about doctors in general practice &#8211; bear with me!</p>
<p>Many doctors find that a patient will visit them with a problem. while they&#8217;re writing the prescription or waiting for the patient to get dressed, the patient will say &#8220;oh by the way, I&#8217;ve also got this lump/rash/pain etc&#8221;.</p>
<p>This is so common, it actually has a medical name &#8211; doorknob syndrome &#8211; Google it to see the results.</p>
<p>I&#8217;m lucky enough to have spent time on both sides of the banking fence &#8211; working along side front-line staff in branches as I waited to get access to the systems I was about to install, fix or upgrade where I couldn&#8217;t help but overhear the conversations and on the digital side where the flow and click rate were key.</p>
<p>What your readers may not realise &#8211; but I&#8217;m sure you will &#8211; is that in on-line or phone banking, customer contact times are measured in seconds per month and strenuous efforts are made to reduce that. Many a time I&#8217;ve had my backside kicked for a system that was slow or not running at the optimum &#8211; believe me, its not something you forget. Barclays once fired their ATM director for the simply mistake of getting a date change wrong one weekend that took the ATM&#8217;s offline!</p>
<p>But my key point is that for a digital bank to make money it has to sell things that are sold from left field &#8211; door-knob syndrome sales &#8211; yet digital is absolutely not optimised to do that. Particularly not local app-based digital. Retail on-line is about minimising clicks to cart. Conventional retail is the diametric opposite &#8211; its about slowing the customer down as much as possible to keep them in store while they think or impulse (door knob) buy.</p>
<p>Every bricks-and-mortar retail environment offers side-sells. Buy a car and where you sit while the process completes and look around you. You&#8217;ll see the floor mats, accessories, clothing. Porsche is the greatest exponent of this. Go and check out a Porsche showroom. I defy you not to buy something you never went in for! </p>
<p>Your greatest challenge is to deal with that disparity. I&#8217;m sure you can fix that, but I&#8217;m worried that&#8217;s not in any of your published discussions.</p>
<p>Again, this will be something you&#8217;re aware of, but your readers may not. Check the site that you contributed to,</p>
<p> <a href="http://engagementbanking.sapient.com/" rel="nofollow">http://engagementbanking.sapient.com/</a></p>
<p>And click the &#8220;role of the branch&#8221; tab, tab 3. The chart shows the customer engagement value matrix &#8211; you&#8217;ll see my point. Digital is low, branch is high. </p>
<p>In summary, I absolutely agree with you that the legacy processes are terrible and should be re-vamped to use the technology now available. Paper is a ridiculous concept and has no place in any modern commercial environment. Believe me, I know I also worked on the IBM AS/400 systems in one bank that managed the vast paper storage facilities for all that paperwork!</p>
<p>But to sweep away the entire legacy environment because the forms sometimes get filled in wrong is a bit like throwing out the baby with the bath water!</p>
<p>I&#8217;d recommend that along with all your web and UX developers, you get some retail psychology people in before you burn too much start-up capital on cool-looking but ultimately ineffective digital front ends.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The upside and downside to the digital shift by brettking</title>
		<link>http://www.banking4tomorrow.com/2012/01/the-upside-and-downside-to-the-digital-shift/comment-page-1/#comment-164832</link>
		<dc:creator>brettking</dc:creator>
		<pubDate>Tue, 17 Jan 2012 03:05:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.banking4tomorrow.com/?p=1336#comment-164832</guid>
		<description>Neil,

Your characterizations aren&#039;t entirely accurate. There&#039;s a difference between core capability to support a digital bank, and legacy capability. 

Firstly, the paperwork of account opening is still done in a legacy branch, then it&#039;s entered into a computer either in-branch or in a central processing centre. For a client opening a current (checking) account, and a credit card, a combined form may be executed, but the data is entered twice into two different systems. It&#039;s not uncommon for customers who&#039;ve opened a CASA account and a credit card, to receive documentation from the bank with errors in one or both of the accounts, such as incorrect addresses, differences in spelling between the debit card, check book and credit card, etc. The centralization of processing, is not exactly a seamless, flawless system. 

The problem for me is still largely unnecessary manual processing and handling. On your comment that branch staff are a &#039;shell&#039; as a tiny cost of overall service provision, the economics I&#039;ve looked at don&#039;t bare this out, but I can see in some derivations that might be the case. Regardless, the manual processing and any paperwork are simply no longer required in this process. So they are still simply legacy costs.

With my experience on the Movenbank side (and with other global banks), I can tell you exactly what the cost of processing, etc is, and I can tell you it is generally fractional compared with the traditional costs I see accounted for by most retail banks on the acquisition and day-to-day account management side. Sure, I need a core system, and I need processing capability. Do I need &quot;legacy&quot; systems? No. Do I need legacy processes? Absolutely, not.

The key debate here, and what I was trying to get into, was not around legacy technology infrastructure, but legacy processes that simply aren&#039;t defensible. Current IDV processes are a big one for me. I&#039;m sorry, but regardless of what defense you want to mount on a central processing basis, maintaining the current signature card and IDV process, is not smart - it&#039;s risky and expensive. 

There&#039;s much work to do. Let&#039;s not confuse core processing capability with the dead wood of manual processing, processes that have already been successfully replaced by other more progressive institutions, and older legacy systems that require significant work-arounds to work in today&#039;s environment.

BK</description>
		<content:encoded><![CDATA[<p>Neil,</p>
<p>Your characterizations aren&#8217;t entirely accurate. There&#8217;s a difference between core capability to support a digital bank, and legacy capability. </p>
<p>Firstly, the paperwork of account opening is still done in a legacy branch, then it&#8217;s entered into a computer either in-branch or in a central processing centre. For a client opening a current (checking) account, and a credit card, a combined form may be executed, but the data is entered twice into two different systems. It&#8217;s not uncommon for customers who&#8217;ve opened a CASA account and a credit card, to receive documentation from the bank with errors in one or both of the accounts, such as incorrect addresses, differences in spelling between the debit card, check book and credit card, etc. The centralization of processing, is not exactly a seamless, flawless system. </p>
<p>The problem for me is still largely unnecessary manual processing and handling. On your comment that branch staff are a &#8217;shell&#8217; as a tiny cost of overall service provision, the economics I&#8217;ve looked at don&#8217;t bare this out, but I can see in some derivations that might be the case. Regardless, the manual processing and any paperwork are simply no longer required in this process. So they are still simply legacy costs.</p>
<p>With my experience on the Movenbank side (and with other global banks), I can tell you exactly what the cost of processing, etc is, and I can tell you it is generally fractional compared with the traditional costs I see accounted for by most retail banks on the acquisition and day-to-day account management side. Sure, I need a core system, and I need processing capability. Do I need &#8220;legacy&#8221; systems? No. Do I need legacy processes? Absolutely, not.</p>
<p>The key debate here, and what I was trying to get into, was not around legacy technology infrastructure, but legacy processes that simply aren&#8217;t defensible. Current IDV processes are a big one for me. I&#8217;m sorry, but regardless of what defense you want to mount on a central processing basis, maintaining the current signature card and IDV process, is not smart &#8211; it&#8217;s risky and expensive. </p>
<p>There&#8217;s much work to do. Let&#8217;s not confuse core processing capability with the dead wood of manual processing, processes that have already been successfully replaced by other more progressive institutions, and older legacy systems that require significant work-arounds to work in today&#8217;s environment.</p>
<p>BK</p>
]]></content:encoded>
	</item>
</channel>
</rss>

