<?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"
	>
<channel>
	<title>Comments on: Microtasks</title>
	<atom:link href="http://www.stevepavlina.com/blog/2007/07/microtasks/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.stevepavlina.com/blog/2007/07/microtasks/</link>
	<description>Personal Development for Smart People</description>
	<pubDate>Thu, 24 Jul 2008 22:25:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Mind Petals: Young Entrepreneur Network &#187; Blog Archive &#187; Microtasking for Improved Productivity</title>
		<link>http://www.stevepavlina.com/blog/2007/07/microtasks/#comment-52756</link>
		<dc:creator>Mind Petals: Young Entrepreneur Network &#187; Blog Archive &#187; Microtasking for Improved Productivity</dc:creator>
		<pubDate>Wed, 26 Sep 2007 12:42:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevepavlina.com/blog/2007/07/microtasks/#comment-52756</guid>
		<description>[...] Microtasking has been explained in great detail by Steve Pavlina in his article on Microtasks . The article explains how focusing on just the next step can keep you going towards the end of the process with much less effort than thinking of the end itself. [...]</description>
		<content:encoded><![CDATA[<p>[...] Microtasking has been explained in great detail by Steve Pavlina in his article on Microtasks . The article explains how focusing on just the next step can keep you going towards the end of the process with much less effort than thinking of the end itself. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Breaking Goals Down Into Microtasks at FreshBlogger</title>
		<link>http://www.stevepavlina.com/blog/2007/07/microtasks/#comment-48804</link>
		<dc:creator>Breaking Goals Down Into Microtasks at FreshBlogger</dc:creator>
		<pubDate>Fri, 27 Jul 2007 11:00:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevepavlina.com/blog/2007/07/microtasks/#comment-48804</guid>
		<description>[...] Steve Pavlina recently wrote an article about microtasks and describes them this way: A solution I’ve found more effective is to break a large project down into a lengthy list of “microtasks,” planning it all the way from beginning to end if possible. A microtask is a very basic action item, so small that you’d be hard pressed to break it down any further without it being ridiculous to do so. An example of a microtask is to make a 5-minute phone call. If you have to break it down into dialing the phone number, you’re going too far. [...]</description>
		<content:encoded><![CDATA[<p>[...] Steve Pavlina recently wrote an article about microtasks and describes them this way: A solution I’ve found more effective is to break a large project down into a lengthy list of “microtasks,” planning it all the way from beginning to end if possible. A microtask is a very basic action item, so small that you’d be hard pressed to break it down any further without it being ridiculous to do so. An example of a microtask is to make a 5-minute phone call. If you have to break it down into dialing the phone number, you’re going too far. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Saving Time and Reducing Errors With Checklists &#8212; Keener Living</title>
		<link>http://www.stevepavlina.com/blog/2007/07/microtasks/#comment-48703</link>
		<dc:creator>Saving Time and Reducing Errors With Checklists &#8212; Keener Living</dc:creator>
		<pubDate>Thu, 26 Jul 2007 11:48:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevepavlina.com/blog/2007/07/microtasks/#comment-48703</guid>
		<description>[...] Recently Steve Pavlina wrote an article on &#8220;microtasks,&#8221; talking about breaking activities into doable bits. I am not sure why Steve did not use David Allen&#8217;s more common &#8220;Next Action&#8221; terminology &#8230; perhaps he thinks David&#8217;s phrase has been overused and is losing its effectiveness. Maybe he is right, and maybe some new terminology will revitalize the concept for some people. [...]</description>
		<content:encoded><![CDATA[<p>[...] Recently Steve Pavlina wrote an article on &#8220;microtasks,&#8221; talking about breaking activities into doable bits. I am not sure why Steve did not use David Allen&#8217;s more common &#8220;Next Action&#8221; terminology &#8230; perhaps he thinks David&#8217;s phrase has been overused and is losing its effectiveness. Maybe he is right, and maybe some new terminology will revitalize the concept for some people. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Business Hacks &#187; Harness the Power of Microtasks on BNET</title>
		<link>http://www.stevepavlina.com/blog/2007/07/microtasks/#comment-48584</link>
		<dc:creator>Business Hacks &#187; Harness the Power of Microtasks on BNET</dc:creator>
		<pubDate>Tue, 24 Jul 2007 14:01:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevepavlina.com/blog/2007/07/microtasks/#comment-48584</guid>
		<description>[...] Struggling to get started on a big project? Stuck at the halfway point? Perhaps it&#8217;s time for a different approach. Personal-development blogger Steve Pavlina suggests breaking a large project down into &#8220;microtasks&#8221; &#8212; small, easily accomplished action items that can be completed in under 30 minutes. Here&#8217;s the idea in a nutshell: A microtask outline is like a recipe. When you follow a recipe, you’re able to focus on the process of doing without having to worry about how you’re going to do it. You just need to follow the steps exactly as they’re written. Similarly, when you create a microtask outline for a project, you separate planning from doing. This helps the action phase go more smoothly, and it’s easier to slide into a productive flow. You know that if you follow your outline, you’re going to get a result. It may not be perfect, but it will get done. [...]</description>
		<content:encoded><![CDATA[<p>[...] Struggling to get started on a big project? Stuck at the halfway point? Perhaps it&#8217;s time for a different approach. Personal-development blogger Steve Pavlina suggests breaking a large project down into &#8220;microtasks&#8221; &#8212; small, easily accomplished action items that can be completed in under 30 minutes. Here&#8217;s the idea in a nutshell: A microtask outline is like a recipe. When you follow a recipe, you’re able to focus on the process of doing without having to worry about how you’re going to do it. You just need to follow the steps exactly as they’re written. Similarly, when you create a microtask outline for a project, you separate planning from doing. This helps the action phase go more smoothly, and it’s easier to slide into a productive flow. You know that if you follow your outline, you’re going to get a result. It may not be perfect, but it will get done. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Are Your Action Steps Too Complex? Or Too Simple?</title>
		<link>http://www.stevepavlina.com/blog/2007/07/microtasks/#comment-47634</link>
		<dc:creator>Are Your Action Steps Too Complex? Or Too Simple?</dc:creator>
		<pubDate>Tue, 17 Jul 2007 22:45:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevepavlina.com/blog/2007/07/microtasks/#comment-47634</guid>
		<description>[...] Steve Pavlina has a wonderful post analyzing these two approaches, and then showing a happy medium between the two.  This is straight outta the GTD methodology, known as Next Actions.   Next actions are simple the  &#8220;next action&#8221; needed to complete a project. [...]</description>
		<content:encoded><![CDATA[<p>[...] Steve Pavlina has a wonderful post analyzing these two approaches, and then showing a happy medium between the two.  This is straight outta the GTD methodology, known as Next Actions.   Next actions are simple the  &#8220;next action&#8221; needed to complete a project. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
