<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Warning: Data Quality Improvement Can Seriously Damage Your Business</title>
	<atom:link href="http://www.dataflux.com/dfblog/?feed=rss2&#038;p=1883" rel="self" type="application/rss+xml" />
	<link>http://www.dataflux.com/dfblog/?p=1883</link>
	<description></description>
	<lastBuildDate>Thu, 09 Sep 2010 19:04:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dylan Jones</title>
		<link>http://www.dataflux.com/dfblog/?p=1883&#038;cpage=1#comment-2243</link>
		<dc:creator>Dylan Jones</dc:creator>
		<pubDate>Mon, 08 Feb 2010 16:27:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.dataflux.com/dfblog/?p=1883#comment-2243</guid>
		<description>@Garnie: I agree it&#039;s tough, particularly in larger organisations obviously, to identify all of these downstream information flows. The key is to have a fallback or parallel running option if at all possible but even this becomes problematic when issues are spotted weeks or even months after the event.

@Phil: Point 2 is a really common problem, totally agree, if you don&#039;t create rules or processes to suit all the recipients then a &quot;local rules&quot; mentality will prevail and they&#039;ll just revert all your good work.

Many thanks for your comments guys, appreciated as ever.</description>
		<content:encoded><![CDATA[<p>@Garnie: I agree it&#8217;s tough, particularly in larger organisations obviously, to identify all of these downstream information flows. The key is to have a fallback or parallel running option if at all possible but even this becomes problematic when issues are spotted weeks or even months after the event.</p>
<p>@Phil: Point 2 is a really common problem, totally agree, if you don&#8217;t create rules or processes to suit all the recipients then a &#8220;local rules&#8221; mentality will prevail and they&#8217;ll just revert all your good work.</p>
<p>Many thanks for your comments guys, appreciated as ever.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Simon</title>
		<link>http://www.dataflux.com/dfblog/?p=1883&#038;cpage=1#comment-2207</link>
		<dc:creator>Phil Simon</dc:creator>
		<pubDate>Fri, 05 Feb 2010 16:24:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.dataflux.com/dfblog/?p=1883#comment-2207</guid>
		<description>Dylan

I enjoyed reading this. I think that you have proven the futility of the &quot;rogue data warrior&quot; concept.  

I too have felt the pain of single-handedly attempting to cleanse organizational data, only to find out that:

1. my fix broken someone else&#039;s (broken) process
2. others had taken steps to recontaminate my purified data

Your post underscores the need for senior and organization-wide commitment.

There&#039;s only so much that one can do.</description>
		<content:encoded><![CDATA[<p>Dylan</p>
<p>I enjoyed reading this. I think that you have proven the futility of the &#8220;rogue data warrior&#8221; concept.  </p>
<p>I too have felt the pain of single-handedly attempting to cleanse organizational data, only to find out that:</p>
<p>1. my fix broken someone else&#8217;s (broken) process<br />
2. others had taken steps to recontaminate my purified data</p>
<p>Your post underscores the need for senior and organization-wide commitment.</p>
<p>There&#8217;s only so much that one can do.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Garnie Bolling</title>
		<link>http://www.dataflux.com/dfblog/?p=1883&#038;cpage=1#comment-2203</link>
		<dc:creator>Garnie Bolling</dc:creator>
		<pubDate>Fri, 05 Feb 2010 15:17:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.dataflux.com/dfblog/?p=1883#comment-2203</guid>
		<description>Dylan, thanks so much for your insight... I like your analogy of a flowing river, and picking up pollution that carries through organizations.  

I have yet to find a solution in finding those hidden pockets of business units that will be impacted by changes to the processes / rules or formats.  I just plan for them... telling the sponsor, expect a few phone calls, and let me help. 

One situation proved to be very helpful, when a team of attorneys called and asked why things have changed, we shared why. Well, they like the change, and helped communicate with other organizations who leverage the old set of rules.  So another win for the &quot;Collaboration Effort.&quot;

Appreciate the facts on rules for prospect data. I will keep that in mind... dont need to lose any percentage of prospects due to upstream data rules.</description>
		<content:encoded><![CDATA[<p>Dylan, thanks so much for your insight&#8230; I like your analogy of a flowing river, and picking up pollution that carries through organizations.  </p>
<p>I have yet to find a solution in finding those hidden pockets of business units that will be impacted by changes to the processes / rules or formats.  I just plan for them&#8230; telling the sponsor, expect a few phone calls, and let me help. </p>
<p>One situation proved to be very helpful, when a team of attorneys called and asked why things have changed, we shared why. Well, they like the change, and helped communicate with other organizations who leverage the old set of rules.  So another win for the &#8220;Collaboration Effort.&#8221;</p>
<p>Appreciate the facts on rules for prospect data. I will keep that in mind&#8230; dont need to lose any percentage of prospects due to upstream data rules.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
