<?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: Winning the Three-Legged Race: Keys to Interdisciplinary Teamwork</title>
	<atom:link href="http://www.juliediamond.net/blog/winning-the-one-legged-race-keys-to-interdisciplinary-teamwork/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.juliediamond.net/blog/winning-the-one-legged-race-keys-to-interdisciplinary-teamwork/</link>
	<description>Thoughts on Leadership Development, Learning and Change</description>
	<lastBuildDate>Sun, 05 Feb 2012 06:55:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Jude Morton</title>
		<link>http://www.juliediamond.net/blog/winning-the-one-legged-race-keys-to-interdisciplinary-teamwork/comment-page-1/#comment-11</link>
		<dc:creator>Jude Morton</dc:creator>
		<pubDate>Sat, 30 Jan 2010 17:48:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.juliediamond.net/blog/?p=214#comment-11</guid>
		<description>Julie,
You are describing my profession, so I find this very interesting. As a business software analyst, my job is to facilitate detailed, goal-oriented communication between purchasers of a large industrial software system and the vendor (my employer). I have to identify gaps and help define workable solutions. Your points are spot on. Re: point 1 - be flexible, and willing to adapt what you think the solution is within the framework of what is actually possible. 2 - if the end users are not in the room you will have to do this all over again with them. 3 - literally multi-lingual, and also respectful of regional and national differences in business models. 4- accept the 80 percent solution; it&#039;s good enough to build on. 5 - make it work or you will all meet again in the unemployment line. A complicating factor is &quot;ghosts&quot; - stakeholders not in the room, e.g. trading partners, whose purported interests are represented by those present as justifications. (Of course all process work principles apply...) I could go on and on... Thanks again !</description>
		<content:encoded><![CDATA[<p>Julie,<br />
You are describing my profession, so I find this very interesting. As a business software analyst, my job is to facilitate detailed, goal-oriented communication between purchasers of a large industrial software system and the vendor (my employer). I have to identify gaps and help define workable solutions. Your points are spot on. Re: point 1 &#8211; be flexible, and willing to adapt what you think the solution is within the framework of what is actually possible. 2 &#8211; if the end users are not in the room you will have to do this all over again with them. 3 &#8211; literally multi-lingual, and also respectful of regional and national differences in business models. 4- accept the 80 percent solution; it&#8217;s good enough to build on. 5 &#8211; make it work or you will all meet again in the unemployment line. A complicating factor is &#8220;ghosts&#8221; &#8211; stakeholders not in the room, e.g. trading partners, whose purported interests are represented by those present as justifications. (Of course all process work principles apply&#8230;) I could go on and on&#8230; Thanks again !</p>
]]></content:encoded>
	</item>
</channel>
</rss>

