<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Chris LeCompte &#187; Effective Monday</title>
	<atom:link href="http://www.clecompte.com/category/effective-monday/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.clecompte.com</link>
	<description></description>
	<lastBuildDate>Mon, 26 Jul 2010 22:25:34 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Effective Monday: Effectively Using Batch Processing to Get Things Done on Projects</title>
		<link>http://www.clecompte.com/batch-processing-to-get-things-done-on-projects/</link>
		<comments>http://www.clecompte.com/batch-processing-to-get-things-done-on-projects/#comments</comments>
		<pubDate>Mon, 14 Dec 2009 13:24:03 +0000</pubDate>
		<dc:creator>Chris LeCompte</dc:creator>
				<category><![CDATA[Effective Monday]]></category>
		<category><![CDATA[batch processing]]></category>
		<category><![CDATA[batch zone]]></category>
		<category><![CDATA[batches]]></category>

		<guid isPermaLink="false">http://www.clecompte.com/?p=521</guid>
		<description><![CDATA[Batch processing is the act of organizing project tasks and activities into time chunks that you can knock out one at a time. This isn’t a new concept and you’ve likely heard about it before. How can we more effectively implement batch processing for our projects? Here are a few key pointers to keep you [...]]]></description>
			<content:encoded><![CDATA[<p>Batch processing is the act of organizing project tasks and activities into time chunks that you can knock out one at a time. This isn’t a new concept and you’ve likely heard about it before.</p>
<p>How can we more effectively implement batch processing for our projects? Here are a few key pointers to keep you on track and make sure those projects get done.</p>
<ul>
<li>Determine what times of the day you think you’ll be most effective. This means the times you believe you’ll be most alert, focused and distraction-free. Use these times as your “batch zones” to start processing.</li>
<li>During your batch zones, close off any potentially distracting applications and devices. Shut down email, close Twitter and set your phone to silent.</li>
<li>Plan your day ahead of batch zones. Figure out which projects need the most attention. That way you won’t be wasting your batch zones trying to find something to work on.</li>
<li>Set mini-goals for your batch zones. Instead of just planning to work straight for three hours on a project, layout specifically what you want to accomplish. With an end in sight, batch processing will be more manageable.</li>
<li>Organize your materials and notes before your batch zones. Every moment you’re batch processing should be dedicated toward project work.</li>
</ul>
<p>Have any batch processing tips of your own? Feel free to share in the comments section.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.clecompte.com/batch-processing-to-get-things-done-on-projects/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Effective Monday: Taking Projects Day by Day</title>
		<link>http://www.clecompte.com/taking-projects-day-by-day/</link>
		<comments>http://www.clecompte.com/taking-projects-day-by-day/#comments</comments>
		<pubDate>Mon, 07 Dec 2009 18:03:32 +0000</pubDate>
		<dc:creator>Chris LeCompte</dc:creator>
				<category><![CDATA[Effective Monday]]></category>
		<category><![CDATA[chunks]]></category>
		<category><![CDATA[daily]]></category>
		<category><![CDATA[day]]></category>
		<category><![CDATA[effective]]></category>
		<category><![CDATA[effectiveness]]></category>
		<category><![CDATA[organize]]></category>
		<category><![CDATA[plan]]></category>
		<category><![CDATA[planning]]></category>
		<category><![CDATA[stress]]></category>

		<guid isPermaLink="false">http://www.clecompte.com/?p=491</guid>
		<description><![CDATA[When we look at projects from a bird’s eye view, it can be a stressful revelation. We see all of the milestones, actions, communication and deliverables that must occur in order to get things done. In my experience, and I’m certain in the experience of many others, this can cause us to shut down mentally [...]]]></description>
			<content:encoded><![CDATA[<p>When we look at projects from a bird’s eye view, it can be a stressful revelation. We see all of the milestones, actions, communication and deliverables that must occur in order to get things done.</p>
<p>In my experience, and I’m certain in the experience of many others, this can cause us to shut down mentally and procrastinate. Oftentimes, this stress can result in a lack of confidence, exhaustion, helplessness and a host of other negative feelings.</p>
<p>How can we get over this hump and become more effective with our projects? My solution is to plan each day into manageable chunks. Every morning, I’ll pull out my notepad, take the cap off my pen and start writing out what I need to accomplish for the day. At first, I found myself just regurgitating all of my projects, but I soon learned to write down only things I could feasibly accomplish in one to three hours.</p>
<p>Time is an essential component to this activity because we’re all limited to a fixed amount of it each day. If you write down too many project tasks, that feeling of being overwhelmed will return. If you don’t write down enough, you’ll feel as if you aren’t doing enough. Plan each specific project item by listing out how much time you think it’ll take and then commit to it.<span id="more-491"></span></p>
<p>Here’s a sample of my project and client plan for the day:</p>
<p><strong>Projects:</strong></p>
<ul>
<li>New Blog Post – 45 minutes</li>
<li>Client A Development Work – 2 hours</li>
<li>Client B Development Work – 2 hours</li>
<li>Client C Design Work – 1 hour</li>
<li>Client D Design Work – 2-3 hours</li>
</ul>
<p><strong>To-Do Items:</strong></p>
<ul>
<li>Review items from accountant</li>
<li>Review Client E update requests</li>
<li>Review Client F update requests</li>
<li>Review Client G update requests</li>
<li>Review weekly notes</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.clecompte.com/taking-projects-day-by-day/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
