DataFlux - The Leader in Data Quality and Data Integration
  1. #1 by Phil Simon at July 21st, 2010

    Great post, Jim.

    “Human behavior,” according to Beth, “is both the root cause and the solution. Technology doesn’t cause or solve the data quality challenge. Rather, it’s a tool that exacerbates or aids human behavior in either direction.”

    Very well put.

    I also have found it puzzling when organizations use technology to deal with what are fundamentally people issues. Part of me wants to blame ambitious software vendors but, let’s be honest, they can’t shoulder all of it. Organizations themselves need to shoulder a good chunk of the burden for failed technology projects. There’s no such thing as a perfect or error-proof systems. CIOs ought to know as much.

  2. #2 by Monis Iqbal at July 21st, 2010

    Again very nicely written, you always take full marks on that part :)
    I think everyone would agree with the “people first” view. My question is which people in the organization? the ones who are running it? ones responsible for data? …
    I’m asking this because people change in an organization and this means if the ones managing the data are like-minded and care for data quality, when they leave the organization do they also leave their data quality vision with them? Isn’t the solution here is “process” rather than “people” in an organization?

  3. #3 by Jim Harris at July 21st, 2010

    Thanks Phil and Monis for “joining” the Data Transcendental Club!

    :-)

    @Phil – Yes, in my experience, organizations tend to blame failed technology projects on the wrong technology being used. A better technology is sought, magically found, and then history slowly and expensively repeats itself. This doesn’t mean that technology is never to blame, but as you have previously noted, technology in no way obviates the need for people to continue to be involved.

    @Monis – You make an excellent point, and I agree that well developed processes are important for many reasons, including alleviating the risk associated with people leaving the organization or changing their roles within the organization. However, a process doesn’t create, maintain, or continually improve itself. People still need to be involved. Exactly who and exactly what their responsibilities are will change over time. However, I have witnessed too many organizations assume that after they have implemented a technology or a process, the people aspect of it is over–which, in my experience, only creates a disaster waiting to happen.

(will not be published)
  1. No trackbacks yet.