So, you’ve got all that data. Now how are you going to use it?
Friday, June 22nd, 2007You may have heard the recent news that an Albertsons group is canceling their customer-loyalty card system. As with similar CRM deployments, the cards were mainly a way to collect customer data. However, according to Bob Colgrove, Albertsons Southwest division president, their aim in canceling the cards “is to give all the consumers in the marketplace the same great deals regardless of having to have a loyalty card” (quoted on RetailNet).
Presenting a compelling case, eWeek’s Evan Schuman argues that “the program got pulled because grocery managers weren’t bothering to use the data.” Schuman says that while many retailers love the idea of CRM data collection, few do much with it after installation. Then, when the business doesn’t see much ROI, they conclude that the CRM solution doesn’t work, and they pull the plug without really trying to figure out more effective uses for that collected data.
Richard Boardman says on The CRM Consultant that organizations shouldn’t even deploy CRM if there is insufficient executive sponsorship, insufficient financial and manpower resources available to run a long term program or instability within the business. The third element seems pretty obvious, but the first two got us wondering about how and why a lack of resources and support spells doom for CRM and all the data attached to it.
In a typical CRM deployment like Albertsons’, the amount of data is huge, and that volume means that the amount of waste is potentially huge as well. The reason for that waste (especially in deployments that lack the proper infrastructure) is that a lot of businesses still don’t have the tools to pull useful information out of their data. Maybe the data is just sitting in silos. Maybe it’s in several databases and in varying formats. Many companies see the resolution of that data as an overwhelming task, but it doesn’t have to be.
One way to extract that data is by using identity resolution software. It can resolve data across remote, disparate databases and turn it into manageable, usable information. By giving a real-time view of that data, it provides a cost-effective way to gain identity knowledge from the data. With CRM in place, you’ve collected lots of useful data; you’ve just got to put it to use.
The hard part is then resolving those multiple instances into one, accurate identity. Thus, navigating the field of identity data is pretty tricky. A good identity resolution system then has to. . .
In a broader sense, that brings up another interesting question: is privacy vs. security a balancing act or does it have to be a quid-pro-quo consumer market?
“The delay is primarily because the proposed database, with records on the 16 million motorists in Texas, has yet to be put into action. However, the reasons behind the slow deployment demonstrate some common database concerns: avoiding false-positives and protecting individuals’ privacy.
It’s true that a rigorous data comparison can cause inconvenience and expenses, but consider the cost of a security breach. Which one of those costs are we more willing to pay?
While Teufel’s remarks don’t necessarily go as far as some privacy advocates would like, it does seem that DHS is interested in finding a balance that keeps passengers safe and protects their personal data.