<?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: Dispelling Collaboration Myths: Is Your &#8220;Team&#8221; An Impediment To Content Management Success?</title>
	<atom:link href="http://thecontentwrangler.com/2006/10/18/dispelling_collaboration_myths_is_your_team_an_impediment_to_content_manage/feed/" rel="self" type="application/rss+xml" />
	<link>http://thecontentwrangler.com/2006/10/18/dispelling_collaboration_myths_is_your_team_an_impediment_to_content_manage/</link>
	<description>Content is a business asset worthy of being managed</description>
	<lastBuildDate>Tue, 16 Mar 2010 01:29:18 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Emma</title>
		<link>http://thecontentwrangler.com/2006/10/18/dispelling_collaboration_myths_is_your_team_an_impediment_to_content_manage/comment-page-1/#comment-41</link>
		<dc:creator>Emma</dc:creator>
		<pubDate>Sun, 22 Oct 2006 15:35:56 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/ee/?p=638#comment-41</guid>
		<description>&lt;p&gt;Thank you all for your comments - and criticisms. I knew when I submitted the article that it would trigger debate, but I confess I had no idea that the debate would be of such high quality. Holly&#8217;s concern that a &#8220;barrier-free&#8221; workplace (literally and figuratively) may drive away some writers who cannot - or will not - make the transition, is a legitimate one. I believe that as the profession changes, it will also draw new people to it, who are perhaps better suited to work collaboratively. In the short term, yes, some tech writers may opt to walk away, or work for companies that are more traditional.
&lt;/p&gt;
&lt;p&gt;
In the longer term, I do believe that the increase in the group&#8217;s productivity will more than compensate for the short term drop in personal productivity for some, as writer holmesd suggests. The response from Kristy certainly indicates how quickly things can go down-hill when a collaboration-friendly workplace is suddenly pulled back into the CubeWorld&#8230; Kristy&#8217;s experience is very near proof of my position that until the walls come tumbling down, collaboration will remain a lofty goal.
&lt;/p&gt;
&lt;p&gt;
For Barry, and others like him, who would like to read more on how to foster and encourage collaboration, I can promise you that I intend to deepen the discussion around this particular topic, and share some success stories with the community. There are more barriers to effective collaborative team work, besides physical conditions, and I will present articles on these barriers regularly on The Content Wrangler - stay tuned for more.
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Thank you all for your comments &#8211; and criticisms. I knew when I submitted the article that it would trigger debate, but I confess I had no idea that the debate would be of such high quality. Holly&#8217;s concern that a &#8220;barrier-free&#8221; workplace (literally and figuratively) may drive away some writers who cannot &#8211; or will not &#8211; make the transition, is a legitimate one. I believe that as the profession changes, it will also draw new people to it, who are perhaps better suited to work collaboratively. In the short term, yes, some tech writers may opt to walk away, or work for companies that are more traditional.
</p>
<p>
In the longer term, I do believe that the increase in the group&#8217;s productivity will more than compensate for the short term drop in personal productivity for some, as writer holmesd suggests. The response from Kristy certainly indicates how quickly things can go down-hill when a collaboration-friendly workplace is suddenly pulled back into the CubeWorld&#8230; Kristy&#8217;s experience is very near proof of my position that until the walls come tumbling down, collaboration will remain a lofty goal.
</p>
<p>
For Barry, and others like him, who would like to read more on how to foster and encourage collaboration, I can promise you that I intend to deepen the discussion around this particular topic, and share some success stories with the community. There are more barriers to effective collaborative team work, besides physical conditions, and I will present articles on these barriers regularly on The Content Wrangler &#8211; stay tuned for more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ScottAbel</title>
		<link>http://thecontentwrangler.com/2006/10/18/dispelling_collaboration_myths_is_your_team_an_impediment_to_content_manage/comment-page-1/#comment-40</link>
		<dc:creator>ScottAbel</dc:creator>
		<pubDate>Sun, 22 Oct 2006 11:39:09 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/ee/?p=638#comment-40</guid>
		<description>&lt;p&gt;Thanks for the great comments everyone. We&#8217;ve asked Emma to continue exploring this topic&#8212;including ideas for how to overcome some of the issues our readers have identified. Look for some personal responses from Emma on this page and expect to see more change management articles by Emma on this weblog soon!
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Thanks for the great comments everyone. We&#8217;ve asked Emma to continue exploring this topic&#8212;including ideas for how to overcome some of the issues our readers have identified. Look for some personal responses from Emma on this page and expect to see more change management articles by Emma on this weblog soon!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kristy</title>
		<link>http://thecontentwrangler.com/2006/10/18/dispelling_collaboration_myths_is_your_team_an_impediment_to_content_manage/comment-page-1/#comment-39</link>
		<dc:creator>Kristy</dc:creator>
		<pubDate>Fri, 20 Oct 2006 17:29:41 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/ee/?p=638#comment-39</guid>
		<description>&lt;p&gt;This article is so very true. My workgroup was a collaborative team until end of last year. While we were technically in cubicles, they were essentially in a circle around a central table. It was very easy to discuss policies, procedures, and materials we were working on individually, which spilled over into other materials and work classifications. This was often how we found out about projects that were indirectly related to our tasks. We called it &#8220;stoop time&#8221; when we rolled out and had these informal meetings.
