<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.thestandard.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title></title>
 <link>http://www.thestandard.com/node/107716/comments</link>
 <description>comments feed.</description>
 <language>en</language>
<item>
 <title>Things the CIA learned about implementing an enterprise wiki</title>
 <link>http://www.thestandard.com/news/2008/06/10/things-cia-learned-about-implementing-enterprise-wiki</link>
 <description>&lt;p&gt;&lt;!--paging_filter--&gt;
&lt;p&gt;The two &lt;a href=&quot;http://www.cio.com/article/389613/subject/Central+Intelligence+Agency&quot; rel=&quot;nofollow&quot;&gt;CIA&lt;/a&gt; officials who lead the Intellipedia-a &lt;a href=&quot;http://www.cio.com/article/122701&quot; rel=&quot;nofollow&quot;&gt;wiki&lt;/a&gt; set up by the CIA for disparate intelligence agencies to collaborate on key topics-delivered a keynote at the Enterprise 2.0 conference this morning. When it comes to social software implementation, they stressed the importance of administering access, starting small and moving information &lt;a href=&quot;http://www.cio.com/article/197101&quot; rel=&quot;nofollow&quot;&gt;out of narrow channels like e-mail and into broader platforms like wikis&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The presentation was delivered by two leaders of the CIA&#039;s Intellipedia project, Sean Dennehy, who&#039;s title is &quot;Intellipedia Evangelist,&quot; and Don Burke. Intellipedia was founded in April 2006 and it is used by 16 agencies in the U.S. government, according to &lt;a href=&quot;http://en.wikipedia.org/wiki/Intellipedia&quot; rel=&quot;nofollow&quot;&gt;a Wikipedia article&lt;/a&gt; citing several government sources and media reports.&lt;/p&gt;
&lt;p&gt;1. Set access policies.&lt;/p&gt;
&lt;p&gt;Because most people associate wikis with &lt;a href=&quot;http://www.cio.com/article/121711&quot; rel=&quot;nofollow&quot;&gt;Wikipedia&lt;/a&gt; , you need to establish that there will be access controls about who views (and just as important) who edits information on a wiki. With Intellipedia, for instance, there are three different versions. One is generally viewable by most agency employees, another is secret, and a third is top secret. Within each of those versions, some people have editing access and others only are allowed to view. Some aren&#039;t allowed writing or viewing access depending on their security clearance.&lt;/p&gt;
&lt;p&gt;The beauty of the wiki model, Dennehy says, is that all edits can be easily tracked and made available in version history. &quot;We&#039;re often asked in the intelligence community, what did you know and when did you know it?&quot; Dennehy says. We&#039;re not dealing with facts; we&#039;re dealing with puzzles and mysteries. If we get something up, we can debate it and talk about what to do. We can have a page that says analysts believe x and some believe y, and we make that transparent so people can look at what documentation supports what viewpoints.&lt;/p&gt;
&lt;p&gt;2. Start small.&lt;/p&gt;
&lt;p&gt;According to Burke, implementing social software is more of a cultural challenge than a technical one. Many of the disparate intelligence agencies had held onto their own data and didn&#039;t share it with one another for years, so changing that paradigm can be difficult, he says. Given this reality, it&#039;s important to start small. At the CIA, the first wiki page they created was a list of acronyms. Since the intelligence community is riddled with them, it became a page people were willing to update (and saw immediate value from). &quot;It&#039;s very simple, and gets to people who are uncomfortable with the tools to quickly make and edit and publish it,&quot; Dennehy says. &quot;If you make those barriers small, they&#039;re more likely to adopt.&quot;&lt;/p&gt;
&lt;p&gt;3. Move information out of traditional enterprise tools such as e-mail.&lt;/p&gt;
&lt;p&gt;In order to change what tools people use to consume and disseminate enterprise content, it&#039;s important to show first that you aren&#039;t making more work for them. As an example, if you find one employee who typically publishes information by e-mailing 50 or so co-workers, encourage him to put that information into the wiki or an internal blog (which the CIA also has) instead. &quot;Move processes out of channels and onto platforms,&quot; Burke says.&quot;If we can take those and replace it with platform based tools, we can capture them on the network.&quot;&lt;/p&gt;
</description>
 <comments>http://www.thestandard.com/news/2008/06/10/things-cia-learned-about-implementing-enterprise-wiki#comments</comments>
 <category domain="http://www.thestandard.com/taxonomy/term/1739">Enterprise</category>
 <category domain="http://www.thestandard.com/taxonomy/term/2361">Enterprise | Collaboration</category>
 <category domain="http://www.thestandard.com/taxonomy/term/1402">IDGNS</category>
 <category domain="http://www.thestandard.com/taxonomy/term/1531">Internet</category>
 <category domain="http://www.thestandard.com/taxonomy/term/1607">Sites</category>
 <category domain="http://www.thestandard.com/taxonomy/term/5667">Software &amp;amp; Web</category>
 <category domain="http://www.thestandard.com/taxonomy/term/2471">Wikis</category>
 <category domain="http://www.thestandard.com/taxonomy/term/98">Breaking News</category>
 <pubDate>Tue, 10 Jun 2008 11:23:58 -0700</pubDate>
 <dc:creator>IDG News Service</dc:creator>
 <guid isPermaLink="false">107716 at http://www.thestandard.com</guid>
</item>
</channel>
</rss>
