<?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: Define your terms or face the consequences</title>
	<atom:link href="http://www.jacksonwightman.com/2010/02/define-your-terms-or-face-the-consequences/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jacksonwightman.com/2010/02/define-your-terms-or-face-the-consequences/</link>
	<description>Carrying out the revolution</description>
	<lastBuildDate>Fri, 03 Feb 2012 15:05:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Jackson Wightman</title>
		<link>http://www.jacksonwightman.com/2010/02/define-your-terms-or-face-the-consequences/comment-page-1/#comment-37</link>
		<dc:creator>Jackson Wightman</dc:creator>
		<pubDate>Wed, 03 Feb 2010 20:52:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.jacksonwightman.com/?p=253#comment-37</guid>
		<description>Hey Justin,

Thanks. 

I saw your post that touched on how sometimes in biz it can be good to have a supplier who you can extract a lot from. Totally agree - and like you I&#039;ve been on both sides (exploiter and exploited). My rule if I am the vendor is to try and spell out scope of work with greatest possible precision (and also delineate what happens if scope is exceeded - e.g. more cash etc). The downside of unclarity is scope creep out the yin yang from my experience.

Re your pt about the burden of clarity being on the listener, I think this is why practicing reflective listening is SO very important in business and a great communications technique no matter where one sits in an organization or biz relationship.</description>
		<content:encoded><![CDATA[<p>Hey Justin,</p>
<p>Thanks. </p>
<p>I saw your post that touched on how sometimes in biz it can be good to have a supplier who you can extract a lot from. Totally agree &#8211; and like you I&#8217;ve been on both sides (exploiter and exploited). My rule if I am the vendor is to try and spell out scope of work with greatest possible precision (and also delineate what happens if scope is exceeded &#8211; e.g. more cash etc). The downside of unclarity is scope creep out the yin yang from my experience.</p>
<p>Re your pt about the burden of clarity being on the listener, I think this is why practicing reflective listening is SO very important in business and a great communications technique no matter where one sits in an organization or biz relationship.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Kownacki</title>
		<link>http://www.jacksonwightman.com/2010/02/define-your-terms-or-face-the-consequences/comment-page-1/#comment-36</link>
		<dc:creator>Justin Kownacki</dc:creator>
		<pubDate>Wed, 03 Feb 2010 18:13:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.jacksonwightman.com/?p=253#comment-36</guid>
		<description>Sometimes people prefer vague terms, so it leaves more room for interpretation.  If you can convince a client to pay you to do &quot;community outreach&quot; and THEY don&#039;t ask you to specify what you&#039;re specifically referring to, it gives you free reign.  Whereas, if you&#039;re TOO specific, your ability to improvise is constricted -- and perhaps it should be.

I believe in the specificity of words, and I also appreciate creative interpretations thereof.  It&#039;s a tricky balance, and as long as we make room for variations, we&#039;ll always run the risk of miscommunication.  In the end, the burden of clarity must be on the listener, to make sure s/he&#039;s hearing what s/he thinks s/he&#039;s hearing.</description>
		<content:encoded><![CDATA[<p>Sometimes people prefer vague terms, so it leaves more room for interpretation.  If you can convince a client to pay you to do &#8220;community outreach&#8221; and THEY don&#8217;t ask you to specify what you&#8217;re specifically referring to, it gives you free reign.  Whereas, if you&#8217;re TOO specific, your ability to improvise is constricted &#8212; and perhaps it should be.</p>
<p>I believe in the specificity of words, and I also appreciate creative interpretations thereof.  It&#8217;s a tricky balance, and as long as we make room for variations, we&#8217;ll always run the risk of miscommunication.  In the end, the burden of clarity must be on the listener, to make sure s/he&#8217;s hearing what s/he thinks s/he&#8217;s hearing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

