<?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: What can we learn about KM from riding a bike?</title>
	<atom:link href="http://thekmcoach.com/2009/07/what-can-we-learn-about-km-from-riding-a-bike/feed/" rel="self" type="application/rss+xml" />
	<link>http://thekmcoach.com/2009/07/what-can-we-learn-about-km-from-riding-a-bike/</link>
	<description>Making Knowledge Work</description>
	<lastBuildDate>Tue, 18 May 2010 04:05:04 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Matt H</title>
		<link>http://thekmcoach.com/2009/07/what-can-we-learn-about-km-from-riding-a-bike/comment-page-1/#comment-9</link>
		<dc:creator>Matt H</dc:creator>
		<pubDate>Fri, 31 Jul 2009 02:13:06 +0000</pubDate>
		<guid isPermaLink="false">http://kmdfw.com/?p=23#comment-9</guid>
		<description>This article should be sent out to all agents for why their job is so important. Capturing the knowledge, and documenting it into information are core components of the KCS methodology.</description>
		<content:encoded><![CDATA[<p>This article should be sent out to all agents for why their job is so important. Capturing the knowledge, and documenting it into information are core components of the KCS methodology.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lisa Austin</title>
		<link>http://thekmcoach.com/2009/07/what-can-we-learn-about-km-from-riding-a-bike/comment-page-1/#comment-8</link>
		<dc:creator>Lisa Austin</dc:creator>
		<pubDate>Fri, 31 Jul 2009 02:12:03 +0000</pubDate>
		<guid isPermaLink="false">http://kmdfw.com/?p=23#comment-8</guid>
		<description>Great question Deborah.  I had to think about this one for a little...  From my perspective, what you call it is really irrelevant.  That&#039;s why I just use the term knowledge management to mean both information and knowledge...  When it comes right down to it, quick, continuous and fluid feedback loops are best.  What I mean is, it&#039;s critical to constantly learn from each agents personal experiences with a client.  Creating a manual and documenting those experiences is great, even better would be to make it a wiki allowing each agent and the client to continually update with their experiences.  Eliminating the formal publication process reduces the knowledge to information time.  Also, and I known in most cases, this is counter to conventional call center wisdom... I would create time for all agents to come together and connect with each other informally (virtually if necessary).  They could bring to the table their most difficult (or best) call of the week, kind of an after action review process, but maybe focused on only a few calls.   As a leader, it also gives you an opportunity to see who really is building their kowledge - especially your newer agents.  And remember, knowledge sharing is all about relationships, the more you enable your agents to connect and build trust, the more likely they are to go above and beyond to help someone out - by sharing their knowledge.  
Hope that helps.</description>
		<content:encoded><![CDATA[<p>Great question Deborah.  I had to think about this one for a little&#8230;  From my perspective, what you call it is really irrelevant.  That&#8217;s why I just use the term knowledge management to mean both information and knowledge&#8230;  When it comes right down to it, quick, continuous and fluid feedback loops are best.  What I mean is, it&#8217;s critical to constantly learn from each agents personal experiences with a client.  Creating a manual and documenting those experiences is great, even better would be to make it a wiki allowing each agent and the client to continually update with their experiences.  Eliminating the formal publication process reduces the knowledge to information time.  Also, and I known in most cases, this is counter to conventional call center wisdom&#8230; I would create time for all agents to come together and connect with each other informally (virtually if necessary).  They could bring to the table their most difficult (or best) call of the week, kind of an after action review process, but maybe focused on only a few calls.   As a leader, it also gives you an opportunity to see who really is building their kowledge &#8211; especially your newer agents.  And remember, knowledge sharing is all about relationships, the more you enable your agents to connect and build trust, the more likely they are to go above and beyond to help someone out &#8211; by sharing their knowledge.<br />
Hope that helps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deborah D</title>
		<link>http://thekmcoach.com/2009/07/what-can-we-learn-about-km-from-riding-a-bike/comment-page-1/#comment-7</link>
		<dc:creator>Deborah D</dc:creator>
		<pubDate>Fri, 31 Jul 2009 02:10:41 +0000</pubDate>
		<guid isPermaLink="false">http://kmdfw.com/?p=23#comment-7</guid>
		<description>Great way to explain the concepts. I think I now understand the difference between the two much better. However, I do have a question in mind. From the article, It seems to me that information is a physical content that can be written on paper or logged on computer; while knowledge is an abstract concept that people perceive from information they obtain. If what I understand is correct, what is the difference between information management and knowledge management? Or maybe they are inseparable. 

This example below might sounds quite elementary, but I&#039;m really curious about KM. When I worked as an Technical Support Supervisor, I thought having a support manual would be helpful for new agents to learn so that they can catch up to speed in shorter time. It was also good for those difficult problems that agents rarely encountered. A lot of resolutions were obtained by try-and-error, which consumed calling time. I thought it would be good to keep these information or knowledge within the company so the next agent does not need to use the same time as we did. Then, in this example, do you define managing the manual as information or knowledge management? 

Thanks,
Deborah</description>
		<content:encoded><![CDATA[<p>Great way to explain the concepts. I think I now understand the difference between the two much better. However, I do have a question in mind. From the article, It seems to me that information is a physical content that can be written on paper or logged on computer; while knowledge is an abstract concept that people perceive from information they obtain. If what I understand is correct, what is the difference between information management and knowledge management? Or maybe they are inseparable. </p>
<p>This example below might sounds quite elementary, but I&#8217;m really curious about KM. When I worked as an Technical Support Supervisor, I thought having a support manual would be helpful for new agents to learn so that they can catch up to speed in shorter time. It was also good for those difficult problems that agents rarely encountered. A lot of resolutions were obtained by try-and-error, which consumed calling time. I thought it would be good to keep these information or knowledge within the company so the next agent does not need to use the same time as we did. Then, in this example, do you define managing the manual as information or knowledge management? </p>
<p>Thanks,<br />
Deborah</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Art Schlussel</title>
		<link>http://thekmcoach.com/2009/07/what-can-we-learn-about-km-from-riding-a-bike/comment-page-1/#comment-6</link>
		<dc:creator>Art Schlussel</dc:creator>
		<pubDate>Fri, 31 Jul 2009 02:08:42 +0000</pubDate>
		<guid isPermaLink="false">http://kmdfw.com/?p=23#comment-6</guid>
		<description>Great analogy. Knowledge is in the head of the beholder.</description>
		<content:encoded><![CDATA[<p>Great analogy. Knowledge is in the head of the beholder.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
