<?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>kmzen &#187; knowledge management</title>
	<atom:link href="http://kmzen.com/tag/knowledge-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://kmzen.com</link>
	<description>Knowledge Management, Meet Zen</description>
	<lastBuildDate>Wed, 27 Apr 2011 19:37:34 +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>A Tale of Two Portals: Target Audience and Portal Taxonomy</title>
		<link>http://kmzen.com/2010/02/28/a-tale-of-two-portals-target-audience-and-portal-taxonomy/</link>
		<comments>http://kmzen.com/2010/02/28/a-tale-of-two-portals-target-audience-and-portal-taxonomy/#comments</comments>
		<pubDate>Sun, 28 Feb 2010 09:48:54 +0000</pubDate>
		<dc:creator>Robert Bruns</dc:creator>
				<category><![CDATA[portals]]></category>
		<category><![CDATA[audience]]></category>
		<category><![CDATA[knowledge management]]></category>
		<category><![CDATA[taxonomy]]></category>

		<guid isPermaLink="false">http://kmzen.com/?p=29</guid>
		<description><![CDATA[<p>Consider the distinct methods of building information portals and you can respect the complexity involved in getting the right information in the right hands. </p> <p>The Two Dimensional Approach</p> <p>Portal A is built with functions to aggregate private information to a public space.  This involves setting up the appropriate plumbing, arranging hierarchies, and maintaining intricate access [...]]]></description>
			<content:encoded><![CDATA[<p>Consider the distinct methods of building information portals and you can respect the complexity involved in getting the right information in the right hands. </p>
<p><strong>The Two Dimensional Approach</strong></p>
<p>Portal A is built with functions to aggregate private information to a public space.  This involves setting up the appropriate plumbing, arranging hierarchies, and maintaining intricate <a href="http://en.wikipedia.org/wiki/Access_control_list">access control lists</a>.</p>
<p>Portal B is built with <a href="http://en.wikipedia.org/wiki/Target_audience">target audience</a>, everything is built horizontally, complex rules spring up for who sees what and when.</p>
<p>The challange with both approaches <span style="color: #000000;">standardization across roles and competency levels</span>.</p>
<p><strong>The Role Based Approach</strong></p>
<p><a href="http://en.wikipedia.org/wiki/Glocalisation"><span style="color: #000000;">Glocal</span></a><span style="color: #004c00;"><span style="color: #000000;"> thought is just as important to information portals as it is to the flat world.</span> </span> This involves a design that maximizes <a href="http://en.wikipedia.org/wiki/Universal_usability">usability</a> for different customers while simultaneously improving the efficiency of information workers.  <a href="http://en.wikipedia.org/wiki/Web_syndication">Syndication</a> of data is paramount for discovering interdependency of information, and <a href="http://en.wikipedia.org/wiki/Aggregator">aggregation</a> of performance metrics to digital dashboards is a mandatory requirement for competitive advantage.</p>
<p>Devising a system to allow <a href="http://en.wikipedia.org/wiki/Agile_Manifesto">agile</a> local control while nodding and respecting overlaps will put you ahead in the game.  The challenge here is balance.</p>
<p><span style="color: #000000;">It can be the best of times, it can be the worst of times</span> depending on a slew of variables and how you handle them.</p>
]]></content:encoded>
			<wfw:commentRss>http://kmzen.com/2010/02/28/a-tale-of-two-portals-target-audience-and-portal-taxonomy/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>Practical Application of Knowledge Management using SharePoint Content Types</title>
		<link>http://kmzen.com/2010/02/24/hello-world/</link>
		<comments>http://kmzen.com/2010/02/24/hello-world/#comments</comments>
		<pubDate>Wed, 24 Feb 2010 02:58:50 +0000</pubDate>
		<dc:creator>Robert Bruns</dc:creator>
				<category><![CDATA[knowledge management]]></category>
		<category><![CDATA[SharePoint]]></category>
		<category><![CDATA[content types]]></category>
		<category><![CDATA[document management]]></category>

		<guid isPermaLink="false">http://atxconsultants.com/_sites/kmzen.com/?p=1</guid>
		<description><![CDATA[<p>The Scenario:  Organizations live in stove pipes.  Often this is in the form of departments responsible for different competencies such as accounting, finance, market, information technology, and management.  Interdependency and overlap are overlooked in organizing the intellectual property produced.  All departments produce &#8216;Products,&#8217; so we need to create a content type in SharePoint to bridge the [...]]]></description>
			<content:encoded><![CDATA[<p><strong>The Scenario:</strong>  Organizations live in stove pipes.  Often this is in the form of departments responsible for different competencies such as accounting, finance, market, information technology, and management.  Interdependency and overlap are overlooked in organizing the intellectual property produced.  All departments produce &#8216;Products,&#8217; so we need to create a <a href="http://msdn.microsoft.com/en-us/library/ms472236.aspx">content type</a> in SharePoint to bridge the gaps.  The &#8216;Products&#8217; content type needs to be created and the appropriate metadata columns assigned.</p>
<p><strong>To make it happen</strong> we must set up a <a href="http://technet.microsoft.com/en-us/library/cc742548.aspx">site collection</a> level content type and inherit throughout all the sites that create &#8216;products.&#8217;  Once we have the content type established, it&#8217;s easy to <a href="http://technet.microsoft.com/en-us/library/cc263473.aspx">associate with document libraries</a> and subsequently <a href="http://office.microsoft.com/en-us/sharepointtechnology/HA100242801033.aspx">create templates</a> for re-usability.</p>
<p><strong>Some unique challanges</strong> that arise deal with handling large document libraries, the size of your content databases, and synching content types across site collections.  <a href="http://office.microsoft.com/en-us/sharepointtechnology/HA101736671033.aspx">Managing large lists</a> and traversing content types should be much easier in <a href="http://technet.microsoft.com/en-us/library/ee519603(office.14).aspx">SharePoint 2010</a>, I have my fingers crossed.</p>
<p><strong>In conclusion</strong>, setting up content types at an enterprise level pays off in organzation that produce thousands of documents.  Do you have individuals that want to search documents within this date range that transcends departments pertaining to &#8216;X?,&#8230;&#8217; no problem.</p>
<p><strong>The technology</strong> is a slam dunk, <strong>the art</strong> is in the vision.</p>
]]></content:encoded>
			<wfw:commentRss>http://kmzen.com/2010/02/24/hello-world/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
	</channel>
</rss>

