<?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: Calculating Information Overload &#8211; Find Out Your Organization&#8217;s Cost</title>
	<atom:link href="http://iorgforum.org/blog/index.php/2009/01/13/calculating-information-overload-find-out-your-organizations-cost/feed/" rel="self" type="application/rss+xml" />
	<link>http://iorgforum.org/blog/2009/01/13/calculating-information-overload-find-out-your-organizations-cost/</link>
	<description>IORG members post on information overload topics</description>
	<lastBuildDate>Sun, 22 Nov 2009 14:03:55 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Pankaj</title>
		<link>http://iorgforum.org/blog/2009/01/13/calculating-information-overload-find-out-your-organizations-cost/comment-page-1/#comment-12804</link>
		<dc:creator>Pankaj</dc:creator>
		<pubDate>Wed, 20 May 2009 19:22:51 +0000</pubDate>
		<guid isPermaLink="false">http://iorgforum.org/blog/2009/01/13/calculating-information-overload-find-out-your-organizations-cost/#comment-12804</guid>
		<description>we had recently done a white paper on management of the email deluge. much of the problem stems from using email for &quot;collaborative purposes&quot; - a boss delegating tasks and asking for updates, collaboration on files, managing schedules. a single mail causes a torrent, and youre forever digging through your inbox. 

email is a &quot;push&quot; medium, and you constantly feel like you&#039;re being poked in your ribs to go check your mail.  shifting to &quot;pull&quot; collaboration tools (document management, task management, forums) not only relieves the email glut, but also smoothen information management in the organization, and the effectiveness of teams working together. 

you can see the white paper at - http://www.hyperoffice.com/business-email-overload/

we also have a guest speaker, tech expert James Gaskin from networkworld.com and itworld.com presenting a webinar on the subject on the 28th of May at 2PM EST</description>
		<content:encoded><![CDATA[<p>we had recently done a white paper on management of the email deluge. much of the problem stems from using email for &#8220;collaborative purposes&#8221; &#8211; a boss delegating tasks and asking for updates, collaboration on files, managing schedules. a single mail causes a torrent, and youre forever digging through your inbox. </p>
<p>email is a &#8220;push&#8221; medium, and you constantly feel like you&#8217;re being poked in your ribs to go check your mail.  shifting to &#8220;pull&#8221; collaboration tools (document management, task management, forums) not only relieves the email glut, but also smoothen information management in the organization, and the effectiveness of teams working together. </p>
<p>you can see the white paper at &#8211; <a href="http://www.hyperoffice.com/business-email-overload/" rel="nofollow">http://www.hyperoffice.com/business-email-overload/</a></p>
<p>we also have a guest speaker, tech expert James Gaskin from networkworld.com and itworld.com presenting a webinar on the subject on the 28th of May at 2PM EST</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Spira</title>
		<link>http://iorgforum.org/blog/2009/01/13/calculating-information-overload-find-out-your-organizations-cost/comment-page-1/#comment-4270</link>
		<dc:creator>Jonathan Spira</dc:creator>
		<pubDate>Fri, 16 Jan 2009 00:20:43 +0000</pubDate>
		<guid isPermaLink="false">http://iorgforum.org/blog/2009/01/13/calculating-information-overload-find-out-your-organizations-cost/#comment-4270</guid>
		<description>Thanks Michael.  Glad you like it.

Regarding the question of deciding what can be stored for later retrieval, etc.... that very act of making that decision is enough of an interruption, but no, we haven&#039;t really studied that question. Not sure if anyone else has.

Your scanning method probably serves you (and many of us) fairly well but given the content explosion, we will always miss important information as well.

So onto your &quot;real question&quot;:  that issue has come up anecdotally in our research but since many organizations have multiple &quot;rules&quot; about what has to be read when and how, we would put most of them in the same bucket for the moment.  

A few years ago, a newspaper reporter told me of an organization where employees in a particular department had to reply to their manager&#039;s e-mails within 15 minutes - or be on the receiving end of a phone call from an angry manager.  Members of the department spent a good part of the day checking e-mail so that they would not get yelled at.</description>
		<content:encoded><![CDATA[<p>Thanks Michael.  Glad you like it.</p>
<p>Regarding the question of deciding what can be stored for later retrieval, etc&#8230;. that very act of making that decision is enough of an interruption, but no, we haven&#8217;t really studied that question. Not sure if anyone else has.</p>
<p>Your scanning method probably serves you (and many of us) fairly well but given the content explosion, we will always miss important information as well.</p>
<p>So onto your &#8220;real question&#8221;:  that issue has come up anecdotally in our research but since many organizations have multiple &#8220;rules&#8221; about what has to be read when and how, we would put most of them in the same bucket for the moment.  </p>
<p>A few years ago, a newspaper reporter told me of an organization where employees in a particular department had to reply to their manager&#8217;s e-mails within 15 minutes &#8211; or be on the receiving end of a phone call from an angry manager.  Members of the department spent a good part of the day checking e-mail so that they would not get yelled at.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Josefowicz</title>
		<link>http://iorgforum.org/blog/2009/01/13/calculating-information-overload-find-out-your-organizations-cost/comment-page-1/#comment-4222</link>
		<dc:creator>Michael Josefowicz</dc:creator>
		<pubDate>Tue, 13 Jan 2009 22:16:36 +0000</pubDate>
		<guid isPermaLink="false">http://iorgforum.org/blog/2009/01/13/calculating-information-overload-find-out-your-organizations-cost/#comment-4222</guid>
		<description>Nice calculator.

Just curious if anyone done an analysis or have thoughts about easy ways to decide very quickly what can be stored for later retrieval if necessary, but doesn&#039;t have to be read now, thus interrupting work. I know that I use my Google Reader for this function.

My decision making rule is that the default position is &quot;I don&#039;t have to read this.&quot; It turns out that applies to between  80% to 90%of the feeds, just by scanning headlines.

My real question is:
Has anyone mapped  the power relations in large organizations and how that creates more IO than is necessary. When I worked in a large formal organization the rule was if it came from a superior the default was it had to be opened and scanned. Usually wasting lots of time and interrupting real work.</description>
		<content:encoded><![CDATA[<p>Nice calculator.</p>
<p>Just curious if anyone done an analysis or have thoughts about easy ways to decide very quickly what can be stored for later retrieval if necessary, but doesn&#8217;t have to be read now, thus interrupting work. I know that I use my Google Reader for this function.</p>
<p>My decision making rule is that the default position is &#8220;I don&#8217;t have to read this.&#8221; It turns out that applies to between  80% to 90%of the feeds, just by scanning headlines.</p>
<p>My real question is:<br />
Has anyone mapped  the power relations in large organizations and how that creates more IO than is necessary. When I worked in a large formal organization the rule was if it came from a superior the default was it had to be opened and scanned. Usually wasting lots of time and interrupting real work.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