&lt;/p&gt;
&lt;p&gt;
Then we were moved physically to another part of the building, with normal cubes in rows and other Employees. That&#8217;s where we began to fall apart, and we could see it happening. After much discussion, we were able to get half-walls put in between the cubes, so we could at least discuss with our closest neighbors. While this has helped, it is not nearly as collaborative as what we had. There is a definite possessiveness now, which was never there before. The pride we used to have in our group is also gone.
&lt;/p&gt;
&lt;p&gt;
While in the circular environement, it was never completely quiet, but quiet enough that you could concentrate (and I like it quiet). Conversations were also easier to filter because you could tell if it would effect your taks or not. The new environment is much louder, and much harder to filter through the non-work-related conversations, making it harder to stay on task.
&lt;/p&gt;
&lt;p&gt;
My workgroup is also attempting to make the transition to single-sourcing and using a content managment system. The transition has nearly stopped (after making great strides) since the move. This is partly because work is taking longer to complete now that we are separated.
&lt;/p&gt;
&lt;p&gt;
It is pretty amazing to see this process in action. Collaboration makes work much easier, the People happier, and management of projects less stressful. Everyone is at least aware of everything that is going on, and able to give some direction to those external to the group.
&lt;/p&gt;
&lt;p&gt;
Emma&#8217;s article should be read and taken to heart. She has really captured the main pieces to having a collaborative team.
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>This article is so very true. My workgroup was a collaborative team until end of last year. While we were technically in cubicles, they were essentially in a circle around a central table. It was very easy to discuss policies, procedures, and materials we were working on individually, which spilled over into other materials and work classifications. This was often how we found out about projects that were indirectly related to our tasks. We called it &#8220;stoop time&#8221; when we rolled out and had these informal meetings.
</p>
<p>
Then we were moved physically to another part of the building, with normal cubes in rows and other Employees. That&#8217;s where we began to fall apart, and we could see it happening. After much discussion, we were able to get half-walls put in between the cubes, so we could at least discuss with our closest neighbors. While this has helped, it is not nearly as collaborative as what we had. There is a definite possessiveness now, which was never there before. The pride we used to have in our group is also gone.
</p>
<p>
While in the circular environement, it was never completely quiet, but quiet enough that you could concentrate (and I like it quiet). Conversations were also easier to filter because you could tell if it would effect your taks or not. The new environment is much louder, and much harder to filter through the non-work-related conversations, making it harder to stay on task.
</p>
<p>
My workgroup is also attempting to make the transition to single-sourcing and using a content managment system. The transition has nearly stopped (after making great strides) since the move. This is partly because work is taking longer to complete now that we are separated.
</p>
<p>
It is pretty amazing to see this process in action. Collaboration makes work much easier, the People happier, and management of projects less stressful. Everyone is at least aware of everything that is going on, and able to give some direction to those external to the group.
</p>
<p>
Emma&#8217;s article should be read and taken to heart. She has really captured the main pieces to having a collaborative team.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: holmesd</title>
		<link>http://thecontentwrangler.com/2006/10/18/dispelling_collaboration_myths_is_your_team_an_impediment_to_content_manage/comment-page-1/#comment-38</link>
		<dc:creator>holmesd</dc:creator>
		<pubDate>Fri, 20 Oct 2006 16:17:36 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/ee/?p=638#comment-38</guid>
		<description>&lt;p&gt;I agree with most of the article - but I&#8217;m a little hesitant to get on board for item 4. I&#8217;ve always been of the school of thought that knowledge workers - whether they be developers, authors, artists, or scholars - need quiet, personal space to work.
