
<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.0.2" -->
<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>The Scribblebook &#187; Forum: Email Context Audit - Recent Topics</title>
		<link>http://www.unstressedsyllables.com/forum/forum/email-context-audit</link>
		<description>Unstressed Syllables discussion and practice</description>
		<language>en-US</language>
		<pubDate>Fri, 10 Sep 2010 19:36:12 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.0.2</generator>
		<textInput>
			<title><![CDATA[Search]]></title>
			<description><![CDATA[Search all topics from these forums.]]></description>
			<name>q</name>
			<link>http://www.unstressedsyllables.com/forum/search.php</link>
		</textInput>
		<atom:link href="http://www.unstressedsyllables.com/forum/rss/forum/email-context-audit/topics" rel="self" type="application/rss+xml" />

		<item>
			<title>Aaron Pogue on "Writing Exercise Instructions"</title>
			<link>http://www.unstressedsyllables.com/forum/topic/writing-exercise-instructions-4#post-9</link>
			<pubDate>Mon, 11 Jan 2010 16:40:22 +0000</pubDate>
			<dc:creator>Aaron Pogue</dc:creator>
			<guid isPermaLink="false">9@http://www.unstressedsyllables.com/forum/</guid>
			<description>&#60;p&#62;I talked last week about the importance of writing good introductions to establish context (especially for readability down the line), and that message is never more important (or overlooked) than when you're sitting down to write an email.&#60;/p&#62;
&#60;p&#62;We still occasionally run into the big formal business letters and memos on company letterhead, and so we're in the habit of thinking of emails, by contrast, as casual communication. It's certainly less work to put together an email, but as a direct result of that most of our official written communication these days takes place in the form of emails.&#60;/p&#62;
&#60;p&#62;Sure, adding a lot of formal structure to emails would make them just as much of a nuisance as memos and business letters, but at the opposite extreme, leaving out information in the name of convenience will ultimately cause problems.&#60;/p&#62;
&#60;p&#62;So your exercise for this week is an email context audit. Open up your email client (personal or work, whichever you prefer), and look at the last ten non-reply emails you sent -- that is, new emails starting new conversations. Copy out the opening paragraph of each email, and add it to a list, then read over all the items in the list and see how easy it is for you to tell what each email message is talking about. Chances are good you still remember each of those emails, so try to guess how well you'd be able to figure the meaning out a year from now, too.&#60;/p&#62;
&#60;p&#62;Then test yourself. Go back one year, and list the opening paragraphs of ten non-reply emails you sent on this date last year. How many of them make sense to you now?&#60;/p&#62;
&#60;p&#62;This is an audit, a self-evaluation, and there's a real possibility you'll come out of it with a perfect score. If you don't, if you find in your archives a bunch of unintelligible one-line emails or messages that start in the middle of a conversation, take some time to practice improvement. Revisit your ten newer messages, and try writing a short, clear introduction for each of them.
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
