Tag Archives: Poor Data Quality
Mar 28, 2012 by Thomas Redman
The most acrimonious company battles I’ve personally witnessed have involved disagreements over data—their meanings and whether they could be trusted. I’ve seem a few of these and, in the re-telling below merged them into a single story (I’ve done my best to convey the essence of each of these battles).
Feb 29, 2012 by Thomas Redman
In this series of posts I’m looking at significant costs of poor data quality that go beyond those we usually focus on. Last week I noted that bad data make it more difficult to implement new technologies. I want to take a slight detour off that post today and look at two subtleties that conspire to make a technologist’s life even more difficult.
Feb 22, 2012 by Thomas Redman
This series of posts looks beyond the costs of poor data quality we usually focus on, namely increased costs, angered customers and compromised decision-making. This week my focus is on the difficulties that bad data add in implementing new technologies. Some years ago a sequence of studies (sponsored, if memory serves, by Gartner, DataFlux and others) identified poor data quality as one of the most important reasons that new enterprise systems and data warehouses failed to gain acceptance by their user community. I’ve seen nothing that suggests any improvements.
Feb 15, 2012 by Thomas Redman
This series of posts looks beyond the costs of poor data quality we usually focus on, namely increased costs, angered customers and compromised decision-making. Last week I gave an example that illustrated how bad data can divert management attention from more important issues.
Feb 08, 2012 by Thomas Redman
A recent article in the New York Times caused me to reflect again on some the cost of poor data quality. We’re used to thinking about added cost, angered customers, and compromised decision-making. But there are a lot of other costs as well. I’m going to devote my next several posts to these non-traditional costs.