Search This Blog

Showing posts with label services per household. Show all posts
Showing posts with label services per household. Show all posts

Saturday, August 28, 2010

Service Per Household-Is it the best Measurement?

Services Per Household or (SPH) has been a staple term in the MCIF industry since the inception of the tool, however is it or should it be a standard to compare your institution to your peers?

Since there are no standards in the industry as to what makes up a service, institutions are free to build, bring together, or break apart as many product categories as they choose fragmenting a standard that was once the norm.

A past organization I had worked with had about 44 different service categories and I was the individual that lobbied hard to get all of them. Now you may be saying that is just way too many, however to my defense the majority were from the commercial world where no standards are set and the litany of products are very unique and diverse. As for the retail world there were standards we adhered to.

Through a lot of discussions we’d determine checking should be broken down to interest and non-interest, savings and money markets, internet banking and bill pay. There were strong cross-sell considerations for each of our categories.

My intention was to increase services per household in a methodical way to build a stronger bond with the customer. As with most organizations the overall count of accounts and household numbers were declining, however those that remained were higher balance and multi service households and better for the organization.

Within your MCIF system there should be a function that will allow you to review your SPH. Do this as a company, however more importantly do this at the branch level. After you have obtained a reading for each, review your service categories make adjustments then run again.

If your system has the ability to stratify your services do so by branch and look for the percentage of clients that are single service, 2 services, 3 services and 4 or greater. The organization that I was with we looked at these components for both existing accounts and new since the last update. The trends were very interesting. New branches consistently had clients come in to the institution with 2 or more services and then built from there, however the more established branches had low initial services for new accounts and lower than normal existing SPH numbers.

The biggest difference between the two were existing locations had a lower number of new households establishing relationships compared to new locations. The sales culture in a new location is just different. They were hungry for the business. In addition, most new locations were built in more affluent areas where a single account would bring a checking, savings, debit card, and all internet services without even blinking an eye.

Services per household is an important measurement, however it should never be the measurement to run your institution. In a later blog I will address how focusing on single service households could be one of the best projects for any marketing group, however for now we will continue to work through SPH.

As said above SPH is a good measurement tool, however a more accurate measurement that one could compare against peer is APH or Accounts Per Household. You just can’t mess that one up. It is what it is.

I’d like to provide you with one of the biggest and most detrimental case studies that was conducted that proved the very point never to run your sales culture on a single measurement, and more importantly never SPH.

Early on in 2000 I had a boss who in my mind was a great man. He knew how to motive his work force and worked hard to implement new measurements and pushed hard to change the culture of the bank. We had always had SPH as a part of our measurements, however is was not THE measurement. As a part of a new initiative he established a goal of obtaining an SPH of 3.55 within a year. On average the company had an SPH of 2.37.

Although a formidable goal we at that time had no idea as to what we started in motion. Marketing plans were drawn, reports were built to monitor the progress BI-weekly. Not known by us at the time was how large and dirty this project became for the organization.

To lay more ground work the company had established a new sales culture to increase cross-sell ratios helping associates break out of their comfort zones to begin truly helping the customers with their financial needs. It was working great, there was a resurgence in people helping people and associates were made accountable for their actions.

The project of monitoring SPH was both a next sales step and something that market makers had been asking Senior Management for years. As the months progressed very little progress was being seen in the numbers. Additional sales training was provided and the pressure started building. In the mean time a number of things were taking place which ended up in an entire restructure of the organization, the CEO, my boss, and others were let go. This came as a shock to everyone.

However what came next was even worse. The incentive compensation models for retail were changed to a point system with point values and incentive payouts based upon average balances and types of accounts. It was my job to run the numbers with past data to determine if the payouts were to be the same and that those that were doing the work were compensated for it. With a few minor adjustments we put the program into play. I was handicapped with one additional issue in that the money for the development of the tracking tool, which had an ancillary benefit of decreasing on boarding time by 75% was cut from my budget. The argument that was provided to me was, “If we reduced the entry times associates would fill it doing something non-productive instead of contacting additional clients.” Strike 2!

Here is one more component I was not prepared for. The new Senior Management team picked up where the others had left off. SPH became THE driving factor in their sales program. This number was the only thing. The funny thing was, there were only three individuals in the entire bank that knew how it was built, knew the issues with it, and knew how important clean data was to connecting households correctly, however we were so far removed from Senior Management we couldn’t nor were allowed to pass the information on.