&lt;/p&gt;
&lt;p&gt;
Many of these workers have to &#8216;get in the zone&#8217; before they can produce their best work or before they can be their most efficient. The downside is that it takes time to get into the zone (typically between 5 and 15 minutes) and it&#8217;s very easy to get knocked out of the zone by outside distractions. The example that&#8217;s most often given is a worker that gets interrupted every 20 minutes by someone else&#8217;s conversations or phone calls. For this person, only 15 minutes of every hour are spent in productive work, while the other 45 are spent attempting to &#8216;get back to work&#8217; or rechecking their notes to make sure they didn&#8217;t miss something.
&lt;/p&gt;
&lt;p&gt;
From my own personal experience, I can say that the difference between an open and a closed office environment is about a 10% reduction in productivity. If it&#8217;s a noisy environment, that number is probably closer to  20%. Assuming that I average 30 hours a week of production time (time spent actually making something), this might mean an overall loss of 6 hours a week of labour.
&lt;/p&gt;
&lt;p&gt;
I guess my hesitation here is that I know that moving to an open, collaborative office environment will definitely mean a reduction in my personal productivity. What I&#8217;m curious about is if the net gains are worth it. Will the loss in individual productivity in each worker be offset by the improvements to group productivity that come from collaboration (and of course, the infrastructure savings of the new office environment)?
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>I agree with most of the article &#8211; but I&#8217;m a little hesitant to get on board for item 4. I&#8217;ve always been of the school of thought that knowledge workers &#8211; whether they be developers, authors, artists, or scholars &#8211; need quiet, personal space to work.
</p>
<p>
Many of these workers have to &#8216;get in the zone&#8217; before they can produce their best work or before they can be their most efficient. The downside is that it takes time to get into the zone (typically between 5 and 15 minutes) and it&#8217;s very easy to get knocked out of the zone by outside distractions. The example that&#8217;s most often given is a worker that gets interrupted every 20 minutes by someone else&#8217;s conversations or phone calls. For this person, only 15 minutes of every hour are spent in productive work, while the other 45 are spent attempting to &#8216;get back to work&#8217; or rechecking their notes to make sure they didn&#8217;t miss something.
</p>
<p>
From my own personal experience, I can say that the difference between an open and a closed office environment is about a 10% reduction in productivity. If it&#8217;s a noisy environment, that number is probably closer to  20%. Assuming that I average 30 hours a week of production time (time spent actually making something), this might mean an overall loss of 6 hours a week of labour.
</p>
<p>
I guess my hesitation here is that I know that moving to an open, collaborative office environment will definitely mean a reduction in my personal productivity. What I&#8217;m curious about is if the net gains are worth it. Will the loss in individual productivity in each worker be offset by the improvements to group productivity that come from collaboration (and of course, the infrastructure savings of the new office environment)?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Barry Schaeffer</title>
		<link>http://thecontentwrangler.com/2006/10/18/dispelling_collaboration_myths_is_your_team_an_impediment_to_content_manage/comment-page-1/#comment-37</link>
		<dc:creator>Barry Schaeffer</dc:creator>
		<pubDate>Fri, 20 Oct 2006 10:41:51 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/ee/?p=638#comment-37</guid>
		<description>&lt;p&gt;Good points but a little heavy on the &#8220;what&#8221; describing the goal without providing the &#8220;how.&#8221;  Particularly liked Emma&#8217;s focus on the human and organizational impediments to true collaboration and team-building.&#160; Unfortunately, the software industry tends to couch these problems as stemming from a lack of proper CM software and IT support (wonder why,) leading many organizations to buy things that don&#8217;t address their problems and limp along without much improvement. This is a failing in many areas of IT-related operations and until it is dealt with, we won&#8217;t see that brave new world that IT keeps telling us about.
