In his blog post “Data Quality and The Middle Way” on the Data Flux Community of Experts, Jim Harris states ‘Data quality practitioners must learn to strive for continuous improvement, but without losing themselves in an ideal such as data perfection’
I couldn’t agree more, striving for continuous improvement should be the ongoing goal for any data governance initiative.
It is too often that data governance initiatives focus purely on the initial goals and deliverables, and forget about planning for continuous improvement. Once the project manager leaves and the team is disbanded, with no continued monitoring and measurement in place, the initial successes are wiped out as the in-life deployment flounders in a sea of change and static advancement.
Deploying a process and structure of active monitoring and measurement, with defined responsibility and accountability, will ensure continued success for any data governance initiative. Furthermore, by ensuring a culture and framework for continuous improvement the initiatives will grow and continue to deliver over and above initial expectations.
What is Continuous Improvement
There is no set framework for continuous improvement. Traditionally it comes as a product of a business improvement or performance management program. A continuous improvement framework needs to fit your organization and align with your goals and ambitions, it is not something that can be bought off the shelf.
My favorite definition of Continuous Improvement is:
“A structured measurement driven process that continually reviews and improves performance.”
Breaking that definition down, we can identify that we need to deliver something which continually drives business improvement through a structured, measurement driven process. Looking at like this provides a number of main focus points for a continuous improvement framework.
I prefer to focus on three of them, being:
- Structure
- Measurement
- Continuous Review
Structure
The diagram below (from the UK Audit Commission) shows the typical steps in translating strategy performance measures through a business improvement model.
Having a defined approach, like this, to your performance measurement and improvement allows for structure and control, with what I think are the key products namely responsibility and accountability.
The fact that performance management impacts more on your staff than any other resource, them knowing who is responsible and accountable for each point in the data governance process is essential to successful in-life management, control and improvement.
Measurement
In a previous blog post on ‘Data Governance at the Front Line’ I concluded that:
“Data ownership needs to be part of the psyche of every employee, make it part of their incentives, set it as a key KPI in the performance management of the organization”
Which aligns with another phrase I like and often use:
“You can’t change what you don’t measure!”
The key word here is ‘Measure’. Measurement is a vital factor in driving change and improvement in any business process or initiative. However before we set any KPI’s we need to understand what we are measuring, we do this by translating business strategy into performance measures and targets.
The dimensions you measure must be relevant to your environment, don’t measure what you don’t need but you must measure everything you do need. (That sounds like something Confucius could have said …)
From a data governance point of view I like to focus on areas grouped into
- Data Availability
- Data Accuracy
- Data Reliability
Once the dimensions you wish to measure are defined and agreed, you can then ‘KPI’ them, set goals for each measurement, define the thresholds that define success and failure, and then identify ‘owners’ of each KPI.
Defining the owners is one of the important success factors here, ensuring that each KPI is aligned to a relevant owner, someone who is ultimately responsible, and capable of ensuring successful delivery to that KPI is essential.
With clear KPI’s identified and communicated we can start to look at how Continuous Improvement comes in to effect.
Continuous Review
Having structure and defined measurements in place is great, but this is not the end product, the structure needs to define a process and embed a culture of continuous review. Without this continuous review monitoring will eventually cease, causing the improvement process to stall.
I find that this process needs to be “enforced” it is natural for resources to focus on what is new, all the exciting development work. People need to be made responsible for the management of the review process, with set review periods. Resources and their management also need to carry out their own informal reviews on an informal basis. It is a great help to build dashboards and exception reporting to automate as much of the measurement as possible, providing real-time notification when KPI’s are being met or not.
It is continuous review that drives continuous improvement.
Final Word
This is an extensive topic, one that I have only touched on here. I would like to hear your stories on how you are or have implemented a continuous improvement culture in your data management organization. Feel free to let me know.
I will leave you with one of my favorite examples of where continuous improvement was implemented at the front line:
A large global fast food organization had a ‘Data Quality Ladder’ that matched all their stores against each other based on the level of quality data entered through their POS system. These stores were KPI’d against where they came on that ladder. The result was constant competition to try and get to the top of the ladder.
Continuous improvement at its best!



