<?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: There&#8217;s a Time and Place for Long Prose &#8211; Email Is Rarely It</title>
	<atom:link href="http:///2008/09/28/theres-a-time-and-place-for-long-prose-email-is-rarely-it/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gtdtimes.com/2008/09/28/theres-a-time-and-place-for-long-prose-email-is-rarely-it/</link>
	<description>The Hub for All Things GTD</description>
	<lastBuildDate>Wed, 08 Feb 2012 20:27:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Fresh Focus&#8230;On Productivity! &#187; Blog Archive &#187; GTD Mastery 100: Part XX &#8211; Reading, Writing, and Calling</title>
		<link>http://www.gtdtimes.com/2008/09/28/theres-a-time-and-place-for-long-prose-email-is-rarely-it/comment-page-1/#comment-1554</link>
		<dc:creator>Fresh Focus&#8230;On Productivity! &#187; Blog Archive &#187; GTD Mastery 100: Part XX &#8211; Reading, Writing, and Calling</dc:creator>
		<pubDate>Tue, 06 Jan 2009 05:00:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.gtdtimes.com/2008/09/28/theres-a-time-and-place-for-long-prose-email-is-rarely-it/#comment-1554</guid>
		<description>[...] it take research from someone else, then it goes into ‚ÄúWaiting‚Äù status. But as reminded by the article at GTD Times, be succinct and to the point in your email responses. No need for&#160; a lengthy [...]</description>
		<content:encoded><![CDATA[<p>[...] it take research from someone else, then it goes into ‚ÄúWaiting‚Äù status. But as reminded by the article at GTD Times, be succinct and to the point in your email responses. No need for&#160; a lengthy [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Virtual Handshake Blog &#124; &#187; Email Etiquette and Productivity</title>
		<link>http://www.gtdtimes.com/2008/09/28/theres-a-time-and-place-for-long-prose-email-is-rarely-it/comment-page-1/#comment-1131</link>
		<dc:creator>The Virtual Handshake Blog &#124; &#187; Email Etiquette and Productivity</dc:creator>
		<pubDate>Sat, 25 Oct 2008 03:10:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.gtdtimes.com/2008/09/28/theres-a-time-and-place-for-long-prose-email-is-rarely-it/#comment-1131</guid>
		<description>[...] There</description>
		<content:encoded><![CDATA[<p>[...] There</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TesTeq</title>
		<link>http://www.gtdtimes.com/2008/09/28/theres-a-time-and-place-for-long-prose-email-is-rarely-it/comment-page-1/#comment-1057</link>
		<dc:creator>TesTeq</dc:creator>
		<pubDate>Fri, 03 Oct 2008 07:12:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.gtdtimes.com/2008/09/28/theres-a-time-and-place-for-long-prose-email-is-rarely-it/#comment-1057</guid>
		<description>@Scott Allen:

1) You wrote: &quot;So why not browse the web with Lynx? Why format documents at all? Why not just put everything in Courier 10 and be done with it?&quot;

Very good questions, indeed. I would add some pictures in Courier 10 ASCII art. ;-)

2) I agree that we‚Äôll just have to agree to disagree. But your conclusion about &quot;the rest of the world&quot; goes too far. Maybe you are missing something when the recipient of the fancy formatted message cannot dig up the diamonds from the pile of visual clutter. I think that the main problem with html e-mails is that many people try to replace the real information with the meaningless &quot;chrome&quot;.

3) As you can see I am a big fan of the numbered lists so I agree with the main theme of your post.</description>
		<content:encoded><![CDATA[<p>@Scott Allen:</p>
<p>1) You wrote: &#8220;So why not browse the web with Lynx? Why format documents at all? Why not just put everything in Courier 10 and be done with it?&#8221;</p>
<p>Very good questions, indeed. I would add some pictures in Courier 10 ASCII art. <img src='/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>2) I agree that we‚Äôll just have to agree to disagree. But your conclusion about &#8220;the rest of the world&#8221; goes too far. Maybe you are missing something when the recipient of the fancy formatted message cannot dig up the diamonds from the pile of visual clutter. I think that the main problem with html e-mails is that many people try to replace the real information with the meaningless &#8220;chrome&#8221;.</p>
<p>3) As you can see I am a big fan of the numbered lists so I agree with the main theme of your post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Allen</title>
		<link>http://www.gtdtimes.com/2008/09/28/theres-a-time-and-place-for-long-prose-email-is-rarely-it/comment-page-1/#comment-1052</link>
		<dc:creator>David Allen</dc:creator>
		<pubDate>Wed, 01 Oct 2008 22:11:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.gtdtimes.com/2008/09/28/theres-a-time-and-place-for-long-prose-email-is-rarely-it/#comment-1052</guid>
		<description>Hey, nephew (Scott)...

Great advice. I just read this, and haven&#039;t started to implement it yet, consciously. But intuitively it resonates a ton. 

Bigger Issue/Opp: think about the structure and format of the message based upon the nature of the content and substance. (Reference, for you GTD Connect members, my InConversation interview with Alan Nelson). I think there are tons of examples of this being done well or poorly, and it&#039;s a great frame for clarifying at least some of the fog.