The pressure was strong at the weekly management meeting about SPH, regions and branches were getting beaten up bad. It was almost like a pressure cooker getting ready to blow. Some locations had it easier than others, however it was very apparent the larger number of households a branch had the more difficult it was to turn the ship.

I must also note that at the time I was still in marketing, the place with the pretty paper and colored pens.

After the first month I felt we had a problem. I made the incentive compensation committee aware. We were a little above our projected payouts, but I had made a few changes in the software program that tracked the data to close down some holes that we found where fraud was occurring. The second month solidified the problem. The payout doubled and toped out the incentive compensation payout in month two for the quarter. At that point the flood gates had opened and I found entire branch locations manipulating the systems to get their SPH numbers up an in turn we were paying associates to do it.

I went in to fraud prevention mode and found hole after hole. Multiple entries into the system, accounts with zero or negative balances, you name it. There were still a lot of good associates out there and they brought these issues to my attention. I was able to quickly write programs to stop or monitor the action. I even had an argument with a manager who just couldn’t understand why we wouldn’t pay incentives on a negative or zero balance/non-funded accounts.

Here is one of the best ones; I sat in on a sales conference call where a regional sales manager was providing best practices for increasing branch SPH. It was take a $1 out of petty cash and open an account for a customer. I also heard of branches that just automatically opened debit cards for those that didn’t have or requested one.

It was so hard for me to believe that a bank that was trusted with individuals life savings was not unlike any other organization, if the door was open and the pressure to succeed was high enough things would find their way gone. By the end of the third month I had closed all of the doors and those that were in the wrong were either let go or reprimanded. I was confident that the program was going to be successful.

However it was determined by the new CEO, it was best to walk away from the damage that was created and start a new program based not on individual accomplishments, however the branch as a whole. The new program was put into place, but the pressure on SPH still remained.

It was about six months later that in one of my regular meetings with regional Sales Managers and Presidents about reporting that a Sales Manger asked me how do we get the pressure of SPH off them. I looked at the regional president who had weekly contact with the CEO, and said he was the one that should take the recommendation. His response was that I should sit in one of those meetings to see how brutal it was.

I took a deep breath and told him that I would take care of it. Believe me I was no body in the organization, however I was the head of the MCIF group and had to tell the CEO why running a company based on the single measurement of SPH was detrimental. Besides what did I have to lose?

I figured a face-to-face meeting was the best, however after more thought I figured I’d just put my thoughts in an e-mail and hope for the best. It took me about two days to get it right and I just sent it directly to him. I informed my boss about what I had done, and his response was that I had just committed suicide. My heart sank, however I was the only person in the company that had the data, that knew the data, and knew why it was wrong. If I was to soon die I knew it was for the best for the company.

The next morning I received a response from the CEO, thanking me for the insight, along with an agreement on the issues and for my very reasons from that day forward the program was stopped.

I had won this little battle of misinformation and felt good. I did spend some additional research time to really see where the mistakes were made. Most tried to blame the head of retail that was no longer employed with the bank, however I was able to see his plans of direct mail campaigns to existing clients aggressively offering additional services. Multiple campaigns to help drive cross-sell, however when he left the supporting campaigns left with him and no one picked up the ball to make the program work.

I use this as a strong case study not to use SPH as the only measurement tool. The company suffered from it. It forced trusted individuals to do distrusted acts. I even feel that earnings and the company’s’ stock price was affected because even though there were a lot more accounts, those accounts came at a price that cost the bank hundreds of thousands of dollars. Zero balance, negative balance accounts that did nothing for revenue, they cost, and in addition the company paid incentives. Try closing 24,000 bill pay accounts that were put on the books and then finding out they had not been used for over 13 months. Even today I shake my head that all of this took place in only 3 months.

In conclusion, use review Services Per Household as a measurement. It will provide you a consistent look at those problem branches or even ones that have it right, however what ever you do don’t drive your company with it.

If you have additional questions on this or any other topic please e-mail me or leave a comment below.

Wednesday, August 25, 2010

How to identify the real issues within a branch attrition rate.

If you have already built a strong retention/attrition program and have started to identify issues within your organization, it is now time to put in place a data collection tool that will allow you to understand what makes up your attrition rate.