Excellent post Charles,
I definitely agree that far too many initiatives have a “declare victory and walk away” mentality, whereby the assembled project team disbands and returns to their normal daily activities.
Therefore, I really like the continuous improvement framework you have outlined, and especially the provided example of the “Data Quality Ladder.”
All too often, it is more like “Data Quality Chutes and Ladders” – one of the classic children’s board games I enjoyed in my youth (ah, the nostalgic simplicity of board games, but I digress) – where variously setbacks beset progress because instead of continuous improvement, organizations executive disconnected one-off projects to deal with data issues when they become too big to ignore – and upon completion of the latest project, they believe “now we are all done with that data quality stuff.”
Cheers,
Jim
Thanks for the great comment Jim, I like your “Data Quality Chutes and Ladders” analogy. I knew that game as ‘Snaked and Ladders’, maybe using that as an analogy would have the wrong connotations …
Charles,
Another excellent post.
I think another key factor is engagement – data quality improvement activities (and sustaining quality) should be seen by all staff as part of their role. This requires clear communication on expectations and responsibilities backed up by ongoing communication processes.
One electricity company has been using an ongoing, multi-faceted communication process to explain the need for data quality improvements to staff which has been ongoing for 18 months and is planned to continue to ensure that the message does not get forgotten.
I fully agree with the comments on measurement and continuous improvement. A transport company I have been working with have instigated performance dashboards related to a data improvement project where each unit is ranked against all the others. The outputs are then published on the intranet, so those towards the bottom of the table have an incentive to improve.
I was amused by the phrase in your third para “static advancement” which sounds like a contradiction, but I think I got the meaning.
Thanks for your excellent comment Julian. I agree engagement and the ongoing communication of expectations and responsibilities is another key factor. It is great to see real life examples of where this is working.
I was wondering if someone would pick up on the “static advancement”. I was taking a bit of ‘poetic licence’ there.
Cheers
Charles
Charles,
Thanks for a nice post. This is indeed a vast topic. I have blogged about some aspects of this topic on my blog as well.
I believe that to be able to inject data quality consideration in every aspect of data capture that business does, we have to propose a financial model around value of the data and its quality to the business. Once we put a monitory value on the data and its quality…. It will become imperative to track ownership and quality of data being captured. Far too many times we have seen businesses repeat same mistakes and not monitor ongoing/continuous data quality/metrics.
In your discussion, you provide example of fast food chain and the “Data Quality Ladder”. What if this organization actually figured out $$ value of accurate data (Up-sell, cross sell, favorite items, promotions based on the sales trends etc…) entered through POS system and provided a monitory credit towards certain % of accurate data to the individual stores? This will incentivize each owner of the franchise to train/educate his/her POS employees to enter detailed information.
As organizations start treating data as an asset with monitory value, great deal of efforts will be spent on making sure that risks associated with poor quality (3 factors you identify in the blog) of data are mitigated by ensuring/embedding data quality measurements on a ongoing basis.
My 2 cents
Vish Agashe
http://www.linkedin.com/vishagashe
http://www.twitter.com/vishagashe
Hi Vish
Thank you for your comments, and fine examples. They are a great addition to the topic.
Well worth your 2 cents.
Great post, Charles.
I agree with the need for continuous improvement but would like to focus for a moment on Julian’s comment. Engagement, commitment, and accountability are really important factors on these types of things as I have seen throughout my years.
I agreed much of with Jim’s post, a scathing rebuttal of my own:
http://www.dataflux.com/dfblog/?p=1403
I jest. The point that I was trying to make was pretty simple: During new system implementations, it’s a unique opportunity to change the culture, to shake things up, and to say “We’re not gonna take it.”
Sorry, I was channeling my inner Dee Snider.
Where was I?
Oh yeah. If you tell people that mediocrity isn’t going to be tolerated anymore, then continuous improvement can still take place. If you don’t, then you’ll have the same DQ issues immediately after the fact.
On my last gig, there were data issues days after going live.
It’s a sad state of affairs.
Enough rambling.
ps
Thanks for your comments Phil,
Agree 100%, mediocrity should not and will not be tolerated!!
BTW I’ve not heard the name Dee Snider mentioned in ages. Rock on baby!!!!
Charles, excellent post: The continuous improvement model in data governance. The day to day maintenance of data is usually not a priority until equipment is down because a spare part not in inventory or warranty is not recognized due incomplete data information.
From my experience, Master Data Management should be a standard requirement of the business process. Working with large manufacturers, the amount of new data introduced into the engineering / purchasing / maintenance is astounding. I categorize the procedures to process data into three buckets: new, active legacy and non active legacy, each category requires a different data cleansing and set up process as the data affects each department differently. Once the processes are set up the cost avoidance saving in time, process, controlled ordering, parts sharing, etc are extremely beneficial. The processes from the user perspective should be simple and non-intrusive to core business.
Charles,
I wrote an article on this topic for the IAIDQ Newsletter a while back. http://iaidq.org/publications/obrien-2008-04.shtml
Oops.. hit return too early there…
I meant to say that your post is excellent and echoes a lot of the points I was making back in 2008 when I wrote about the long tail of risk and the need to keep incrementally improving to prevent yourself slipping backwards in Information Quality and Data Governance terms.
Jackie,
Thank you for your comments and real life examples. I agree, MDM should be a standard requirements of the business process. As I’ve said before, MDM should be part of your organizational DNA.
Daragh
Thanks for your comments (both of them
) Incremental improvement is a fine way to define how MDM or any DQ initiative should be approached. No ‘big bang’ approach but constant improvement in line with business growth and change.
Cheers
Charles