<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Capacity for Language Introduces Uncertainty</title>
	<link>http://www.reformingprojectmanagement.com/2003/11/18/270/</link>
	<description>The magazine for the project age</description>
	<pubDate>Fri, 16 May 2008 18:57:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Garrie hankins
        </title>
		<link>http://www.reformingprojectmanagement.com/2003/11/18/270/#comment-103</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2003/11/18/270/#comment-103</guid>
					<description>
        This thread is very timely.

 I am currently gathering information to write a paper for a college class I am taking on language and society. The subject is on the breakdown of language comprehension between different professionals. 

I am borrowing the Saussure and Sapir – Whorf thesis that Language is developed by social groups to communicate shared concepts. The words and phrases we use develop meaning by group agreement. Only that social in-group fully understands the concept assigned to the words or phrases that express thought. 

I think a big challenge to communications is that in our project teams we have people from several different social groups that are brought together - often for the first time - for a temporary endeavor. Within these groups they have developed their own language and modes of communications. They hold in their linguistic toolbox words and phrases for communicating concepts that the other team members do not share. 

A project team is the forming of a new social group and this group must develop its own agreements that connect words to concepts to effectively communicate. Actively attempting communications, encountering the breakdown and having the patients to attempt repair is the only way the team can accomplish this.

Maybe the things that we can do as project managers are; 

Make the team members aware of this linguistic difference so unexpected breakdowns do not frustrate them. 

Help to develop linguistic bridges between the team members differing words – concept associations. 

Encourage the team members to communicate with each other on a constant and regular bias.

Thanks
      </description>
		<content:encoded><![CDATA[<p>This thread is very timely.</p>
<p> I am currently gathering information to write a paper for a college class I am taking on language and society. The subject is on the breakdown of language comprehension between different professionals. </p>
<p>I am borrowing the Saussure and Sapir – Whorf thesis that Language is developed by social groups to communicate shared concepts. The words and phrases we use develop meaning by group agreement. Only that social in-group fully understands the concept assigned to the words or phrases that express thought. </p>
<p>I think a big challenge to communications is that in our project teams we have people from several different social groups that are brought together - often for the first time - for a temporary endeavor. Within these groups they have developed their own language and modes of communications. They hold in their linguistic toolbox words and phrases for communicating concepts that the other team members do not share. </p>
<p>A project team is the forming of a new social group and this group must develop its own agreements that connect words to concepts to effectively communicate. Actively attempting communications, encountering the breakdown and having the patients to attempt repair is the only way the team can accomplish this.</p>
<p>Maybe the things that we can do as project managers are; </p>
<p>Make the team members aware of this linguistic difference so unexpected breakdowns do not frustrate them. </p>
<p>Help to develop linguistic bridges between the team members differing words – concept associations. </p>
<p>Encourage the team members to communicate with each other on a constant and regular bias.</p>
<p>Thanks
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Hal
        </title>
		<link>http://www.reformingprojectmanagement.com/2003/11/18/270/#comment-104</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2003/11/18/270/#comment-104</guid>
					<description>
        Frank and Laurent make helpful additions.  Frank jumped the gun on me.  I'm working thru what we can do as project mgrs and leaders acknowledging the conditions of our human-ness.

To clarify, I am not saying it is human nature.  For instance, that people don't listen to what others are saying is not the nature.  It is what we are likely to find operating in a situation.  More likely it's just habit.  This might be a quibble.

I share Frank's view that behavior changes through time.  I speak of Humberto Maturana.  He co-authored  the book The Tree of Knowledge.  He's a biologist and philosopher.  Some might also say a cognitive scientist.  Anyway, here's the important lesson for me: changing what we do and who we do it with changes who we are.  It's great news for the PM.  By designing different ways for team members to engage and then seeing that they do engage that way we can bring about a shift in what Frank calls the 'the lowest level of human behavior'.

To Laurent's points, the two models he mentions offer a way of analyzing a conversation, but miss the situational-personal in-the-moment explanation of not speaking and not listening.  I'll share my thoughts on this in a coming posting.  I've been holding back on this, mostly because there's so much to say that requires a foundation for saying it.  I've been considering writing a 10-page paper on it.  Maybe I'll just blog it then put the article together...

Thanks guys! :+:
      </description>
		<content:encoded><![CDATA[<p>Frank and Laurent make helpful additions.  Frank jumped the gun on me.  I&#8217;m working thru what we can do as project mgrs and leaders acknowledging the conditions of our human-ness.</p>
<p>To clarify, I am not saying it is human nature.  For instance, that people don&#8217;t listen to what others are saying is not the nature.  It is what we are likely to find operating in a situation.  More likely it&#8217;s just habit.  This might be a quibble.</p>
<p>I share Frank&#8217;s view that behavior changes through time.  I speak of Humberto Maturana.  He co-authored  the book The Tree of Knowledge.  He&#8217;s a biologist and philosopher.  Some might also say a cognitive scientist.  Anyway, here&#8217;s the important lesson for me: changing what we do and who we do it with changes who we are.  It&#8217;s great news for the PM.  By designing different ways for team members to engage and then seeing that they do engage that way we can bring about a shift in what Frank calls the &#8216;the lowest level of human behavior&#8217;.</p>
<p>To Laurent&#8217;s points, the two models he mentions offer a way of analyzing a conversation, but miss the situational-personal in-the-moment explanation of not speaking and not listening.  I&#8217;ll share my thoughts on this in a coming posting.  I&#8217;ve been holding back on this, mostly because there&#8217;s so much to say that requires a foundation for saying it.  I&#8217;ve been considering writing a 10-page paper on it.  Maybe I&#8217;ll just blog it then put the article together&#8230;</p>
<p>Thanks guys! :+:
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Frank Winters
        </title>
		<link>http://www.reformingprojectmanagement.com/2003/11/18/270/#comment-105</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2003/11/18/270/#comment-105</guid>
					<description>
        Project teams need a glossary of terms specifically defining the terms important to the team. The glossary should grow as the project progresses.

Proposals and other definitional documents also need terms defined within them. Contracts usually have a section to define terms, but then introduces legalistic language that tends to negate the added clarity. A contract should not be the only place to turn for clarity.

I agree that awareness of the probable differing meanings of terms among team members is key. Creation of a true project culture, including terminology will help avoid breakdowns.
      </description>
		<content:encoded><![CDATA[<p>Project teams need a glossary of terms specifically defining the terms important to the team. The glossary should grow as the project progresses.</p>
<p>Proposals and other definitional documents also need terms defined within them. Contracts usually have a section to define terms, but then introduces legalistic language that tends to negate the added clarity. A contract should not be the only place to turn for clarity.</p>
<p>I agree that awareness of the probable differing meanings of terms among team members is key. Creation of a true project culture, including terminology will help avoid breakdowns.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
