<?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: Send: Make sure you&#039;re as nice in email as you are in person</title>
	<atom:link href="http://blog.penelopetrunk.com/2007/05/11/send-make-sure-youre-as-nice-in-email-as-you-are-in-person/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.penelopetrunk.com/2007/05/11/send-make-sure-youre-as-nice-in-email-as-you-are-in-person/</link>
	<description>Advice at the intersection of work and life</description>
	<lastBuildDate>Thu, 18 Mar 2010 20:16:01 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: 7 steps to becoming an e-mail pro</title>
		<link>http://blog.penelopetrunk.com/2007/05/11/send-make-sure-youre-as-nice-in-email-as-you-are-in-person/comment-page-1/#comment-184507</link>
		<dc:creator>7 steps to becoming an e-mail pro</dc:creator>
		<pubDate>Thu, 23 Apr 2009 12:05:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.penelopetrunk.com/2007/05/11/send-make-sure-youre-as-nice-in-email-as-you-are-in-person/#comment-184507</guid>
		<description>[...] Brazen Careerist: Make sure you’re as nice in e-mail as you are in person [...]</description>
		<content:encoded><![CDATA[<p>[...] Brazen Careerist: Make sure you’re as nice in e-mail as you are in person [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 7 steps to becoming an e-mail pro &#171; Lawyer&#8217;s Right Hand</title>
		<link>http://blog.penelopetrunk.com/2007/05/11/send-make-sure-youre-as-nice-in-email-as-you-are-in-person/comment-page-1/#comment-128000</link>
		<dc:creator>7 steps to becoming an e-mail pro &#171; Lawyer&#8217;s Right Hand</dc:creator>
		<pubDate>Fri, 21 Dec 2007 12:06:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.penelopetrunk.com/2007/05/11/send-make-sure-youre-as-nice-in-email-as-you-are-in-person/#comment-128000</guid>
		<description>[...] Brazen Careerist: Make sure you&#8217;re as nice in e-mail as you are in person [...]</description>
		<content:encoded><![CDATA[<p>[...] Brazen Careerist: Make sure you&#039;re as nice in e-mail as you are in person [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will Schwalbe</title>
		<link>http://blog.penelopetrunk.com/2007/05/11/send-make-sure-youre-as-nice-in-email-as-you-are-in-person/comment-page-1/#comment-70489</link>
		<dc:creator>Will Schwalbe</dc:creator>
		<pubDate>Sun, 13 May 2007 09:15:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.penelopetrunk.com/2007/05/11/send-make-sure-youre-as-nice-in-email-as-you-are-in-person/#comment-70489</guid>
		<description>Very interesting point on the &quot;cc&quot; -- many people complain about the volume of emails they get, but don&#039;t realize the extent they contribute to email overload. When you add up all the time that is wasted by people&#039;s over-cc&#039;ing, it&#039;s really staggering. And the &quot;bcc&quot; caution is always a good one.

The discussion around point five -- consistency -- makes me think that this is one of those areas where each of us needs to be more careful -- but, also, where each of us needs to cut others more slack. That is, it&#039;s good to be sensitive to our outgoing, but a bit more thick-skinned on the incoming. A really good reminder on the outgoing, Kerry, and incoming, Brian.

And that&#039;s very strong advice, Scott, fleshing out the idea of being specific. People love to focus on email &quot;disasters&quot; but most of the problems with email, I think, come from people just not being clear about what they want and when they want it.</description>
		<content:encoded><![CDATA[<p>Very interesting point on the &#034;cc&#034; &#8212; many people complain about the volume of emails they get, but don&#039;t realize the extent they contribute to email overload. When you add up all the time that is wasted by people&#039;s over-cc&#039;ing, it&#039;s really staggering. And the &#034;bcc&#034; caution is always a good one.</p>
<p>The discussion around point five &#8212; consistency &#8212; makes me think that this is one of those areas where each of us needs to be more careful &#8212; but, also, where each of us needs to cut others more slack. That is, it&#039;s good to be sensitive to our outgoing, but a bit more thick-skinned on the incoming. A really good reminder on the outgoing, Kerry, and incoming, Brian.</p>
<p>And that&#039;s very strong advice, Scott, fleshing out the idea of being specific. People love to focus on email &#034;disasters&#034; but most of the problems with email, I think, come from people just not being clear about what they want and when they want it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kerry Dexter</title>
		<link>http://blog.penelopetrunk.com/2007/05/11/send-make-sure-youre-as-nice-in-email-as-you-are-in-person/comment-page-1/#comment-69740</link>
		<dc:creator>Kerry Dexter</dc:creator>
		<pubDate>Fri, 11 May 2007 18:54:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.penelopetrunk.com/2007/05/11/send-make-sure-youre-as-nice-in-email-as-you-are-in-person/#comment-69740</guid>
		<description>Point number 5 especially is equally important for independent professionals to consider, on both sides of the sending and receiving equation.</description>
		<content:encoded><![CDATA[<p>Point number 5 especially is equally important for independent professionals to consider, on both sides of the sending and receiving equation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scot Herrick</title>
		<link>http://blog.penelopetrunk.com/2007/05/11/send-make-sure-youre-as-nice-in-email-as-you-are-in-person/comment-page-1/#comment-69721</link>
		<dc:creator>Scot Herrick</dc:creator>
		<pubDate>Fri, 11 May 2007 18:00:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.penelopetrunk.com/2007/05/11/send-make-sure-youre-as-nice-in-email-as-you-are-in-person/#comment-69721</guid>
		<description>Since a tremendous amount of delegation and task assignment is done via e-mail, I would add something more than just &quot;being specific.&quot; 

That is, right at the top of the e-mail, place your task assignment, what the successful outcome of the task looks like, due date, with the person assigned to complete the task.

One of the most difficult things for a knowledge worker is figuring out if there is something THEY need to do based upon receiving the e-mail. This is completely understandable when one receives many e-mails a day and half of them have ten other e-mails buried underneath the top one.

Then, once they figure out there is something that needs to be done, they have to figure out what the successful outcome is of what they are doing and when it would need to be completed.

Let&#039;s do that up front and leave the rest of the e-mail as &quot;context&quot; filler for what the actual task is that needs to be done.

Much better than leaving someone to figure out what to do with a top line from a manager saying &quot;fix this!&quot; and having nothing but 100 people copied and 40 e-mail messages below it to try and determine what to fix.

And we all know that happens, right?</description>
		<content:encoded><![CDATA[<p>Since a tremendous amount of delegation and task assignment is done via e-mail, I would add something more than just &#034;being specific.&#034; </p>
<p>That is, right at the top of the e-mail, place your task assignment, what the successful outcome of the task looks like, due date, with the person assigned to complete the task.</p>
<p>One of the most difficult things for a knowledge worker is figuring out if there is something THEY need to do based upon receiving the e-mail. This is completely understandable when one receives many e-mails a day and half of them have ten other e-mails buried underneath the top one.</p>
<p>Then, once they figure out there is something that needs to be done, they have to figure out what the successful outcome is of what they are doing and when it would need to be completed.</p>
<p>Let&#039;s do that up front and leave the rest of the e-mail as &#034;context&#034; filler for what the actual task is that needs to be done.</p>
<p>Much better than leaving someone to figure out what to do with a top line from a manager saying &#034;fix this!&#034; and having nothing but 100 people copied and 40 e-mail messages below it to try and determine what to fix.</p>
<p>And we all know that happens, right?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Duane</title>
		<link>http://blog.penelopetrunk.com/2007/05/11/send-make-sure-youre-as-nice-in-email-as-you-are-in-person/comment-page-1/#comment-69687</link>
		<dc:creator>Duane</dc:creator>
		<pubDate>Fri, 11 May 2007 16:20:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.penelopetrunk.com/2007/05/11/send-make-sure-youre-as-nice-in-email-as-you-are-in-person/#comment-69687</guid>
		<description>Go especially easy on the &quot;bcc&quot; (blind cc).  It&#039;ll get you in trouble more often than not.  You&#039;re basically saying &quot;I want to hide the fact that B has seen what I said to A&quot;, and it&#039;s the rough equivalent of denying that people are in the room while you&#039;re on speaker phone.

I had that happen once where I was sent something by my boss, then replied to all with my input, and then I got a chat message from him saying &quot;I bcc&#039;d you on that, so don&#039;t reply.&quot;  Too late!

Duane
http://commutesmarter.blogspot.com</description>
		<content:encoded><![CDATA[<p>Go especially easy on the &#034;bcc&#034; (blind cc).  It&#039;ll get you in trouble more often than not.  You&#039;re basically saying &#034;I want to hide the fact that B has seen what I said to A&#034;, and it&#039;s the rough equivalent of denying that people are in the room while you&#039;re on speaker phone.</p>
<p>I had that happen once where I was sent something by my boss, then replied to all with my input, and then I got a chat message from him saying &#034;I bcc&#039;d you on that, so don&#039;t reply.&#034;  Too late!</p>
<p>Duane<br />
<a href="http://commutesmarter.blogspot.com" rel="nofollow">http://commutesmarter.blogspot.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Johnson</title>
		<link>http://blog.penelopetrunk.com/2007/05/11/send-make-sure-youre-as-nice-in-email-as-you-are-in-person/comment-page-1/#comment-69675</link>
		<dc:creator>Brian Johnson</dc:creator>
		<pubDate>Fri, 11 May 2007 15:25:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.penelopetrunk.com/2007/05/11/send-make-sure-youre-as-nice-in-email-as-you-are-in-person/#comment-69675</guid>
		<description>On the flip side of point #5, as a manager I&#039;ve found that it&#039;s important to remember that often times your employees may NOT be taking this into consideration, or they simply may not be strong writers.  Before I read too much into an email from an employee with an unexpected tone, I&#039;ll first consider the general strength of their usual writing skills. Then If I still suspect something is amiss, I&#039;ll follow-up with a phone call rather than email to get the non-verbal pieces of the puzzle.  I&#039;ve learned the hard way not to jump to conclusions about notes from my employees whose writing skills may not be why they were hired for their position.</description>
		<content:encoded><![CDATA[<p>On the flip side of point #5, as a manager I&#039;ve found that it&#039;s important to remember that often times your employees may NOT be taking this into consideration, or they simply may not be strong writers.  Before I read too much into an email from an employee with an unexpected tone, I&#039;ll first consider the general strength of their usual writing skills. Then If I still suspect something is amiss, I&#039;ll follow-up with a phone call rather than email to get the non-verbal pieces of the puzzle.  I&#039;ve learned the hard way not to jump to conclusions about notes from my employees whose writing skills may not be why they were hired for their position.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg</title>
		<link>http://blog.penelopetrunk.com/2007/05/11/send-make-sure-youre-as-nice-in-email-as-you-are-in-person/comment-page-1/#comment-69658</link>
		<dc:creator>Greg</dc:creator>
		<pubDate>Fri, 11 May 2007 15:04:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.penelopetrunk.com/2007/05/11/send-make-sure-youre-as-nice-in-email-as-you-are-in-person/#comment-69658</guid>
		<description>One more:
Go easy on the CCs, especially if there is a potential problem or negative.

I work in IT, and occasionally I will get “Explain this unresolved issue!” email from a site manager or low-level executive, CC’d to my entire chain (CIO down) and their entire chain (Division President down),  usually 6 or more executives. In most cases there is either an acceptable explanation or I can resolve it quickly. But then I spend two hours calling, dropping in on, and emailing everyone that the event was a non-crisis. (the one plus is I get to tell my side of the story, which end with “Gosh, if they just emailed or called me direct, I would not have needed to waste you’re your time…)</description>
		<content:encoded><![CDATA[<p>One more:<br />
Go easy on the CCs, especially if there is a potential problem or negative.</p>
<p>I work in IT, and occasionally I will get “Explain this unresolved issue!” email from a site manager or low-level executive, CC’d to my entire chain (CIO down) and their entire chain (Division President down),  usually 6 or more executives. In most cases there is either an acceptable explanation or I can resolve it quickly. But then I spend two hours calling, dropping in on, and emailing everyone that the event was a non-crisis. (the one plus is I get to tell my side of the story, which end with “Gosh, if they just emailed or called me direct, I would not have needed to waste you’re your time…)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