Thanks!

David</description>
		<content:encoded><![CDATA[<p>Hey, nephew (Scott)&#8230;</p>
<p>Great advice. I just read this, and haven&#8217;t started to implement it yet, consciously. But intuitively it resonates a ton. </p>
<p>Bigger Issue/Opp: think about the structure and format of the message based upon the nature of the content and substance. (Reference, for you GTD Connect members, my InConversation interview with Alan Nelson). I think there are tons of examples of this being done well or poorly, and it&#8217;s a great frame for clarifying at least some of the fog.</p>
<p>Thanks!</p>
<p>David</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Allen</title>
		<link>http://www.gtdtimes.com/2008/09/28/theres-a-time-and-place-for-long-prose-email-is-rarely-it/comment-page-1/#comment-1044</link>
		<dc:creator>Scott Allen</dc:creator>
		<pubDate>Tue, 30 Sep 2008 07:15:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.gtdtimes.com/2008/09/28/theres-a-time-and-place-for-long-prose-email-is-rarely-it/#comment-1044</guid>
		<description>&gt; Besides I think that fancy formatting is 
&gt; just a clutter around the real information.

So why not browse the web with Lynx? Why format documents at all? Why not just put everything in Courier 10 and be done with it?

For most people, formatting makes for more effective communication, regardless of the medium.

Guess we&#039;ll just have to agree to disagree TesTeq, and you and Steve Gibson can just miss out on communicating with the rest of the world who are just using the default settings on their email clients.  ;-)</description>
		<content:encoded><![CDATA[<p>&gt; Besides I think that fancy formatting is<br />
&gt; just a clutter around the real information.</p>
<p>So why not browse the web with Lynx? Why format documents at all? Why not just put everything in Courier 10 and be done with it?</p>
<p>For most people, formatting makes for more effective communication, regardless of the medium.</p>
<p>Guess we&#8217;ll just have to agree to disagree TesTeq, and you and Steve Gibson can just miss out on communicating with the rest of the world who are just using the default settings on their email clients.  <img src='/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TesTeq</title>
		<link>http://www.gtdtimes.com/2008/09/28/theres-a-time-and-place-for-long-prose-email-is-rarely-it/comment-page-1/#comment-1043</link>
		<dc:creator>TesTeq</dc:creator>
		<pubDate>Tue, 30 Sep 2008 06:21:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.gtdtimes.com/2008/09/28/theres-a-time-and-place-for-long-prose-email-is-rarely-it/#comment-1043</guid>
		<description>@owstarr:

As Scott Allen wrote there are significant security and privacy issues with html e-mail (at least in current implementations). On this topic I am with Steve Gibson (&quot;Security Now!&quot; podcast). He deletes every html e-mail before reading. :-)

Besides I think that fancy formatting is just a clutter around the real information.</description>
		<content:encoded><![CDATA[<p>@owstarr:</p>
<p>As Scott Allen wrote there are significant security and privacy issues with html e-mail (at least in current implementations). On this topic I am with Steve Gibson (&#8220;Security Now!&#8221; podcast). He deletes every html e-mail before reading. <img src='/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Besides I think that fancy formatting is just a clutter around the real information.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Allen</title>
		<link>http://www.gtdtimes.com/2008/09/28/theres-a-time-and-place-for-long-prose-email-is-rarely-it/comment-page-1/#comment-1039</link>
		<dc:creator>Scott Allen</dc:creator>
		<pubDate>Mon, 29 Sep 2008 15:43:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.gtdtimes.com/2008/09/28/theres-a-time-and-place-for-long-prose-email-is-rarely-it/#comment-1039</guid>
		<description>And thanks, James, for sharing your experience. And you&#039;re right -- the specifics of the formatting are probably well within the realm of personal preference. The key elements are the numbered list and a scannable topic phrase or sentence.</description>
		<content:encoded><![CDATA[<p>And thanks, James, for sharing your experience. And you&#8217;re right &#8212; the specifics of the formatting are probably well within the realm of personal preference. The key elements are the numbered list and a scannable topic phrase or sentence.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Allen</title>
		<link>http://www.gtdtimes.com/2008/09/28/theres-a-time-and-place-for-long-prose-email-is-rarely-it/comment-page-1/#comment-1038</link>
		<dc:creator>Scott Allen</dc:creator>
		<pubDate>Mon, 29 Sep 2008 15:41:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.gtdtimes.com/2008/09/28/theres-a-time-and-place-for-long-prose-email-is-rarely-it/#comment-1038</guid>
		<description>I&#039;ve heard a few security/privacy specialists recommend using plain-text email, and a few Unix/Linux geeks complain about it, but the fact of the matter is that most people use HTML email. It&#039;s the default setting in Outlook, Outlook Express, GMail, etc.

Besides accommodating the text-based Unix/Linux fanatics, the main other arguments against HTML email are that images can be used as an email tracking mechanism and that links can be disguised to be something other than they actually are. In theory, malicious code could also be embedded in an HTML email.

In practice, though, Outlook, GMail, et al., all have various protection mechanisms against those things. Plus you should be running anti-virus/anti-spyware anyway.

The purpose of email is communication. The purpose of text formatting is more effective communication. Bottom line: the advantages FAR outweigh the risks, if you take the other appropriate protection measures.

Following the privacy/security argument, people should use a text-based browser like Lynx. If you&#039;re willing to browse HTML, why not use HTML email?

Anyway, even if you prefer text-based HTML, you can still do the numbered lists, and create &quot;pseudo-headers&quot; using all-caps, although probably just for a word or phrase, not a whole sentence.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve heard a few security/privacy specialists recommend using plain-text email, and a few Unix/Linux geeks complain about it, but the fact of the matter is that most people use HTML email. It&#8217;s the default setting in Outlook, Outlook Express, GMail, etc.</p>
<p>Besides accommodating the text-based Unix/Linux fanatics, the main other arguments against HTML email are that images can be used as an email tracking mechanism and that links can be disguised to be something other than they actually are. In theory, malicious code could also be embedded in an HTML email.</p>
<p>In practice, though, Outlook, GMail, et al., all have various protection mechanisms against those things. Plus you should be running anti-virus/anti-spyware anyway.</p>
<p>The purpose of email is communication. The purpose of text formatting is more effective communication. Bottom line: the advantages FAR outweigh the risks, if you take the other appropriate protection measures.</p>
<p>Following the privacy/security argument, people should use a text-based browser like Lynx. If you&#8217;re willing to browse HTML, why not use HTML email?</p>
<p>Anyway, even if you prefer text-based HTML, you can still do the numbered lists, and create &#8220;pseudo-headers&#8221; using all-caps, although probably just for a word or phrase, not a whole sentence.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: owstarr</title>
		<link>http://www.gtdtimes.com/2008/09/28/theres-a-time-and-place-for-long-prose-email-is-rarely-it/comment-page-1/#comment-1037</link>
		<dc:creator>owstarr</dc:creator>
		<pubDate>Mon, 29 Sep 2008 14:11:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.gtdtimes.com/2008/09/28/theres-a-time-and-place-for-long-prose-email-is-rarely-it/#comment-1037</guid>
		<description>TesTeq,  perhaps you&#039;d care to expound upon why you don&#039;t recommend html email formatting for the uninitiated?

Editor</description>
		<content:encoded><![CDATA[<p>TesTeq,  perhaps you&#8217;d care to expound upon why you don&#8217;t recommend html email formatting for the uninitiated?</p>
<p>Editor</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TesTeq</title>
		<link>http://www.gtdtimes.com/2008/09/28/theres-a-time-and-place-for-long-prose-email-is-rarely-it/comment-page-1/#comment-1036</link>
		<dc:creator>TesTeq</dc:creator>
		<pubDate>Mon, 29 Sep 2008 07:52:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.gtdtimes.com/2008/09/28/theres-a-time-and-place-for-long-prose-email-is-rarely-it/#comment-1036</guid>
		<description>To bold the start of each item you have to use html e-mail format which I don&#039;t recommend.</description>
		<content:encoded><![CDATA[<p>To bold the start of each item you have to use html e-mail format which I don&#8217;t recommend.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://www.gtdtimes.com/2008/09/28/theres-a-time-and-place-for-long-prose-email-is-rarely-it/comment-page-1/#comment-1035</link>
		<dc:creator>James</dc:creator>
		<pubDate>Mon, 29 Sep 2008 07:22:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.gtdtimes.com/2008/09/28/theres-a-time-and-place-for-long-prose-email-is-rarely-it/#comment-1035</guid>
		<description>I have to agree very much with this advise. For those who&#039;re doubting it. I&#039;ve switched to the style of numbering each actionable item about a year or two ago, and it really makes a difference!

Oh, only difference for me is in the first line of each actionable item: I underscore instead of bold the first line, and I always give a &#039;shift-enter&#039;.

I guess the difference there isn&#039;t that big, as long as you make you seperate items stand out.</description>
		<content:encoded><![CDATA[<p>I have to agree very much with this advise. For those who&#8217;re doubting it. I&#8217;ve switched to the style of numbering each actionable item about a year or two ago, and it really makes a difference!</p>
<p>Oh, only difference for me is in the first line of each actionable item: I underscore instead of bold the first line, and I always give a &#8216;shift-enter&#8217;.</p>
<p>I guess the difference there isn&#8217;t that big, as long as you make you seperate items stand out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.gtdtimes.com/2008/09/28/theres-a-time-and-place-for-long-prose-email-is-rarely-it/comment-page-1/#comment-1031</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Sun, 28 Sep 2008 19:41:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.gtdtimes.com/2008/09/28/theres-a-time-and-place-for-long-prose-email-is-rarely-it/#comment-1031</guid>
		<description>That is some really good advice. Much better than a lot of &#039;email&#039; posts we often see.</description>
		<content:encoded><![CDATA[<p>That is some really good advice. Much better than a lot of &#8216;email&#8217; posts we often see.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

