<?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: Tee &#8216;em up</title>
	<atom:link href="http://richardkmiller.com/309/tee-em-up/feed" rel="self" type="application/rss+xml" />
	<link>http://richardkmiller.com/309/tee-em-up</link>
	<description></description>
	<lastBuildDate>Tue, 15 May 2012 02:38:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Finding the Right Metaphor &#187; Above Yourself</title>
		<link>http://richardkmiller.com/309/tee-em-up/comment-page-1#comment-144157</link>
		<dc:creator>Finding the Right Metaphor &#187; Above Yourself</dc:creator>
		<pubDate>Fri, 01 Feb 2008 03:54:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.richardkmiller.com/blog/archives/2007/12/tee-em-up#comment-144157</guid>
		<description>[...] Tee &#8216;Em Up - My friend Richard was recently thinking about the way he wrote tasks on his to-do list. He wanted to set up his tasks in such a way that unfamiliar items could be easily tackled. He uses the automatic tees on a driving range to introduce this idea: Growing up in Las Vegas, our favorite place to hit golf balls was Desert Pines. It was 30 minutes away, but it boasted a double decker driving range and automatic tees. After each hit, the tee dropped into the floor and re-emerged with a new ball. You could hit ball after ball without the pesky work of bending down to tee them. You could keep your stance and stay in the zone. [...]</description>
		<content:encoded><![CDATA[<div class='microid-4a38f78a5a6a5c15dc942f869b8cd64eb97ac287'>[...] Tee &#8216;Em Up &#8211; My friend Richard was recently thinking about the way he wrote tasks on his to-do list. He wanted to set up his tasks in such a way that unfamiliar items could be easily tackled. He uses the automatic tees on a driving range to introduce this idea: Growing up in Las Vegas, our favorite place to hit golf balls was Desert Pines. It was 30 minutes away, but it boasted a double decker driving range and automatic tees. After each hit, the tee dropped into the floor and re-emerged with a new ball. You could hit ball after ball without the pesky work of bending down to tee them. You could keep your stance and stay in the zone. [...]</div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Missy</title>
		<link>http://richardkmiller.com/309/tee-em-up/comment-page-1#comment-143848</link>
		<dc:creator>Missy</dc:creator>
		<pubDate>Thu, 10 Jan 2008 22:06:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.richardkmiller.com/blog/archives/2007/12/tee-em-up#comment-143848</guid>
		<description>Somehow you manged to come up with a golf analogy that was new; my dad hasn&#039;t had a new one since I was eight. I&#039;ve had some new things to figure out at work this week at work &amp; when things are technical I find myself overwhelmed. Jimmy&#039;s right, your examples are really good. I just wanted to say thanks - you are the Jon Udell of your peer group; this post has has been on my mind all week &amp; I feel like it made a big difference.</description>
		<content:encoded><![CDATA[<div class='microid-2490d69a9947fe4ab64326eaa719bd2b952637fd'>Somehow you manged to come up with a golf analogy that was new; my dad hasn&#8217;t had a new one since I was eight. I&#8217;ve had some new things to figure out at work this week at work &amp; when things are technical I find myself overwhelmed. Jimmy&#8217;s right, your examples are really good. I just wanted to say thanks &#8211; you are the Jon Udell of your peer group; this post has has been on my mind all week &amp; I feel like it made a big difference.</div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard K Miller</title>
		<link>http://richardkmiller.com/309/tee-em-up/comment-page-1#comment-140785</link>
		<dc:creator>Richard K Miller</dc:creator>
		<pubDate>Wed, 12 Dec 2007 07:07:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.richardkmiller.com/blog/archives/2007/12/tee-em-up#comment-140785</guid>
		<description>Jimmy: Estimating how long it will take to complete a project is a skill I&#039;d like to learn. I&#039;ve always found it perplexing. Joel Spolsky talks about breaking down projects into 4 hour or 1 day blocks, at most, but I find even that difficult for large projects.</description>
		<content:encoded><![CDATA[<div class='microid-781638ceff08110e27cb6063c5cd105a241b5e67'>Jimmy: Estimating how long it will take to complete a project is a skill I&#8217;d like to learn. I&#8217;ve always found it perplexing. Joel Spolsky talks about breaking down projects into 4 hour or 1 day blocks, at most, but I find even that difficult for large projects.</div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jimmy Zimmerman</title>
		<link>http://richardkmiller.com/309/tee-em-up/comment-page-1#comment-140735</link>
		<dc:creator>Jimmy Zimmerman</dc:creator>
		<pubDate>Tue, 11 Dec 2007 19:49:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.richardkmiller.com/blog/archives/2007/12/tee-em-up#comment-140735</guid>
		<description>I find that whenever I&#039;m in a lull and just stare at a task for too long, it&#039;s usually because I&#039;ve described the task in too general of terms. Your examples are really good.

Breaking down your tasks into bite-sized chunks also helps in estimating how much time you&#039;ll need to get things done.

Tee&#039;ing up your tasks like you&#039;ve outlined seems pretty simple and obvious, but I&#039;m amazed at how many times I find myself stumped by a problem that is overcome just by describing what I need to do in more detail. I&#039;m sure I&#039;m not the only one that suffers from this. I think developers and project managers all over the world would benefit from this advice.

Great follow up on your last post! Keep these coming.</description>
		<content:encoded><![CDATA[<div class='microid-ed9303fce8473d7f5bd5119a967f901b0a6e0fd6'>I find that whenever I&#8217;m in a lull and just stare at a task for too long, it&#8217;s usually because I&#8217;ve described the task in too general of terms. Your examples are really good.</p>
<p>Breaking down your tasks into bite-sized chunks also helps in estimating how much time you&#8217;ll need to get things done.</p>
<p>Tee&#8217;ing up your tasks like you&#8217;ve outlined seems pretty simple and obvious, but I&#8217;m amazed at how many times I find myself stumped by a problem that is overcome just by describing what I need to do in more detail. I&#8217;m sure I&#8217;m not the only one that suffers from this. I think developers and project managers all over the world would benefit from this advice.</p>
<p>Great follow up on your last post! Keep these coming.</p></div>
]]></content:encoded>
	</item>
</channel>
</rss>

