Preventing the “Great DQM Fire”

For German readers: Es gibt eine deutsche Version dieses Blogeintrags.

When dealing with the Middle Ages, there are a lot massive fires that destroy entire cities. An example is the "Great Fire of London" (see Wikipedia article). It lasted four full days in September 1666 and destroyed four fifths of the City of London, including most of the medieval buildings, and resulted in about 100,000 homeless people.


Source: Wikipedia, Great Fire London
Today, there are numerous provisions for fire protection, so that fires occur much less frequently than before. And in the case of a fire, every town and every village has a professional or volunteer fire department that can respond quickly and prevent extensive damage.

This concept can also be applied to the data quality management.

Data Quality Middle Ages

Again and again, problems result from bad data quality. Typically, these issues occur in major projects (eg, data migration or process optimization), changes in personnel or when there is a high visibility to upper management. To achieve its objectives, the project must then take care of the problems in an ad-hoc fashion. After the immediate, pressing problems solved and the projects objectives are achieved, there is no need to introduce a regular DQM. Until the next DQ emergency occurs …

This "ad-hoc DQM" has many negatives, some examples:

  • No single approach, no standard tools
  • Only the main symptoms are eliminated, without resolving the root causes
  • No preventive measures
  • Investment in DQ tools cannot be justified for a single project (either too expensive or too time consuming)
  • DQ issues are handled by various people and departments
  • No predictability of budgets and resources, therefore external support is often needed
  • When new problems occur, everything has to start again from scratch, resulting in high recurrent costs

Modern Era Data Quality

It therefore makes a lot of sense to establish a unit with the main task of regular, active data quality management. The objectives of this unit are to establish a general process, organization and technical platform to continuously monitor and improve of data quality. The relevant aspects will be discussed in further posts.


Posted

in

by

Tags:

Comments

3 responses to “Preventing the “Great DQM Fire””

  1. Steve Sarsfield Avatar

    Yes. In fact, you should look for the fires and start THERE when you see them burning. After a building has burned down, make sure you point out why it happened. You’d be surprised how many people just ignore it and are surprised when it happens again. It’s the responsibility of the data champion to leverage the burning building to get the resources they need for data quality.

    In the words of Ron Bechtold, Chief Data Officer for the US Army, “start with a burning bridge and if necessary create one”

    Justify the costs of data management by solving a critical business issue and that may mean fanning the flames of a known problem to reveal its true impact.

  2. Jim Harris Avatar

    Excellent post Thorsten,

    The “Great DQM Fire” is a great metaphor!

    Sometimes it feels as if we will never see the end of The Data Quality Middle Ages and the prevalence of “ad-hoc DQM” as the emergency response to data quality issues after they have occurred.

    I am looking forward to your future posts that discuss Modern Era Data Quality.

    Best Regards,

    Jim

  3. Thorsten Avatar
    Thorsten

    Steve and Jim,
    thanks for the kind words and helping to paint the picture a bit more.

    I hope that there is a lot more in the metaphor, and it may help serve to make some esoteric concepts a bit easier to grab.

    Looking forward to more comments!

    Thorsten

Leave a Reply

Your email address will not be published. Required fields are marked *