<?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"
	>
<channel>
	<title>Comments on: Worst Practices for Managing Wikis in Organizations</title>
	<atom:link href="http://www.kinf.wiai.uni-bamberg.de/WiOblog/index.php/top-3-worst-practices-for-managing-wikis-in-organizations/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.kinf.wiai.uni-bamberg.de/WiOblog/index.php/top-3-worst-practices-for-managing-wikis-in-organizations/</link>
	<description>From Invention to Innovation</description>
	<pubDate>Fri, 10 Feb 2012 03:43:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Kristian Voigt</title>
		<link>http://www.kinf.wiai.uni-bamberg.de/WiOblog/index.php/top-3-worst-practices-for-managing-wikis-in-organizations/#comment-6760</link>
		<dc:creator>Kristian Voigt</dc:creator>
		<pubDate>Thu, 26 Feb 2009 14:41:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.kinf.wiai.uni-bamberg.de/WiOblog/index.php/top-3-worst-practices-for-managing-wikis-in-organizations/#comment-6760</guid>
		<description>In an organisation it is possible to make people share best practise (of course if you can find them) - but how will you make people share their worst practises. 'Please look at me and see how badly I failed'. I'm affraid that this won't give much credit - eventhough it can be very beneficial to others. I think you need to have a good reputation to show your dirty laundry in public.</description>
		<content:encoded><![CDATA[<p>In an organisation it is possible to make people share best practise (of course if you can find them) - but how will you make people share their worst practises. &#8216;Please look at me and see how badly I failed&#8217;. I&#8217;m affraid that this won&#8217;t give much credit - eventhough it can be very beneficial to others. I think you need to have a good reputation to show your dirty laundry in public.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steffen</title>
		<link>http://www.kinf.wiai.uni-bamberg.de/WiOblog/index.php/top-3-worst-practices-for-managing-wikis-in-organizations/#comment-6698</link>
		<dc:creator>Steffen</dc:creator>
		<pubDate>Mon, 16 Feb 2009 08:30:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.kinf.wiai.uni-bamberg.de/WiOblog/index.php/top-3-worst-practices-for-managing-wikis-in-organizations/#comment-6698</guid>
		<description>@Dennis

Are best practices the enemy of innovation? Absolutely! Copying best practices leads to just one thing: a copy. And a copy is nothing new, certainly not an innovation.

Should we be talking about best thinking, then? I don't really see the difference to best practices. Slappin' on another label changes little to nothing. What matters most is thinking for oneself, thinking outside the box. I don't mean to say that best practices are necessarily bad. Neither are worst practices. On the contrary, it's essential that we look to others as well as to ourselves. What we need to realize is that while some things work for others, they may not work for us at all. Thus, it's not best or worst thinking but simply THINKING.

How do we broaden the concepts of invention and innovation? First, don't think of a lineary process from invention to innovation but as a recursive process with intermediary loops, setbacks, and steps forward. Wikis are a prime example. Most organizations quickly apply some kind of structure to their wikis that resembles something they're familiar with, e.g., the departmental hierarchy in place or a project-based hyperlink structure. Over time, however, this structure adepts to the needs of its users. People link projects, put up new pages, and basically try something that hasn't been done before -- it's natural curiosity. Fortunately, a wiki is a highly democratic medium that allows for dynamic change; in a very sense, it's the complete opposite of other enterprise software such as SAP where not a single field in a GUI may change without the help of a third-party consultant.

Again, I agree, the question you're posing are way beyond wikis. And we're working on the answers :-)</description>
		<content:encoded><![CDATA[<p>@Dennis</p>
<p>Are best practices the enemy of innovation? Absolutely! Copying best practices leads to just one thing: a copy. And a copy is nothing new, certainly not an innovation.</p>
<p>Should we be talking about best thinking, then? I don&#8217;t really see the difference to best practices. Slappin&#8217; on another label changes little to nothing. What matters most is thinking for oneself, thinking outside the box. I don&#8217;t mean to say that best practices are necessarily bad. Neither are worst practices. On the contrary, it&#8217;s essential that we look to others as well as to ourselves. What we need to realize is that while some things work for others, they may not work for us at all. Thus, it&#8217;s not best or worst thinking but simply THINKING.</p>
<p>How do we broaden the concepts of invention and innovation? First, don&#8217;t think of a lineary process from invention to innovation but as a recursive process with intermediary loops, setbacks, and steps forward. Wikis are a prime example. Most organizations quickly apply some kind of structure to their wikis that resembles something they&#8217;re familiar with, e.g., the departmental hierarchy in place or a project-based hyperlink structure. Over time, however, this structure adepts to the needs of its users. People link projects, put up new pages, and basically try something that hasn&#8217;t been done before &#8212; it&#8217;s natural curiosity. Fortunately, a wiki is a highly democratic medium that allows for dynamic change; in a very sense, it&#8217;s the complete opposite of other enterprise software such as SAP where not a single field in a GUI may change without the help of a third-party consultant.</p>
<p>Again, I agree, the question you&#8217;re posing are way beyond wikis. And we&#8217;re working on the answers <img src='http://www.kinf.wiai.uni-bamberg.de/WiOblog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dennis</title>
		<link>http://www.kinf.wiai.uni-bamberg.de/WiOblog/index.php/top-3-worst-practices-for-managing-wikis-in-organizations/#comment-6677</link>
		<dc:creator>Dennis</dc:creator>
		<pubDate>Fri, 13 Feb 2009 17:58:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.kinf.wiai.uni-bamberg.de/WiOblog/index.php/top-3-worst-practices-for-managing-wikis-in-organizations/#comment-6677</guid>
		<description>Are best practices the enemyof innovation?  Should we be talking about best thinking?  Best practices help us overcome worst practices and complacency, up to the point that thinking stops and habits of mind take over.

How do we really broaden the concept of Invention to Innovation so that best thinking includes reflection, double and triple loop thinking?   

Seems this can be directed way beyond Wiki discussion.</description>
		<content:encoded><![CDATA[<p>Are best practices the enemyof innovation?  Should we be talking about best thinking?  Best practices help us overcome worst practices and complacency, up to the point that thinking stops and habits of mind take over.</p>
<p>How do we really broaden the concept of Invention to Innovation so that best thinking includes reflection, double and triple loop thinking?   </p>
<p>Seems this can be directed way beyond Wiki discussion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yigal Chamish</title>
		<link>http://www.kinf.wiai.uni-bamberg.de/WiOblog/index.php/top-3-worst-practices-for-managing-wikis-in-organizations/#comment-6224</link>
		<dc:creator>Yigal Chamish</dc:creator>
		<pubDate>Fri, 05 Dec 2008 07:08:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.kinf.wiai.uni-bamberg.de/WiOblog/index.php/top-3-worst-practices-for-managing-wikis-in-organizations/#comment-6224</guid>
		<description>Great post, thank you.
The main good/best practice in regard of motivation within Knowledge management and organizational learning is that executives and managers will move themselves towards the position of enablers: they should establish the spirit, the environment and the infrastructure for those who know - to meet, talk and share their stories.
Now, in regard to Wiki, it will only succeed if people within the organization will feel that they can formulate and create the encyclopedia values by themselves.</description>
		<content:encoded><![CDATA[<p>Great post, thank you.<br />
The main good/best practice in regard of motivation within Knowledge management and organizational learning is that executives and managers will move themselves towards the position of enablers: they should establish the spirit, the environment and the infrastructure for those who know - to meet, talk and share their stories.<br />
Now, in regard to Wiki, it will only succeed if people within the organization will feel that they can formulate and create the encyclopedia values by themselves.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steffen</title>
		<link>http://www.kinf.wiai.uni-bamberg.de/WiOblog/index.php/top-3-worst-practices-for-managing-wikis-in-organizations/#comment-5487</link>
		<dc:creator>Steffen</dc:creator>
		<pubDate>Wed, 10 Sep 2008 17:34:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.kinf.wiai.uni-bamberg.de/WiOblog/index.php/top-3-worst-practices-for-managing-wikis-in-organizations/#comment-5487</guid>
		<description>Unfortunately, there is no general answer to this question. Several factors affect your decision.

For example, MediaWiki is a good choice: (a) Most of your employees will already know how to use it since its the engine Wikipedia uses, (b) it's highly customizable with your own CSS and thousands of (free) plug-ins, and (c) it scales really well (obviously, if you consider Wikipedia). But if you are looking for third-party tech support or you just cannot allow open source (e.g., I know a major company that does not allow MySQL as a database, and that's MediaWiki's backend), you may be better of with something like Confluence.

A good place to compare wikis in terms of features is www.wikimatrix.org.</description>
		<content:encoded><![CDATA[<p>Unfortunately, there is no general answer to this question. Several factors affect your decision.</p>
<p>For example, MediaWiki is a good choice: (a) Most of your employees will already know how to use it since its the engine Wikipedia uses, (b) it&#8217;s highly customizable with your own CSS and thousands of (free) plug-ins, and (c) it scales really well (obviously, if you consider Wikipedia). But if you are looking for third-party tech support or you just cannot allow open source (e.g., I know a major company that does not allow MySQL as a database, and that&#8217;s MediaWiki&#8217;s backend), you may be better of with something like Confluence.</p>
<p>A good place to compare wikis in terms of features is <a href="http://www.wikimatrix.org" rel="nofollow">http://www.wikimatrix.org</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Human Resource Consulting</title>
		<link>http://www.kinf.wiai.uni-bamberg.de/WiOblog/index.php/top-3-worst-practices-for-managing-wikis-in-organizations/#comment-5486</link>
		<dc:creator>Human Resource Consulting</dc:creator>
		<pubDate>Wed, 10 Sep 2008 15:50:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.kinf.wiai.uni-bamberg.de/WiOblog/index.php/top-3-worst-practices-for-managing-wikis-in-organizations/#comment-5486</guid>
		<description>What software package do you reccommend for setting up a Wiki at the office?</description>
		<content:encoded><![CDATA[<p>What software package do you reccommend for setting up a Wiki at the office?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

