Wednesday, July 13, 2005

Data Quality is important. Do companies ever get it?

In my job, I spend a considerable amount of time watching the data quality and data integration markets, including user adoption, best (and worst) practices, and major blunders by large organizations. Right now, I'm struggling with my bank, because they keep sending me marketing stuff although I'm already a customer. Now, the problem is, they don't understand that their data entry people added the names of the account owners (joint account of my wife and myself) in a way that makes zero sense.

Typically, you have a field for first name and a field for last name (forget middle initials). Works well for single account owners or maybe joint account owners with the same last name. Does not work for couples with different last names. For example, if Joe Bloggs is married to Jane Doe, they would enter "Joe and Jane Doe" under first name and "Bloggs" under last name. Or "Joe and Jane" "Bloggs and Doe". And that's just silly. Because any such combination would not match the real name of the person, plus it looks really stupid on the address field of a letter or bank statement: "Dear Joe and Jane Bloggs and Doe". Yeah right.

Trying to change it to a single name poses major difficulties in the bank, because "the system doesn't allow it". Geez. So I ask them to drop me from the marketing list, and they say they can't find me on the campaign list. Duh. If it wasn't such as hassle to switch banks, I'd do it (again) in an instant. Bad data quality is a clear indicator for incompetency.

0 Comments:

Post a Comment

Links to this post:

Create a Link

<< Home