<?xml version="1.0" encoding="utf-8"?>

<rdf:RDF
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  xmlns:admin="http://webns.net/mvcb/"
  xmlns:cc="http://web.resource.org/cc/"
  xmlns="http://purl.org/rss/1.0/">

<channel rdf:about="http://www.markcarey.com/web-dawn/">
<title>Blnowledge Management</title>
<link>http://www.markcarey.com/web-dawn/archives/discuss-blnowledge-management.html</link>
<description>Conversation for Blnowledge Management</description>
<dc:language>en-us</dc:language>
<dc:creator>Mark</dc:creator>
<dc:date>2003-09-25T20:02:00-05:00</dc:date>
<admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=3.31" />


<items>
<rdf:Seq><rdf:li rdf:resource="http://www.markcarey.com/web-dawn/archives/discuss-blnowledge-management.html#000486" />
</rdf:Seq>
</items>

</channel>

<item rdf:about="http://www.markcarey.com/web-dawn/archives/discuss-blnowledge-management.html">
<title>Blnowledge Management</title>
<link>http://www.markcarey.com/web-dawn/archives/discuss-blnowledge-management.html</link>
<description><![CDATA[<p>An <a href="http://studioid.com/pg/blogging_in_corporate_america.php">interesting presentation</a> about blogging as a Knowledge Management tool in large organizations such as Lucent.  To me this makes perfect sense.  One the largest struggles with KM has alway been to make it as unobtrusive for the user as possible - if you have to record 37 pieces of meta about everything you do, it just won't work.  Blogging is both informative and social, yet it inlcudes easy-to-use tools for publishing and XML formats for knowledge aggregation and indexing.  If companies can get employee enthusiastic about blogging, they will have a wealth of new knowledge that just wasn't captured previously.  The challenge, as I see it, is to make it fun and interesting.  So Knowledge Management really boils down to social engineering.</p>

<p>Via <a href="http://www.headshift.com/archives/000260.cfm">Headshift Moments</a> via <a href="http://radio.weblogs.com/0121664/2003/09/18.html#a260">Conversations with Dina</a> via <a href="http://www.mcgeesmusings.net/2003/09/20.html#a3680">McGee's Musings</a> via <a href="http://radio.weblogs.com/0110772/2003/09/23.html#a1125">Seb's Open Research</a></p>]]></description>
<dc:subject>Blogging</dc:subject>
<dc:creator>Mark</dc:creator>
<dc:date>2003-09-25T20:02:00-05:00</dc:date>
</item>

<item rdf:about="http://www.markcarey.com/web-dawn/archives/discuss-blnowledge-management.html">
<title>Blnowledge Management</title>
<link>http://www.markcarey.com/web-dawn/archives/discuss-blnowledge-management.html#000486</link>
<description><![CDATA[<p>I suppose what worries many companies about blogging in the enterprise sphere is the "outward" facing nature of blogs. By this I don't just mean the "publishing to the outside world" perspective, but the relinquishing of central control and structure. Blogs (or K-logs) are a fantastic tool because of their ability to stimulate more free-form and interactive discussions, and create loose groupings of common interest. The more enlightened and Knowledge-management-focused companies out there are doubtless using the reduced "meta" load of blogs to gain these type of advantages (and some are even using project-based wikis etc.), but I know some companies look at blogs as if they would replace their structured approaches, get scared at this and shy away from them. Blogs are neither a panacea nor a disruptive force, just another useful tool in managing, maintaining and distributing knowledge and information.</p>]]></description>
<dc:subject>Blogging</dc:subject>
<dc:creator>Mark Thristan</dc:creator>
<dc:date>2003-09-26T12:08:26-05:00</dc:date>
</item>


</rdf:RDF>