<?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>Living Legacy &#187; lists</title>
	<atom:link href="http://www.tiadpeterson.com/tag/lists/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.tiadpeterson.com</link>
	<description>creating a life filled with passion and joy</description>
	<lastBuildDate>Tue, 31 Aug 2010 16:43:12 +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>Writing Statuses: Better than a to-do list?</title>
		<link>http://www.tiadpeterson.com/writing-statuses-better-than-a-to-do-list/</link>
		<comments>http://www.tiadpeterson.com/writing-statuses-better-than-a-to-do-list/#comments</comments>
		<pubDate>Wed, 05 Mar 2008 05:37:00 +0000</pubDate>
		<dc:creator>Tia Peterson</dc:creator>
				<category><![CDATA[Retired Posts]]></category>
		<category><![CDATA[lists]]></category>
		<category><![CDATA[Organization]]></category>
		<category><![CDATA[status memos]]></category>
		<category><![CDATA[Time Management]]></category>
		<category><![CDATA[working from home]]></category>

		<guid isPermaLink="false">http://blog.allamericanadmin.com/writing-statuses-better-than-a-to-do-list/</guid>
		<description><![CDATA[OK so maybe not better, but different in a very good way. I was drafting a status e-mail to one of my clients tonight, and it was amazing the clarity that came as a result of it. When I sit down to write a to-do list, it always fills up with junk! When I sit [...]]]></description>
			<content:encoded><![CDATA[<p>OK so maybe not better, but different in a very good way.</p>
<p>I was drafting a status e-mail to one of my clients tonight, and it was amazing the clarity that came as a result of it. When I sit down to write a to-do list, it always fills up with junk! When I sit down to write a status email &#8211; lo and behold&#8230;a to-do list! Really. I suddenly had my to-do list (or a portion of it) and it came so much more easily to mind than it would have if I had said to myself  &#8220;Self, let&#8217;s come up with a to-do list.&#8221;</p>
<p>So here&#8217;s my advice. Draft status memos for each of your clients (even if they haven&#8217;t asked for one). As you&#8217;re drafting the status, categorize it by completed, and to-do (this week) and to-do (next week &#8211; or just skip next week. One week at a time!). You&#8217;ll discover, if you&#8217;re like me and you have a lot of work, that as you&#8217;re typing up your &#8216;completed&#8217; section, all of your &#8216;to-do&#8217; tasks become very obvious. Write those under the to-do section and sub-categorize them by day. Then, put all of your to-do tasks from all of your clients in a list.</p>
<p>Tada! To-do list magic. AND status memo magic. Status memos are extremely helpful even when they aren&#8217;t requested. For one thing, they help you see how much work you&#8217;re actually doing for your client! Two, they show you how you&#8217;ve spent your time (most of my time today was spent working stuff out with the baby). Three, they put your work right in your face so you have a better understanding of your workload so that you can say &#8220;yes&#8221; or &#8220;no&#8221; with confidence to future requests.</p>
<p>Cheers! Enjoy making your status memos!</p>
<p style='text-align:left'>&copy; 2008 &#8211; 2009, <a href='http://www.tiadpeterson.com'>Tia Peterson</a>. All rights reserved. This text may be reproduced with permission. Please contact tia@tiadpeterson.com to request permission to reuse this content. Thank you!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.tiadpeterson.com/writing-statuses-better-than-a-to-do-list/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
