<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.7" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: What question does this answer?</title>
	<link>http://www.proteanit.com/b/2009/07/24/what-question-does-this-answer/</link>
	<description>pro·te·an   (prō'tē-ən, prō-tē'-)  "Exhibiting considerable versatility or diversity"</description>
	<pubDate>Fri, 30 Jul 2010 20:54:46 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.7</generator>

	<item>
		<title>by: BI Monkey</title>
		<link>http://www.proteanit.com/b/2009/07/24/what-question-does-this-answer/#comment-24637</link>
		<pubDate>Mon, 27 Jul 2009 00:18:24 +0000</pubDate>
		<guid>http://www.proteanit.com/b/2009/07/24/what-question-does-this-answer/#comment-24637</guid>
					<description>My first significant BI project is a good case for this. I was a techy person put in to "sort out" the reporting. There were huge problems - data was suspect, existing reports were inconsistent, mainframe developers were long gone. 

So I solved the technical problems. Data was cleansed, reconciled and reliable, and we had decent ETL, OLAP and tools. And when any attempt to access the data left my department, it failed. 

I had failed to grasp just how data illiterate the rest of the company was. So I had built a beautiful, flexible system that was easy to understand -  from my point of view. I had overestimated the users and underestimated the "sales" effort required to get them to even *think* about data.

In hindsight, one of my most useful lessons learned in my career. Shame I didn't grasp it until a few years after I was out of that role!</description>
		<content:encoded><![CDATA[<p>My first significant BI project is a good case for this. I was a techy person put in to &#8220;sort out&#8221; the reporting. There were huge problems - data was suspect, existing reports were inconsistent, mainframe developers were long gone. </p>
<p>So I solved the technical problems. Data was cleansed, reconciled and reliable, and we had decent ETL, OLAP and tools. And when any attempt to access the data left my department, it failed. </p>
<p>I had failed to grasp just how data illiterate the rest of the company was. So I had built a beautiful, flexible system that was easy to understand -  from my point of view. I had overestimated the users and underestimated the &#8220;sales&#8221; effort required to get them to even *think* about data.</p>
<p>In hindsight, one of my most useful lessons learned in my career. Shame I didn&#8217;t grasp it until a few years after I was out of that role!
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
