<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Inbox Difficulties</title>
	<link>http://www.2time-sys.com/2008/02/04/inbox-difficulties/</link>
	<description>Custom-Design Your Own System Now</description>
	<pubDate>Sun, 05 Jul 2009 20:34:01 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Professional Un-productivity &#171; The 2Time Mgt Blog</title>
		<link>http://www.2time-sys.com/2008/02/04/inbox-difficulties/#comment-94</link>
		<dc:creator>Professional Un-productivity &#171; The 2Time Mgt Blog</dc:creator>
		<pubDate>Tue, 01 Apr 2008 16:43:22 +0000</pubDate>
		<guid>http://www.2time-sys.com/2008/02/04/inbox-difficulties/#comment-94</guid>
		<description>[...] 2Time Mgt Blog Tools for Designing Your Own Time Management System      &#171; Inbox&#160;Difficulties The Essentials of&#160;GTD [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] 2Time Mgt Blog Tools for Designing Your Own Time Management System      &laquo; Inbox&nbsp;Difficulties The Essentials of&nbsp;GTD [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Summy</title>
		<link>http://www.2time-sys.com/2008/02/04/inbox-difficulties/#comment-95</link>
		<dc:creator>Summy</dc:creator>
		<pubDate>Mon, 04 Feb 2008 17:33:57 +0000</pubDate>
		<guid>http://www.2time-sys.com/2008/02/04/inbox-difficulties/#comment-95</guid>
		<description>I like the idea of having a clean inbox- and practice it.

Unfortunately it's difficult to require people to keep an empty inbox because everyone has their own system. some people can keep on top of their lists and be productive with an "messy" desk and a full inbox (the people I know that do this use flags to track their lists). Further if someone has a high inbox it could be because they have the most responsibility.

To measure the above I recommend setting standards. If there are hard and easy claims then have 2 buckets (i would have buckets for each type of workflow if they are different), then allow for exceptions- the exceptions don't count. Here's how it would work. each type of work is accounted for and assigned to the right bucket. each bucket has an expectation. People know what they need to do (the buckets should be visible to management so they can monitor that issues are properly handled). There will be some issues that dont fall into a bucket or it has to take a unique workflow so longer times are acceptable for them. dont let people make everything an exception. even some "exceptions" can become routine if they are thought through and accounted for.

Of course you'll need to strengthen your quality assurance procedure to make sure that it is working. with million dollar claims that's essential.

I successfully implemented a similar procedure in my organization. The results were remarkable. Best practices were shared. productivity increased. fire drills decreased. the environment was more relaxed. For me i got an award and a promotion.

Don't get me wrong I'd recommend everyone keep an empty inbox but that's just a symptom.</description>
		<content:encoded><![CDATA[<p>I like the idea of having a clean inbox- and practice it.</p>
<p>Unfortunately it&#8217;s difficult to require people to keep an empty inbox because everyone has their own system. some people can keep on top of their lists and be productive with an &#8220;messy&#8221; desk and a full inbox (the people I know that do this use flags to track their lists). Further if someone has a high inbox it could be because they have the most responsibility.</p>
<p>To measure the above I recommend setting standards. If there are hard and easy claims then have 2 buckets (i would have buckets for each type of workflow if they are different), then allow for exceptions- the exceptions don&#8217;t count. Here&#8217;s how it would work. each type of work is accounted for and assigned to the right bucket. each bucket has an expectation. People know what they need to do (the buckets should be visible to management so they can monitor that issues are properly handled). There will be some issues that dont fall into a bucket or it has to take a unique workflow so longer times are acceptable for them. dont let people make everything an exception. even some &#8220;exceptions&#8221; can become routine if they are thought through and accounted for.</p>
<p>Of course you&#8217;ll need to strengthen your quality assurance procedure to make sure that it is working. with million dollar claims that&#8217;s essential.</p>
<p>I successfully implemented a similar procedure in my organization. The results were remarkable. Best practices were shared. productivity increased. fire drills decreased. the environment was more relaxed. For me i got an award and a promotion.</p>
<p>Don&#8217;t get me wrong I&#8217;d recommend everyone keep an empty inbox but that&#8217;s just a symptom.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
