<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Boxes and Arrows: Comments by Mark Aufflick</title>
    <link>http://www.boxesandarrows.com/person/1718</link>
    <pubDate>Fri, 26 Jan 2007 14:53:37 GMT</pubDate>
    <description>Comments by Mark Aufflick</description>
    <item>
      <description>&lt;p&gt;Quote from original comment:&lt;/p&gt;

	&lt;p&gt;&amp;#8220;Also Wikis and Blogs seem to be the hottest &#8220;must have&#8221; for a company. But how do you motivate your employees to contribute to a wiki? How do you prevent that they do not use blogs to reveal secrets?&amp;#8221;&lt;/p&gt;

	&lt;p&gt;I suggest the article should be &amp;#8220;the trouble with inflexible companies&amp;#8221;.&lt;/p&gt;

	&lt;p&gt;Web 2.0 shows that collaborative media works if people are given freedom. If ou are concerned that your employees might reveal secrets then either you don&amp;#8217;t trust your employees enough, or the culture within your company is wrong (why would the employees be motivated to releaes secrets). And how do you know that it&amp;#8217;s not beneficial to release some of those secrets in some way?&lt;/p&gt;

	&lt;p&gt;This comment reveals a major flaw in some company thinking &amp;#8211; that somehow it&amp;#8217;s in the best interests of the company to control from the top.&lt;/p&gt;

	&lt;p&gt;Let&amp;#8217;s take two of my employment experiences. Both used wikis, both were multi-national and near the top of their market. One had an effective (internal) wiki and employees who were active on public mailing lists etc. The other had a wiki in name only, internal mailing lists that were inactive, and very few people recieved mailing lists let alone contributed. The first team was producing innovative technologies, had a vibrant atmosphere, and was contributing significantly to the profitability of the company. The second team was a limiting factor &amp;#8211; it had an atmosphere where it ws better to do it yourself and retain the glory, and participation in internal or external mailing lists was regarded as a waste of time.&lt;/p&gt;

	&lt;p&gt;In these true examples, which team do you think would love to read an article titled &amp;#8220;the trouble with Web 2.0&amp;#8221;? I think the latter, but the problem isn&amp;#8217;t that the collaborative nature of web 2.0 doesn&amp;#8217;t suit the enterprise, it&amp;#8217;s that some enterprises don&amp;#8217;t have the right environment to take advantage of what it offers.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/idea/view/3650#content_4045</link>
      <guid>http://www.boxesandarrows.com/idea/view/3650#content_4045</guid>
      <pubDate>Fri, 26 Jan 2007 14:53:37 GMT</pubDate>
      <author>Mark Aufflick</author>
    </item>
    <item>
      <description>&lt;p&gt;It&amp;#8217;s not all relevant to your question, but you might like to read an article (and the comments) Lars wrote a while ago &lt;a href="http://pinds.com/articles/2005/11/15/reuse-in-the-large-is-an-unsolved-problem-why-i-left-openacs-for-rails" rel="nofollow"&gt;Reuse-in-the-large is an unsolved problem&lt;/a&gt;.&lt;/p&gt;

	&lt;p&gt;The thought was based on an article by Robert Glass &lt;a href="http://www.informit.com/articles/printerfriendly.asp?p=30091&amp;#38;rl=1" rel="nofollow"&gt;Facts of Software Engineering Management&lt;/a&gt;&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/idea/view/2330#content_4046</link>
      <guid>http://www.boxesandarrows.com/idea/view/2330#content_4046</guid>
      <pubDate>Fri, 26 Jan 2007 14:53:37 GMT</pubDate>
      <author>Mark Aufflick</author>
    </item>
    <item>
      <description>&lt;p&gt;Alok &amp;#8211; this is brilliant. Love your blog entry.&lt;/p&gt;

	&lt;p&gt;You have just been added to my rss reader!&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/idea/view/3622#content_4047</link>
      <guid>http://www.boxesandarrows.com/idea/view/3622#content_4047</guid>
      <pubDate>Fri, 26 Jan 2007 14:53:37 GMT</pubDate>
      <author>Mark Aufflick</author>
    </item>
  </channel>
</rss>
