It’s human nature to procrastinate. If given the choice of doing something uncomfortable and unfamiliar most of us would rather put it off.
Procrastination
–verb
1. to defer action; delay: to procrastinate until an opportunity is lost.
We see this all the time in business. I can think of one company right now who has procrastinated for 5 years over one data quality project. They know they need to do it. It is strategic, there is no getting around it, they have no choice. To align their business and reap the benefits of a unified services and IT architecture they must move forward.
But they can’t.
They delay and create excuses for why it’s not the right time.
The problem is that it isn’t really a “they” kind of problem. These things generally come down to one person. Sure, in my example above, there are whole steering committees and panels who are procrastinating en masse but ultimately the decision to take action rests with one person.
This is a perennial problem for data quality.
For most companies, particularly those low down on the maturity scale, data quality is uncomfortable and unfamiliar for those who need to make the decision to act. New ways of thinking to learn, new methods to adopt, new software to buy, new skills to teach. All to protect an asset most people assumed was already being effectively managed. So the decision to move forward is a tough one, particularly when it can be easily put off. Serial procrastination soon follows.
But if we take a look at the definition of procrastination at the start of this post we’ll see why taking action is the right decision.
Without action, there is no opportunity.
Back to my case study organisation. Each day, each week, each year they defer the decision to act on data quality they lose more and more opportunities. The opportunity to automate new services that their customers demand. The opportunity to cut capital costs and streamline their workforce. The opportunity to regain the competitive advantage they once possessed.
If you have business critical data that lacks sound data governance and robust data quality controls then things are not suddenly going to get better. The data isn’t going to magically improve itself. The staff are not suddenly going to create a culture of data quality overnight. It will only get worse.
The longer you defer, delay and procrastinate, the harder it will become to regain control. The hole is only going to get deeper.
And when you do make the decision to tackle data quality, you will inevitably make mistakes. People will dig their heels in and fight you all the way. There are no silver bullets. It can be a long, thankless task.
But that doesn’t mean it isn’t the right option for you to take.



#1 by Jim Harris at November 12th, 2009
Brilliant post Dylan,
I believe that the two perilous P’s of data quality are Procrastination and Perfection.
Pursuing either perilous P will result in guaranteed failure.
You can’t afford to procrastinate and once you do get started, you can’t afford to allow the pursuit of perfection to undermine your efforts.
As you said, data quality can be a long, thankless task. However, it is not only the right thing to do, but the necessary thing as well.
Cheers,
Jim
#2 by Charles Blyth at November 12th, 2009
Great post Dylan and comments by Jim.
Too many companies have their heads in the sand on Data Quality, hoping that if they ignore it the problem will go away. Unfortunately, while you have your head in the sand, your competition can walk straight past your without you knowing.
Don’t ignore data quality, face is front on and take on the challenge, it is the only way that you will succeed in today’s climate!
There is another analogy about what happens when you stick you head in the sand, and what you leave sticking up in the air, and firecrackers and the get go, but I will leave it for a different post …
#3 by Dylan Jones at November 13th, 2009
@Jim – you’re right, the other extreme can be almost as damaging. I don’t subscribe to the zero defects route but I know many practitioners do. I also prefer a pragmatic, pareto style approach, certainly until the maturity and governance improves.
@Charles – Thanks for the analogy, far more direct and compelling than mine! You’re spot on about the climate though, now is not the time to cut funding and run for the hills, data quality improvement is an excellent way to improve your competitive performance.
#4 by Ken O'Connor at November 13th, 2009
Hi Dylan,
Great post, and insightful comments by Jim and Charles.
I believe that we Data Quality Professionals need to work together to make “Data Quality By Design” such a “no brainer” that procrastination is not an option.
I have started a line of thought on this in a recent post on my blog called “Lego Blocks and data quality”
See:
http://kenoconnordata.wordpress.com/2009/10/22/lego-blocks-and-data-quality/
Rgds Ken
#5 by Dylan Jones at November 19th, 2009
Cheers Ken, I agree that collectively we can (and must) share experiences on what beats down the doors of procrastination.
You’re an expert in the anti-money laundering space (amongst others) but the patterns of data quality you apply in that discipline are equally applicable to countless other scenarios.
Your analogy brings me on to re-use and another article I’ve got in motion for this forum, how we can build data quality centres within the organisation that spot these patterns and apply them to many different scenarios, dramatically cutting costs.
For example, 3rd party data feeding into an organisation requires the same basic process but we have hordes of different teams and standards in place.
By following your “Lego block” (other plastic building construction sets are available!) analogy we can start to beat procrastination by demonstrating the ROI of re-using these components.
Thanks again for your comment, much appreciated as ever.