&lt;/p&gt;
&lt;p&gt;
Actually, there is a pretty extensive library of techniques for building the multidisciplinary team contained in the literature around &#8220;Concurrent Engineering&#8221; or CE.&#160; This philosophy, articulated in the 80s by the DoD and designed to bring together the often antagonistic relationships between design and process engineering in the manufacturing world, addresses most if not all of the points in Emma&#8217;s article and is equally applicable to information projects.
&lt;/p&gt;
&lt;p&gt;
Emma&#8217;s piece contributes to the sometimes painful realization that the only core players in the information life-cycle are the SMEs who know things and the consumers who need and are willing to pay for those things.&#160; Everyone in between, however capable, and that includes tech writers, IT, etc., are carrying water for the these key players.&#160; Until everyone accepts that fact and understands his or her role, we won&#8217;t see the kind of progress the world needs.
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Good points but a little heavy on the &#8220;what&#8221; describing the goal without providing the &#8220;how.&#8221;  Particularly liked Emma&#8217;s focus on the human and organizational impediments to true collaboration and team-building.&nbsp; Unfortunately, the software industry tends to couch these problems as stemming from a lack of proper CM software and IT support (wonder why,) leading many organizations to buy things that don&#8217;t address their problems and limp along without much improvement. This is a failing in many areas of IT-related operations and until it is dealt with, we won&#8217;t see that brave new world that IT keeps telling us about.
</p>
<p>
Actually, there is a pretty extensive library of techniques for building the multidisciplinary team contained in the literature around &#8220;Concurrent Engineering&#8221; or CE.&nbsp; This philosophy, articulated in the 80s by the DoD and designed to bring together the often antagonistic relationships between design and process engineering in the manufacturing world, addresses most if not all of the points in Emma&#8217;s article and is equally applicable to information projects.
</p>
<p>
Emma&#8217;s piece contributes to the sometimes painful realization that the only core players in the information life-cycle are the SMEs who know things and the consumers who need and are willing to pay for those things.&nbsp; Everyone in between, however capable, and that includes tech writers, IT, etc., are carrying water for the these key players.&nbsp; Until everyone accepts that fact and understands his or her role, we won&#8217;t see the kind of progress the world needs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ScottAbel</title>
		<link>http://thecontentwrangler.com/2006/10/18/dispelling_collaboration_myths_is_your_team_an_impediment_to_content_manage/comment-page-1/#comment-36</link>
		<dc:creator>ScottAbel</dc:creator>
		<pubDate>Fri, 20 Oct 2006 09:52:11 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/ee/?p=638#comment-36</guid>
		<description>&lt;p&gt;Thanks for sharing your thoughts about this important topic, Holly. We expect to see many more articles on change management in our trade and industry publications as businesses around the globe move away from managing content inefficiently. We also expect to see resistance to change.
