<?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: Army Uses Wiki to Gather Experience, Revise Field Manuals</title>
	<atom:link href="http://www.ikiw.org/2009/08/17/army-uses-wiki-to-gather-experience-revise-field-manuals/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ikiw.org/2009/08/17/army-uses-wiki-to-gather-experience-revise-field-manuals/</link>
	<description></description>
	<lastBuildDate>Sun, 14 Mar 2010 15:23:10 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Principles, Operational Procedures, &#38; Permissions on a Wiki &#124; Future Changes</title>
		<link>http://www.ikiw.org/2009/08/17/army-uses-wiki-to-gather-experience-revise-field-manuals/comment-page-1/#comment-140084</link>
		<dc:creator>Principles, Operational Procedures, &#38; Permissions on a Wiki &#124; Future Changes</dc:creator>
		<pubDate>Thu, 27 Aug 2009 15:24:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.ikiw.org/?p=6935#comment-140084</guid>
		<description>[...] Caldwell of Gartner offers his take on the Army&#8217;s pilot project to gather experience and revise field manuals using a wiki: The Army saw the failures of doctrine in Iraq, and how the gaps were filled by social networking. [...]</description>
		<content:encoded><![CDATA[<p>[...] Caldwell of Gartner offers his take on the Army&#8217;s pilot project to gather experience and revise field manuals using a wiki: The Army saw the failures of doctrine in Iraq, and how the gaps were filled by social networking. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Tropea</title>
		<link>http://www.ikiw.org/2009/08/17/army-uses-wiki-to-gather-experience-revise-field-manuals/comment-page-1/#comment-139989</link>
		<dc:creator>John Tropea</dc:creator>
		<pubDate>Wed, 19 Aug 2009 00:12:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.ikiw.org/?p=6935#comment-139989</guid>
		<description>Part 3 is awesome - the psychology of change hey...Lee Bryant talks about steering away from terms like blog, wiki in slide 37 http://www.headshift.com/blog/2009/08/behavioural-transition-strateg.php
I also notice some vendors use the term online document rather than wiki, and messages rather than blog...this way it feels like nothing THAT new

I really like this use case for a wiki...I mentioned something similar in my post
http://libraryclips.blogsome.com/2008/10/13/wikis-for-exceptions-and-process-failures/

I mentioned that Wikis reach what procedures cannot forsee, here&#039;s an excerpt:

&quot;Every plant site has procedures, but like everything else these procedures cannot be aware of every situation that can occur, or meet every need, so a site wiki for these heuristics, anomalies, band-aids, exceptions can be communally created by the people who actually work at the site.

A wiki would be doing a site manager a favour in the ways of safety, and possible new inclusion into the procedures…when exceptions become the rule. Now that I think of it, it’s kind of a distant cousin to an online suggestion box.

What I like about this is no-one is in charge or responsible to write such a document, it’s just stuff everyone knows or doesn’t know, so by everyone pitching in we help each other out, there is no effort on just one person, therefore it’s more prone to exist…plus none of us are smarter than the sum of us.&quot;</description>
		<content:encoded><![CDATA[<p>Part 3 is awesome &#8211; the psychology of change hey&#8230;Lee Bryant talks about steering away from terms like blog, wiki in slide 37 <a href="http://www.headshift.com/blog/2009/08/behavioural-transition-strateg.php" rel="nofollow">http://www.headshift.com/blog/2009/08/behavioural-transition-strateg.php</a><br />
I also notice some vendors use the term online document rather than wiki, and messages rather than blog&#8230;this way it feels like nothing THAT new</p>
<p>I really like this use case for a wiki&#8230;I mentioned something similar in my post<br />
<a href="http://libraryclips.blogsome.com/2008/10/13/wikis-for-exceptions-and-process-failures/" rel="nofollow">http://libraryclips.blogsome.com/2008/10/13/wikis-for-exceptions-and-process-failures/</a></p>
<p>I mentioned that Wikis reach what procedures cannot forsee, here&#8217;s an excerpt:</p>
<p>&#8220;Every plant site has procedures, but like everything else these procedures cannot be aware of every situation that can occur, or meet every need, so a site wiki for these heuristics, anomalies, band-aids, exceptions can be communally created by the people who actually work at the site.</p>
<p>A wiki would be doing a site manager a favour in the ways of safety, and possible new inclusion into the procedures…when exceptions become the rule. Now that I think of it, it’s kind of a distant cousin to an online suggestion box.</p>
<p>What I like about this is no-one is in charge or responsible to write such a document, it’s just stuff everyone knows or doesn’t know, so by everyone pitching in we help each other out, there is no effort on just one person, therefore it’s more prone to exist…plus none of us are smarter than the sum of us.&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
