<?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: Why the term &#8216;communication problem&#8217; insults your team members and retards the performance of your organization</title>
	<atom:link href="http://www.salesprocessengineering.net/2009/07/25/why-the-term-communication-problem-insults-your-team-members-and-retards-the-performance-of-your-organization/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.salesprocessengineering.net/2009/07/25/why-the-term-communication-problem-insults-your-team-members-and-retards-the-performance-of-your-organization/</link>
	<description>The application of process-engineering principles (particularly TOC) to the sales process</description>
	<lastBuildDate>Wed, 18 Jan 2012 22:26:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Sales Process Engineering &#187; Blog Archive &#187; How to get the most out of Manufacturer&#8217;s Reps (and distributors)</title>
		<link>http://www.salesprocessengineering.net/2009/07/25/why-the-term-communication-problem-insults-your-team-members-and-retards-the-performance-of-your-organization/comment-page-1/#comment-681</link>
		<dc:creator>Sales Process Engineering &#187; Blog Archive &#187; How to get the most out of Manufacturer&#8217;s Reps (and distributors)</dc:creator>
		<pubDate>Fri, 08 Jan 2010 20:40:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.salesprocessengineering.net/2009/07/25/why-the-term-communication-problem-insults-your-team-members-and-retards-the-performance-of-your-organization/#comment-681</guid>
		<description>[...] of the fact that formal workflows are required and that these workflows must be designed to eliminate the requirement for the trasfer of anything other than simple information.&#160; The key to doing this effectively is to ensure that any complex workflows are managed by [...]</description>
		<content:encoded><![CDATA[<p>[...] of the fact that formal workflows are required and that these workflows must be designed to eliminate the requirement for the trasfer of anything other than simple information.&nbsp; The key to doing this effectively is to ensure that any complex workflows are managed by [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Communication Problems are actually Process Design Problems &#124; Reach1to1 Technologies</title>
		<link>http://www.salesprocessengineering.net/2009/07/25/why-the-term-communication-problem-insults-your-team-members-and-retards-the-performance-of-your-organization/comment-page-1/#comment-606</link>
		<dc:creator>Communication Problems are actually Process Design Problems &#124; Reach1to1 Technologies</dc:creator>
		<pubDate>Wed, 29 Jul 2009 16:45:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.salesprocessengineering.net/2009/07/25/why-the-term-communication-problem-insults-your-team-members-and-retards-the-performance-of-your-organization/#comment-606</guid>
		<description>[...] Justin Roff-Marsh, proponent of his highly effective Sales Process Engineering methodology that incorporates the techniques from Theory of Constraints into the sales process &#8211; has written an excellent article on his Sales Process Engineering blog, where he explains &#8220;Why the term ‘communication problem’ insults your team members and retards the performance of yo...&#8220;. [...]</description>
		<content:encoded><![CDATA[<p>[...] Justin Roff-Marsh, proponent of his highly effective Sales Process Engineering methodology that incorporates the techniques from Theory of Constraints into the sales process &#8211; has written an excellent article on his Sales Process Engineering blog, where he explains &#8220;Why the term ‘communication problem’ insults your team members and retards the performance of yo&#8230;&#8220;. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Malcolm Ryder</title>
		<link>http://www.salesprocessengineering.net/2009/07/25/why-the-term-communication-problem-insults-your-team-members-and-retards-the-performance-of-your-organization/comment-page-1/#comment-604</link>
		<dc:creator>Malcolm Ryder</dc:creator>
		<pubDate>Sun, 26 Jul 2009 19:45:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.salesprocessengineering.net/2009/07/25/why-the-term-communication-problem-insults-your-team-members-and-retards-the-performance-of-your-organization/#comment-604</guid>
		<description>Hi Justin. Nice bit.

Just for the sake of commentary: I think there are some fine points to your great observation.

1. Complex information can be handed off. Translation may be necessary. Information transformation is not the same thing as information loss. In fact, a key thing to understand is that users of Information Type X may add, modify and delete *data* in order to produce Information Type Y, with nothing &quot;lost&quot; that is important to a process.

2. In Example A, I think you&#039;re describing the need for an architect. This is not the same as a project leader. A project leader is a production manager. An architect is an analyst/designer. It&#039;s the architect that does the translation of Info Type X to Info Type Y.

3. In example B, your punchline is really great. You would want your consultants to acquire the skillsets for requirements analysis and use case definition. The developers understand that handoff, even if it is complex information.

My own punchline here is a personal favorite: complexity and complication are not the same thing. Complication you want to get rid of, in general; whereas, many extremely valuable things to have or do cannot exist without complexity. When something complex is valuable and needed, you don&#039;t want it to be replaced or obscured by something complicated...</description>
		<content:encoded><![CDATA[<p>Hi Justin. Nice bit.</p>
<p>Just for the sake of commentary: I think there are some fine points to your great observation.</p>
<p>1. Complex information can be handed off. Translation may be necessary. Information transformation is not the same thing as information loss. In fact, a key thing to understand is that users of Information Type X may add, modify and delete *data* in order to produce Information Type Y, with nothing &#8220;lost&#8221; that is important to a process.</p>
<p>2. In Example A, I think you&#8217;re describing the need for an architect. This is not the same as a project leader. A project leader is a production manager. An architect is an analyst/designer. It&#8217;s the architect that does the translation of Info Type X to Info Type Y.</p>
<p>3. In example B, your punchline is really great. You would want your consultants to acquire the skillsets for requirements analysis and use case definition. The developers understand that handoff, even if it is complex information.</p>
<p>My own punchline here is a personal favorite: complexity and complication are not the same thing. Complication you want to get rid of, in general; whereas, many extremely valuable things to have or do cannot exist without complexity. When something complex is valuable and needed, you don&#8217;t want it to be replaced or obscured by something complicated&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack Vinson</title>
		<link>http://www.salesprocessengineering.net/2009/07/25/why-the-term-communication-problem-insults-your-team-members-and-retards-the-performance-of-your-organization/comment-page-1/#comment-602</link>
		<dc:creator>Jack Vinson</dc:creator>
		<pubDate>Sun, 26 Jul 2009 01:27:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.salesprocessengineering.net/2009/07/25/why-the-term-communication-problem-insults-your-team-members-and-retards-the-performance-of-your-organization/#comment-602</guid>
		<description>Thanks, Justin.  I completely agree with the sentiment that if we leave the blame at something we think we can&#039;t control, then we leave ourselves open to that problem again and again.  

I had an entertaining comment from a client recently, where &quot;communication&quot; has been a question.  He &quot;discovered&quot; that the project wasn&#039;t much more than a means to improve communication in the organization.</description>
		<content:encoded><![CDATA[<p>Thanks, Justin.  I completely agree with the sentiment that if we leave the blame at something we think we can&#8217;t control, then we leave ourselves open to that problem again and again.  </p>
<p>I had an entertaining comment from a client recently, where &#8220;communication&#8221; has been a question.  He &#8220;discovered&#8221; that the project wasn&#8217;t much more than a means to improve communication in the organization.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: clarke chign</title>
		<link>http://www.salesprocessengineering.net/2009/07/25/why-the-term-communication-problem-insults-your-team-members-and-retards-the-performance-of-your-organization/comment-page-1/#comment-601</link>
		<dc:creator>clarke chign</dc:creator>
		<pubDate>Sat, 25 Jul 2009 08:57:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.salesprocessengineering.net/2009/07/25/why-the-term-communication-problem-insults-your-team-members-and-retards-the-performance-of-your-organization/#comment-601</guid>
		<description>Nice work Justin.</description>
		<content:encoded><![CDATA[<p>Nice work Justin.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced

Served from: www.salesprocessengineering.net @ 2012-02-10 17:16:42 -->
