OCDQ Blog
for Information Management Blogs
FEB 27, 2012 9:09am ET

Blogroll

blog

Data Quality: Quo Vadimus?

Print
Reprints
Email

Over the past week, an excellent meme has been making its way around the data quality blogosphere.  It all started, as many of the best data quality blogging memes do, with a post written by Henrik Liliendahl Sørensen.

In “Turning a Blind Eye to Data Quality,” Henrik blogged about how, as data quality practitioners, we are often amazed by the inconvenient truth that our organizations are capable of growing as a successful business even despite the fact that they often turn a blind eye to data quality by ignoring data quality issues and not following the data quality best practices that we advocate.

“The evidence about how poor data quality is costing enterprises huge sums of money has been out there for a long time,” Henrik explained. “But business successes are made over and over again despite bad data. There may be casualties, but the business goals are met anyway. So, poor data quality is just something that makes the fight harder, not impossible.”

As data quality practitioners, we often don’t effectively sell the business benefits of data quality, but instead we often only talk about the negative aspects of not investing in data quality, which, as Henrik explained, is usually why business leaders turn a blind eye to data quality challenges. Henrik concluded with the recommendation that when we are talking with business leaders, we need to focus on “smaller, but tangible, wins where data quality improvement and business efficiency goes hand in hand.”

Is Data Quality a Journey or a Destination?

Henrik’s blog post received excellent comments, which included a debate about whether data quality is a journey or a destination.

Garry Ure responded with his blog post “Destination Unknown,” in which he explained how “historically the quest for data quality was likened to a journey to convey the concept that you need to continue to work in order to maintain quality.” But Garry also noted that sometimes when an organization does successfully ingrain data quality practices into day-to-day business operations, it can make it seem like data quality is a destination that the organization has finally reached.

Garry concluded data quality is “just one destination of many on a long and somewhat recursive journey. I think the point is that there is no final destination, instead the journey becomes smoother, quicker, and more pleasant for those traveling.”

Bryan Larkin responded to Garry with the blog post “Data Quality: Destinations Known,” in which Bryan explained, “data quality should be a series of destinations where short journeys occur on the way to those destinations. The reason is simple. If we make it about one big destination or one big journey, we are not aligning our efforts with business goals.”

In order to do this, Bryan recommends that “we must identify specific projects that have tangible business benefits (directly to the bottom line — at least to begin with) that are quickly realized. This means we are looking at less of a smooth journey and more of a sprint to a destination — to tackle a specific problem and show results in a short amount of time. Most likely we’ll have a series of these sprints to destinations with little time to enjoy the journey.”

“While comprehensive data quality initiatives,” Bryan concluded, “are things we as practitioners want to see — in fact we build our world view around such — most enterprises (not all, mind you) are less interested in big initiatives and more interested in finite, specific, short projects that show results. If we can get a series of these lined up, we can think of them more in terms of an overall comprehensive plan if we like — even a journey. But most functional business staff will think of them in terms of the specific projects that affect them.”

The Latin phrase Quo Vadimus? translates into English as “Where are we going?” When I ponder where data quality is going, and whether data quality is a journey or a destination, I am reminded of the words of T.S. Eliot:

“We must not cease from exploration and the end of all our exploring will be to arrive where we began and to know the place for the first time.”

We must not cease from exploring new ways to continuously improve our data quality and continuously put into practice our data governance principles, policies, and procedures, and the end of all our exploring will be to arrive where we began and to know, perhaps for the first time, the value of high-quality data to our enterprise’s continuing journey toward business success.

This post originally appeared at OCDQ Blog.

Advertisement

Comments (4)
I like the short journey metaphor. We need targeted goals and ongong commitment, but beyond seting standards for our quality of work, we can't determine where market dynamics will require our attention past a year or two. Even annual IT budgets are becoming harder to manage when demand for information becomes so distributed and elastic.
Posted by Jim E | Tuesday, February 28 2012 at 12:22PM ET
Thanks for your comment, Jim.

Yes, data quality, just like every other aspect of the constantly changing business world, requires a continuous monitoring and continuous improvement mindset. We can't predict what will happen tomorrow, which is precisely why we can't plan and prepare as if we could. We have to follow what works for as long as it works without being afraid to adjust as necessary when circumstances inevitably change.

Best Regards,

Jim

Posted by Jim H | Tuesday, February 28 2012 at 4:41PM ET
Business succeed (or at least stay afloat) despite mismanagement, corruption, and other inefficiencies all the time. Seems like everything is a "journey" if it just means the business works at making things better. The only real "destination" might be selling it off or going public - letting the next person/company continue that journey.
Posted by Robert W | Wednesday, February 29 2012 at 11:03AM ET
I think this is best summed up as 'Survival of the fit' as opposed to 'survival of the fittest' as far as data quality is concerned. Also given the high cost of data quality solutions from a traditional IT point of view keeps business and IT execs from wanting to tackle the problem. Since we knew that there was resistance to data quality initiatives on our current ERP data we started with our external sales/marketing leads data. Deduplicating leads, cross referencing current customer with large database lists to identify good prospects. We found the effort paid for itself in a day but more importantly convinced the doers and leaders that data quality is important. Note we didn't use one of the huge providers to start this off but a company called data ladder which was cheap enough to get things moving with no big approvals needed.

data quality tools

data ladder

Posted by Jon B | Wednesday, April 04 2012 at 8:21AM 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.

Blog Archive for Jim Harris

Pondering a Big Data Philosophy
Galileo, the Hubble and Clear Data Insight
When Poor Data Quality Lands on the Ledger
Poor Data Quality That Kills
Data Quality and the OK Plateau

More from Jim Harris »

Blog Index »

Where do young IT professionals (30 and under) obtain information to aid with daily role responsibilities and career development?

Trade publication websites 14%
Social media 23%
Vendor websites 4%
Vendor/community forums 7%
Newsletters 1%
Trade conferences/meetups 2%
RSS feeds 6%
Web search 44%

 

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.