&lt;/p&gt;
&lt;p&gt;
Those organizations that succeed at adopting collaboration will hopefully continue to share their stories with us so we can learn from their expereinces. Those that fail, well, we&#8217;ll point and laugh at as we say, &#8220;We told you so.&#8221;
&lt;/p&gt;
&lt;p&gt;
Of course, there are both pros and cons to making your office environment collaboration-friendly. And there are also some unanswered questions: What about those who work from home or remotely. How do we bring them into the mix? And, are there any web-based technologies that may be able to connect remote workers so they are able to collaborate in a similar manner as if they were working at the office.
&lt;/p&gt;
&lt;p&gt;
Lots to thinks about. That&#8217;s for sure. Thanks again for your thoughtful comments.
&lt;/p&gt;
&lt;p&gt;
Scott Abel
&lt;br /&gt;
The Content Wrangler, Inc.
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Thanks for sharing your thoughts about this important topic, Holly. We expect to see many more articles on change management in our trade and industry publications as businesses around the globe move away from managing content inefficiently. We also expect to see resistance to change.
</p>
<p>
Those organizations that succeed at adopting collaboration will hopefully continue to share their stories with us so we can learn from their expereinces. Those that fail, well, we&#8217;ll point and laugh at as we say, &#8220;We told you so.&#8221;
</p>
<p>
Of course, there are both pros and cons to making your office environment collaboration-friendly. And there are also some unanswered questions: What about those who work from home or remotely. How do we bring them into the mix? And, are there any web-based technologies that may be able to connect remote workers so they are able to collaborate in a similar manner as if they were working at the office.
</p>
<p>
Lots to thinks about. That&#8217;s for sure. Thanks again for your thoughtful comments.
</p>
<p>
Scott Abel<br />
<br />
The Content Wrangler, Inc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Holly</title>
		<link>http://thecontentwrangler.com/2006/10/18/dispelling_collaboration_myths_is_your_team_an_impediment_to_content_manage/comment-page-1/#comment-35</link>
		<dc:creator>Holly</dc:creator>
		<pubDate>Thu, 19 Oct 2006 15:27:48 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/ee/?p=638#comment-35</guid>
		<description>&lt;p&gt;Provocative article with many good points.
&lt;/p&gt;
&lt;p&gt;
I&#8217;ve always found that when a tech writer&#8217;s documentation is not up to snuff, 9 times out of 10, the reason is that they didn&#8217;t collaborate very well with the developer, the SME, or another necessary contact.
&lt;/p&gt;
&lt;p&gt;
I totally agree on the &#8220;it&#8217;s not your document\&#8221; point.
&lt;/p&gt;
&lt;p&gt;
I&#8217;m of two minds on the &#8220;no cubicles&#8221; argument. Working together in the same room can be invigorating, but it can also be stressful. Private, quiet, alone time is a good way to alleviate stress. Not having your own space to retreat to, can cause dissatisfaction. Working from home may not be an option in some situations.
&lt;/p&gt;
&lt;p&gt;
People have different work habits. Some like to socialize and joke around. Others are heads down, always focused. These two types can work together, but I wouldn&#8217;t put them in the same room.
&lt;/p&gt;
&lt;p&gt;
You can force people into common areas and maybe get some quick wins, but will you retain those employees in the long run? Will your employees recommend your company to their friends and acquaintances? You have to think beyond the immediate project.
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Provocative article with many good points.
</p>
<p>
I&#8217;ve always found that when a tech writer&#8217;s documentation is not up to snuff, 9 times out of 10, the reason is that they didn&#8217;t collaborate very well with the developer, the SME, or another necessary contact.
</p>
<p>
I totally agree on the &#8220;it&#8217;s not your document\&#8221; point.
</p>
<p>
I&#8217;m of two minds on the &#8220;no cubicles&#8221; argument. Working together in the same room can be invigorating, but it can also be stressful. Private, quiet, alone time is a good way to alleviate stress. Not having your own space to retreat to, can cause dissatisfaction. Working from home may not be an option in some situations.
</p>
<p>
People have different work habits. Some like to socialize and joke around. Others are heads down, always focused. These two types can work together, but I wouldn&#8217;t put them in the same room.
</p>
<p>
You can force people into common areas and maybe get some quick wins, but will you retain those employees in the long run? Will your employees recommend your company to their friends and acquaintances? You have to think beyond the immediate project.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
