<?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"
	>
<channel>
	<title>Comments on: What&#8217;s a problem?</title>
	<atom:link href="http://www.sitsite.com/blog/2009/02/whats-a-problem/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitsite.com/blog/2009/02/whats-a-problem/</link>
	<description></description>
	<pubDate>Thu, 17 May 2012 15:37:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Fabian Szulanski</title>
		<link>http://www.sitsite.com/blog/2009/02/whats-a-problem/#comment-318</link>
		<dc:creator>Fabian Szulanski</dc:creator>
		<pubDate>Mon, 09 Feb 2009 11:56:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitsite.com/blog/?p=141#comment-318</guid>
		<description>What is interesting about the UDP process is that it takes us away from the "reacting to events" mode, leading to focus on what could be the root causes and also what consequences may appear in the future, related to an original "problem".

And it opens many oppoortunities of intervention, helped by SIT tools and principles. 

As an expansion to UDP, I would also suggest that some of the "so what", could eventually influence some of the "whys". Cause and effect chains might became a causal loop diagram.</description>
		<content:encoded><![CDATA[<p>What is interesting about the UDP process is that it takes us away from the &#8220;reacting to events&#8221; mode, leading to focus on what could be the root causes and also what consequences may appear in the future, related to an original &#8220;problem&#8221;.</p>
<p>And it opens many oppoortunities of intervention, helped by SIT tools and principles. </p>
<p>As an expansion to UDP, I would also suggest that some of the &#8220;so what&#8221;, could eventually influence some of the &#8220;whys&#8221;. Cause and effect chains might became a causal loop diagram.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

