Letting B2B Data Die or: How I Learned to Stop Worrying and Ignore the Problem

I had a conversation with a colleague from another company recently. They mentioned a data quality project to clean up old B2B CRM Data.  I had to stop and ask, “Why?” This wasn’t just old data, but really old pre-acquisition data from another source system.

We discussed further and I found that the data in question was sales data from 2006. When it was migrated the database keys were butchered, and many of the relationships were lost. It was going to take  four FTE resources over 6 months to fix the problem. In a bad economy, I just couldn’t justify why any company would spend that effort. My suggestion… Dump the data from the reporting tables. That’s right. Delete it. Archive it for audit purposes, but get it out of the way and focus on today’s problems.

My colleague was shocked. Here I am, a Data Governance expert and Data Quality evangelist telling them to ignore the problem. My reasoning? You need to constantly prioritize your projects. If something is more valuable in terms of revenue, or presents a greater risk, or is a bigger pain to more people, fix that first! Don’t dwell on perfection. You’ll never get there. Just try to make the most improvements you can, as quickly as you can. Grab the low hanging fruit rather than re-planting the tree.

If this offends your data quality sensibilities, please comment. I’m curious to know whether my opinion resonates.