<?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: Interpretive Management</title>
	<atom:link href="http://kipthinks.com/2008/04/interpretive-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://kipthinks.com/2008/04/interpretive-management/</link>
	<description>a place of reflection and inquiry during my doctoral studies</description>
	<lastBuildDate>Sat, 08 Jan 2011 16:55:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Notes To Myself &#124; kipum lee &#124; kipthinks.com</title>
		<link>http://kipthinks.com/2008/04/interpretive-management/comment-page-1/#comment-220</link>
		<dc:creator>Notes To Myself &#124; kipum lee &#124; kipthinks.com</dc:creator>
		<pubDate>Sun, 21 Dec 2008 01:43:28 +0000</pubDate>
		<guid isPermaLink="false">http://kipthinks.com/?p=12#comment-220</guid>
		<description>[...] 2. &#8220;Participatory Design&#8221; and &#8220;Experience Prototyping&#8221; are attitudinal rather than procedural/prescriptive methods [by Forlizzi]. Probably the same way &#8220;attitude&#8221; is used by Boland &amp; Collopy when they describe design attitude v. decision attitude in Managing as Designing [see previous post] [...]</description>
		<content:encoded><![CDATA[<p>[...] 2. &#8220;Participatory Design&#8221; and &#8220;Experience Prototyping&#8221; are attitudinal rather than procedural/prescriptive methods [by Forlizzi]. Probably the same way &#8220;attitude&#8221; is used by Boland &amp; Collopy when they describe design attitude v. decision attitude in Managing as Designing [see previous post] [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kyle</title>
		<link>http://kipthinks.com/2008/04/interpretive-management/comment-page-1/#comment-22</link>
		<dc:creator>Kyle</dc:creator>
		<pubDate>Wed, 01 Oct 2008 04:02:53 +0000</pubDate>
		<guid isPermaLink="false">http://kipthinks.com/?p=12#comment-22</guid>
		<description>I&#039;d say that the nature of conversation is one of productive tension. As such, this can occur within your head if you are wrestling with the tension of two ideas, but it is more likely to occur between two or more individuals with different viewpoints. 

Many exchanges that we consider conversations actually present no conflict or disagreement between the parties involved. But when a conversation begins with a disagreement and works through that tension to a resolution which includes aspects of both sides in a new relationship it feels like magic. 

I think we experience this a lot in design grad school. People with strong but different opinions are placed on a team and asked to solve some sort of ambiguous and huge wicked problem, in a semester. There are so many points of tension in that situation resulting in the long crazy discussions. I think maintaining a team and an environment which can support this type of stuff in the business world is incredibly difficult, but doable if you can get people to trust you when things are super-fuzzy and vague on the front end.</description>
		<content:encoded><![CDATA[<p>I&#8217;d say that the nature of conversation is one of productive tension. As such, this can occur within your head if you are wrestling with the tension of two ideas, but it is more likely to occur between two or more individuals with different viewpoints. </p>
<p>Many exchanges that we consider conversations actually present no conflict or disagreement between the parties involved. But when a conversation begins with a disagreement and works through that tension to a resolution which includes aspects of both sides in a new relationship it feels like magic. </p>
<p>I think we experience this a lot in design grad school. People with strong but different opinions are placed on a team and asked to solve some sort of ambiguous and huge wicked problem, in a semester. There are so many points of tension in that situation resulting in the long crazy discussions. I think maintaining a team and an environment which can support this type of stuff in the business world is incredibly difficult, but doable if you can get people to trust you when things are super-fuzzy and vague on the front end.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

