<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Semantic Puzzle&#187; Corporate wiki</title>
	<atom:link href="http://blog.semantic-web.at/tag/corporate-wiki/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.semantic-web.at</link>
	<description>Open World Assumptions</description>
	<lastBuildDate>Thu, 02 Feb 2012 14:26:25 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>corporate wiki: more than a software</title>
		<link>http://blog.semantic-web.at/2009/01/19/corporate-wiki-more-than-a-software/</link>
		<comments>http://blog.semantic-web.at/2009/01/19/corporate-wiki-more-than-a-software/#comments</comments>
		<pubDate>Mon, 19 Jan 2009 14:07:37 +0000</pubDate>
		<dc:creator>Thomas Thurner</dc:creator>
				<category><![CDATA[Enterprise 2.0]]></category>
		<category><![CDATA[Corporate wiki]]></category>
		<category><![CDATA[Groupware]]></category>
		<category><![CDATA[Wiki]]></category>
		<category><![CDATA[Wiki Engines]]></category>

		<guid isPermaLink="false">http://blog.semantic-web.at/?p=430</guid>
		<description><![CDATA[Image via Wikipedia It&#8217;s fashionable to have a corporate wiki installed at the own company. But often &#8211; to speak a word of truth &#8211; this wikis are not more than a burial ground of vague project memos. This isn&#8217;t &#8230; <a href="http://blog.semantic-web.at/2009/01/19/corporate-wiki-more-than-a-software/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<div class="zemanta-img" style="margin: 1em; float: right; display: block;">
<div>
<dl class="wp-caption" style="width: 212px;">
<dt class="wp-caption-dt"><a href="http://commons.wikipedia.org/wiki/Image:SovietGravesSaaremaa.JPG"><img title="Soviet WWII graves, Saaremaa, Estonia. July 27..." src="http://upload.wikimedia.org/wikipedia/commons/thumb/4/49/SovietGravesSaaremaa.JPG/202px-SovietGravesSaaremaa.JPG" alt="Soviet WWII graves, Saaremaa, Estonia. July 27..." width="202" height="152" /></a></dt>
<dd class="wp-caption-dd zemanta-img-attribution" style="font-size: 0.8em;">Image via <a href="http://commons.wikipedia.org/wiki/Image:SovietGravesSaaremaa.JPG">Wikipedia</a></dd>
</dl>
</div>
</div>
<p>It&#8217;s fashionable to have a <a class="zem_slink" title="Corporate wiki" rel="wikipedia" href="http://en.wikipedia.org/wiki/Corporate_wiki">corporate wiki</a> installed at the own company. But often &#8211; to speak a word of truth &#8211; this wikis are not more than a burial ground of vague project memos. This isn&#8217;t a big surprise, because often corporate strategy on innovate wikis into company&#8217;s every day life, comes in a simple triple jump: (1) buy some software, (2) get a one-day workshop, (3) write a binding memo to employees to use that wiki. Leaving the process <span>in such a kind</span>, wikis are developing the way that is inherent for them: run riot (optimistic case) or run dry (normal case).</p>
<p>But wikis are extensive and powerful instruments in corporate life. You can plan, communicate, document and control everyday corporate processes with them &#8211; within a common environment. So wikis are less a chunk of software, they are more the potential future working environment, where employees are &#8220;living in&#8221;. So, as careful as we are furnish our offices, we should also setup our virtual working place: The corporate wiki.</p>
<p>Andreas Heilwagen points out some tips on innovate corporate wikis right at &#8220;<a href="http://www.computerwoche.de/1871031" target="_blank">Computerwoche</a>&#8221;</p>
<ul>
<li> clear rules and responsibilities</li>
<li> do not start with empty wikis</li>
<li> so called &#8220;champions&#8221; have to smooth the way</li>
<li> change your mind on information processing</li>
<li> be careful with vendor-specific plugins</li>
<li> do not outsource to professional information brokers</li>
<li> everybody should be able to edit (nearby) every page</li>
<li> get your pages connected intern and extern</li>
<li> always create useful information which others can reuse</li>
</ul>
<p>Following my statement at the beginning, I would add:</p>
<ul>
<li> get a clear definition about the fields you want to use the wiki for</li>
<li> identify company&#8217;s surplus in having a wiki</li>
<li> see which tools and services bring some very personnel benefit for the employees</li>
</ul>
<p>It&#8217;s the preparation phase which is essential in the quaetion on how effective the work with a future corporate wiki can be. Vienna based <a href="http://www.semantic-web.at" target="_blank">Semantic Web Company</a> exemplary runs through such a preparation phase this days. Getting data, using tools like storytelling, personas and usage scenarios, this may end in a &#8220;well equipped working environment of the future&#8221; &#8211; the corporate wiki.</p>
<p>Retated:</p>
<ul>
<li><a href="http://blogs.oracle.com/fusionecm/2009/01/enterprise_wiki_strategies.html" target="_blank">Oracle Fusion ECM: Enterprise Wiki Strategies</a></li>
</ul>
<div class="zemanta-pixie" style="margin-top: 10px; height: 15px;"><a class="zemanta-pixie-a" title="Zemified by Zemanta" href="http://reblog.zemanta.com/zemified/74edc5c4-14aa-49f3-9689-4a5b99fec3c0/"><img class="zemanta-pixie-img" style="border: medium none; float: right;" src="http://img.zemanta.com/reblog_e.png?x-id=74edc5c4-14aa-49f3-9689-4a5b99fec3c0" alt="Reblog this post [with Zemanta]" /></a></div>
]]></content:encoded>
			<wfw:commentRss>http://blog.semantic-web.at/2009/01/19/corporate-wiki-more-than-a-software/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