It is one thing to reprimand associates for bad behavior, however another if you are doing it without any knowledge of how the issues occurred.  With any project I research it is not to call out anyone, but a way to look at a process, improve on it, then coach or redefine a new behavior to obtain the needed results.

Here is how to look at breaking down attrition: Accounts close all of the time for many many reasons, however of all of the reasons, can we determine if they are life cycle, process issues, relocation, death, divorce, a closing of a location, personnel, ingress, egress issues, NSF or anything that force the client or the institution to close an account.   

What you will find is that of the 10% to 25% of those clients that attrited, most are issues beyond ones control, however what this exercise will accomplish is of those that can be controlled if fixed can it change the retention rates.

I must add a simple note here.  At times depending on your clientele, attriting is not a bad idea.  I'll leave the deeper aspect of identifying profitable clients to a separate blog, however sometimes retaining clients just to retain them is not always a good thing.  That is why it is so important to research all aspects of attrition before coming to conclusions.  This information is to identify issues then to fix them...not a way to hang and burn people.

You are first going to have to find a way to collect data from the front line.  If your core system has the ability to collect reason codes that will be your best bet.  It may be as simple as an open field that you can use, however contact your IT group to find out.

Our sales group implemented the first go around and boy was that a failure.  The attempt was knowable, but the results were a mess.  In their defense they gathered the troupes and implemented the data collection process, however that is about a far as it went.  It got better, however keeping 1,500 associates capable of entering data informed as to the process, and the churn factor of employees just didn't help.

Keep this in mind when working with data and lots of it there has to be commonalities so one can work with and review the results quickly.  Problem #1 the sales staff chose a alpha numeric field to enter information in.  This is fine if you truely want to read about the issues, however disastrous if you have 4,000 closed accounts in a month and they all have different verbiage.  The only way to review the data is to look at it and try to match it in silos.  It is just not going to happen.

I quickly made a change to the input of data.  With the help of the sales staff I asked for as many common issues we could think of then I assigned a numeric code to each.

They were as follows:
1 - Rate
2 - Facility Closure
3 - Moving out of the market
4 - Account funds used for purpose intended
5 - Deceased
6 - Removal of name
7 - Dissatisfied with service
8 - Dissatisfied with product
9 - Competitors promotion
10 - Convenience - moving within the market
11 - Transfer funds to another account within the institution
12 - Divorced
13 - Other
14 - NSF/Overdraft
15 - Married
16 - Fraud
17 - Dormant
18- No longer needs accounts
19 - Lost job


If you are looking to implement such a program use these only as guidelines.  You may need to begin with a few then add as needed.  I provided a simple sheet that could be posted close so they could refer to it as often as needed.       

After implementing these new standards it became easier for both sides.  It was less work for the associates and for me I could now do something with the data.  We still struggled with even this part for some associates who felt they were being helpful would instead of just entering the number they would enter "#12" or "number 12" instead of just "12."  If I had the capabilities to change the field to just numeric I would have.  If you can, do it.

I was able to identify those associate issues and then passed that information on to their branch manager.  After some time it got better.

The results in graph form allowed myself and associates to quickly see where the issues were.

Once a month in the core system I had a query run in periodic options that would collect the information I needed to build the report.  I was able to through Excel build a path through an ODBC function with iSeries that after building macros would shake hands with the query grab the data then bring it back and configure the report they way I wanted to see it and deliver it in graphic form for the company and by branch.  This report could be built in seconds each month.

The report provided results in three multiple ways:  1. Numerically providing numbers associated with a graph.  2. The same results, however in graph form.  3. The numeric data was broken down by branch. 4. Each code was given a factor as to if an associate could have changed the behavior of the client which became "issues."  A percentage was provided as to of all the closed accounts what percent was the branch in control of. 5. Where and who the data came from.  


I must bring back once again how important it is for you to learn Excel.  This report on its own could take several hours to build, however once set up it takes longer to open the report than it does to run it.  Learn your core or find someone in IT to work with you.  Have them look into iSeries or ODBC in Excel to connect with your core system.  Learn how to build macros in both your core and Excel.  And also learn how and understand pivot tables. 


It will be hard at first, however once you get the hang of it you will be able to understand the data, build it quickly and start spending more time analyzing it. 


If you need additional help please feel free to contact me through e-mail