FEB 22, 2011 8:25am ET

Related Links

Innovative Organizations Likely to have More Pervasive BI and Data Governance
September 2, 2014
Revolutionize Your Business Intelligence with Lean, High-Performance Solutions
August 21, 2014
Should You Always Obey Orders from Your Executives?
August 7, 2014

Web Seminars

Essential Guide to Using Data Virtualization for Big Data Analytics
September 24, 2014
Integrating Relational Database Data with NoSQL Database Data
October 23, 2014

Has Data Become a Four-Letter Word?

Print
Reprints
Email

In her excellent blog post “'The Bad Data Ate My Homework'’' and Other IT Scapegoating,” Loraine Lawson explained how “there are a lot of problems that can be blamed on bad data. I suspect it would be fair to say that there’s a good percentage of problems we don’t even know about that can be blamed on bad data and a lack of data integration, quality and governance.”

Get access to this article and thousands more...

All Information Management articles are archived after 7 days. REGISTER NOW for unlimited access to all recently archived articles, as well as thousands of searchable stories. Registered Members also gain access to:

  • Full access to information-management.com including all searchable archived content
  • Exclusive E-Newsletters delivering the latest headlines to your inbox
  • Access to White Papers, Web Seminars, and Blog Discussions
  • Discounts to upcoming conferences & events
  • Uninterrupted access to all sponsored content, and MORE!

Already Registered?

Advertisement

Comments (9)
Bad data is only a valid excuse if management refuses to dedicate any resources to its resolution. Once bad data is identified and the source is identified it's time for action to correct it, rather than using it as a crutch. However, it has been my experience that the owners of the systems that are generating bad data are often able to convince management that it is too costly and difficult to fix it at the source - so why don't we just make IT "fix" it as it is moved from source to destination. Architecturally this is the worst option (well, second worst to "make the reports account for bad data"). But the difference is that IT can usually accomplish this so we are victims of our own proficiency. I have actually heard first hand conversations where the owners of reports who have coded for bad data are upset when the data is cleaned up and insist that IT "unfix" the data so the reports work. To my amazement, management agreed to this solution - they purposefully messed up their own data. I chose to leave that company, for obvious reasons.
Posted by Mark V | Wednesday, February 23 2011 at 10:41AM ET
I would suggest something completely different: it is not data or data quality that is the problem. It is that people, and by extension organizational cultures, that think that data is absolute that are the problem. The phrase: "the data is bad" is the epitome of the innumeracy that is plaguing our progress in the 21st century. All raw information has some uncertainty associated with it and any process that uses that data needs to take that into account. So by definition there isn't any 'bad' data, just data with a certain amount of uncertainty.

The reason that organizations like Amazon and Google run circles around their competition is because in their corporate cultures they embrace that uncertainty and bake it right into their business processes.

Talking about data in the absolute is missing the bigger picture.

Posted by Theodore O | Wednesday, February 23 2011 at 10:41AM ET
Add Your Comments:
You must be registered to post a comment.
Not Registered?
You must be registered to post a comment. Click here to register.
Already registered? Log in here
Please note you must now log in with your email address and password.
Twitter
Facebook
LinkedIn
Login  |  My Account  |  White Papers  |  Web Seminars  |  Events |  Newsletters |  eBooks
FOLLOW US
Please note you must now log in with your email address and password.