<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Knowledge-Management on Dr. Hitesh Sarda</title>
		<link>https://hitesh.in/tags/knowledge-management/</link>
		<description>Recent content in Knowledge-Management on Dr. Hitesh Sarda</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Wed, 28 Jul 2021 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://hitesh.in/tags/knowledge-management/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Information Overload</title>
				<link>https://hitesh.in/2021/information-overload/</link>
				<pubDate>Wed, 28 Jul 2021 00:00:00 +0000</pubDate>
				<guid>https://hitesh.in/2021/information-overload/</guid>
				<description>&lt;p&gt;There is a deluge of knowledge today. On platforms like YouTube and LinkedIn, there are so many thought leaders who could be followed for great insights. But how do you absorb, retain and apply this knowledge? This has become the real challenge.&lt;/p&gt;&#xA;&lt;h3 id=&#34;my-2-part-system-for-knowledge-management&#34;&gt;My 2 part system for knowledge management&lt;/h3&gt;&#xA;&lt;p&gt;1.&lt;strong&gt;Store and Index.&lt;/strong&gt; No, I am not building a knowledge base, database, or even write things done (which I should!). I tend to commit things to memory. What is important is to be able to recall on demand.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
