Data isn’t valuable. Information is!
Banks spend a vast amount of time researching and collecting data about clients, but often lack the bigger picture of connecting these separate data piles from various systems. Data alone is worthless, but connected and turned into information using an identity database, new possibilities such as reducing the cost per client, increasing quality of service and anticipating a client's actions are possible.
Let me introduce you to Urs. He is a member of the board at a private bank called Bank Lake Zurich. His main goal is to increase the amount of clients handled by his relationship managers, which means reducing costs. He realizes that relationship managers spend a major share of their time researching which client to contact next and what he or she might be interested in. Urs’ new best friend Patrik, the CIO, figures that this problem can only be solved by a data driven approach.
Patrik states that over the years, the bank has collected a big pile of data consisting of transactions, position information, tax statements, but also CRM, click streams, phone calls, emails, written letters and so on. Each pile alone is next to worthless (except the banking stuff of course:-) ). Patrik thinks out loud that once you start to connect all the piles, you’d be able to figure out the answers to questions like:
- How often was the client in contact with the bank? How did the activity change over time? Is it trending up- or downwards?
- What is the client’s opinion towards the bank and how does this influence the amount and volume of trades he is performing? How much new money has he brought?
- Is the client at risk of leaving the bank?
Urs thinks that this is great news and exactly what he always wanted for his relationship mangers. So he wants to know more about how this might work.
The key: connecting data from various systems to one client using an identity database
In a perfect world, every system would have the same identifier to classify a client. However, the world isn’t perfect. It’s not only not perfect, but a lot of interesting sources additionally don’t have a unique qualifier! Therefore, something more sophisticated is needed to connect each system.
Every person has many identifying properties, for example a name, CRM ID, an account number, etc.
Meet Hans, a typical bank client:
To identify Hans in any system, we can use any of his known identifying properties.
So let’s apply this to an email archive. The bank received the email below and it contains three properties we already know belong to Hans. This means we can - with a fairly high probability – conclude that this email was sent by Hans. Going through all existing data and connecting it to a certain client is what we call crawling.
But wait, the email offers even more information! It contains an email address. Email addresses are a pretty good identifier. In fact, much better than just a first and a last name. The email “firstname.lastname@example.org” is added to the pool of known identifiers. This is called the learning aspect. It can be digitized, which means that you don’t need to manually maintain the identity database! The possibilities of the learning process are infinite.
EXAMPLE: Assume Hans browses your web site for quite some time, all his actions are logged, but they are of no use to you because he has never logged in. One day, Hans sends an email using the contact form. At this point, you are able to trace back every click Hans ever did! Why? Because the contact email will contain the browser identifier, which is then used to match the clickstream history.
Sounds incredibly difficult and expensive?
Urs wants to stay realistic and thinks of the cost of such a solution. But Patrik, the CIO, tells him that he already has a working proof of concept in place, which was developed by ti&m using their “Analytics” product. Patrik invites Urs to see for himself and to stop by ti&m in Zurich for another “Lab-Visit” - for more inspiration and to sharpen the gut-feeling of what is possible.
Legal / compliance / reputational remarks
The next argument is about compliance: Firms in general and banks specifically need to keep the legal/compliance aspects as well as the reputational risks in mind. Data privacy laws allow the use of internal data to profile and classify clients. They also give any client the right to demand to know what data is stored about them, how it is used and to request a deletion. The bank privacy laws guarantee the privacy of the client’s bank relation to any 3rd party. As the data is only used internally, there is no violation of banking regulations.
Knowing what data is available about each client and proactively as well as transparently making it available to the client can lead to a reputation gain! Thus, the client feels in power of what the company knows. Nevertheless, personalized pricing and similar actions are very sensitive and the public has not yet accepted them. Aggregating all data in one place is a high risk. It can be mitigated by making the aggregate anonymous or enforcing technical as well as organizational security.
Urs is convinced. Having such a system in place will give him the full 360° view of his clients. This allows him to reduce the cost per client due to less human time being invested. On top of that, his relationship managers may increase quality of service as they can anticipate the client’s actions. And these are just a few of the possibilities. By using big data technologies and brain power one can come up with amazing opportunities to reduce costs and grow business.
Please get in touch – come by for a Lab Visit at ti&m!
If you are a developer, you have had to set up your development environment for any of your projects. Database, application server, index, and so on. That might go smoothly… or not. If the first applies, CONGRATULATIONS! And get to work ;) but if not, then welcome to the non-smooth environment setup problem. Even worse, what if you need to have different environments for different projects (e.g. database versions)? And what if you need to reset one, but keep the others untouched?Mehr erfahren
Dass schnelle Innovationen in grossen Organisationen möglich sein soll, scheint vielen unmöglich zu sein. Doch Thomas Wüst zeigt mit seiner ti&m AG jeden Tag aufs Neue, dass genau dies möglich ist.Mehr erfahren
Veraltete Software-Entwicklungsmethoden sind ein sicheres Rezept zum Scheitern. Dabei gibt es bekannte und bereits bewährte Methoden und Frameworks, die Abhilfe schaffen können. Ihr Motto: lieber nachfragen und testen anstatt Checklisten eines Managers abarbeiten.Mehr erfahren
Seit August 2016 ist Marco Berg Leiter der ti&m Niederlassung in Frankfurt am Main. Wir haben mit ihm über seine ersten Eindrücke von ti&m, über seinen Werdegang und seine Ziele gesprochen.Mehr erfahren