<?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>The Business &#38; Employment Law Blog &#187; Post</title>
	<atom:link href="http://reddingbusinessandemploymentlawblog.com/tag/post/feed/" rel="self" type="application/rss+xml" />
	<link>http://reddingbusinessandemploymentlawblog.com</link>
	<description>Northern California&#039;s Source for Business and Employment News</description>
	<lastBuildDate>Mon, 14 May 2012 18:18:12 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Top 10 email mistakes made by management</title>
		<link>http://reddingbusinessandemploymentlawblog.com/2010/02/top-10-email-mistakes-made-by-management/</link>
		<comments>http://reddingbusinessandemploymentlawblog.com/2010/02/top-10-email-mistakes-made-by-management/#comments</comments>
		<pubDate>Sat, 06 Feb 2010 02:37:40 +0000</pubDate>
		<dc:creator>Shawn McCammon</dc:creator>
				<category><![CDATA[Business Protection]]></category>
		<category><![CDATA[Business and Entrepreneur]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Email]]></category>
		<category><![CDATA[grammar]]></category>
		<category><![CDATA[Management]]></category>
		<category><![CDATA[Mistakes]]></category>
		<category><![CDATA[Post]]></category>
		<category><![CDATA[subject line]]></category>
		<category><![CDATA[Top 10]]></category>

		<guid isPermaLink="false">http://reddingbusinessandemploymentlawblog.com/?p=163</guid>
		<description><![CDATA[Top 10 email mistakes made by management]]></description>
			<content:encoded><![CDATA[<p style="text-align: justify;">I saw this guest post by Tim Flood (assistant professor of Management and Corporate Communications at the University of North Carolina&#8217;s Kenan-Flagler Business School ) posted at the Wall St. Journal regarding the 10 most common mistakes management makes in connection with emails, and I thought I would pass it along, enjoy!</p>
<p style="text-align: justify;">Many of us think we use email well. We don&#8217;t.</p>
<p style="text-align: justify;">Too many of us rush, causing confusion and requiring more time to clarify misunderstandings later. We miss chances to build relationships, motivate others, close deals and convey important information.</p>
<p style="text-align: justify;">Avoid the following ten mistakes.</p>
<p style="text-align: justify;"><strong>1. Using vague subject lines.</strong> &#8220;Meeting,&#8221; &#8220;Update,&#8221; or &#8220;Question&#8221; provide no value as subject lines.</p>
<p style="text-align: justify;">Maximize the subject line&#8217;s message. PDA users will get the message quickly; everyone will appreciate the clear summary. You can communicate plenty in a five to 10 word subject line: &#8220;Your Action Items and Minutes from Last Week&#8217;s Meeting&#8221; or &#8220;Sam: See You at 10:00 Tuesday with Report In-Hand?&#8221;</p>
<p style="text-align: justify;"><strong>2. Burying the news.</strong> Convey the important points first: put dates, deadlines and deliverables in the first one to three lines of the message (if not also in the subject line). PDA limitations, time pressures, cultural distinctions and value judgments keep many readers from reading further.</p>
<p style="text-align: justify;"><strong>3. Hiding Behind the &#8220;BCC&#8221; field.</strong> At best, the &#8216;blind copy&#8217; field is sneaky and risky. At worst, it&#8217;s deceitful or unethical. Plus, blind recipients sometimes hit &#8220;reply all,&#8221; revealing the deception. Instead, post the initial message and BCC no one. Then forward your sent message to others with a brief explanation.</p>
<p style="text-align: justify;"><strong>4. Failing to clean up the mess of earlier replies/forwards.</strong> Few readers will wade through strings of previous messages.</p>
<ul style="text-align: justify;">
<li>State your      position clearly, even if context follows below in the email string.      &#8220;Yes&#8221; helps less than &#8220;Yes, you can have the extra funding      to hire 5 temporary workers.&#8221;</li>
<li>Summarize      the discussion to date: &#8220;See below: R&amp;D is looking for more time      but Sales risks losing customers if we don&#8217;t act now.&#8221;</li>
<li>Force      focus when necessary: &#8220;Let&#8217;s focus on cost now and revisit the morale      and equity issues at our staff meeting next week.&#8221;</li>
</ul>
<ul style="text-align: justify;">
<li>Change      subject lines cautiously. Tighter, more relevant subject lines work best,      but even one letter&#8217;s difference upsets inbox sorting mechanisms.</li>
<li>Cut      extraneous or repetitive information.</li>
</ul>
<p style="text-align: justify;"><strong>5. Ignoring grammar and mechanics.</strong> PDAs have granted us certain sloppy flexibility, which means you&#8217;ll impress readers even more when you write precisely.</p>
<ul style="text-align: justify;">
<li>Follow      standard punctuation, capitalization and spelling rules.</li>
<li>Think      carefully about the tone different punctuation conveys. &#8220;Dear      Betty,&#8221; is standard, neutral; &#8220;Dear Betty:&#8221; is      professional, perhaps distant; &#8220;Dear Betty!&#8221; is personable,      perhaps excessively so; &#8220;Dear Betty.&#8221; prefaces bad news.</li>
<li>Avoid      over-stylizing with high-priority marks, disorienting color or complex      backgrounds.</li>
</ul>
<ul style="text-align: justify;">
<li>Avoid      all-caps and excessives (like &#8220;!!!!&#8221; or other strings of      punctuation).</li>
</ul>
<p style="text-align: justify;"><strong>6. Avoiding necessarily long emails.</strong> Longer messages sometimes work best; they can help avoid attachments&#8217; hassle and security fuss. Don&#8217;t fear long emails but outline your structure and motivate reading up top.</p>
<ul style="text-align: justify;">
<li>Provide a      &#8216;mapping statement&#8217; to allow readers to skim for key information:      &#8220;I&#8217;ve included information, below, on the background, costs,      implementation schedule and possible problems.&#8221;</li>
<li>Emphasize      the specific response you seek: &#8220;Please let me know, before Monday,      how this project will impact your team.&#8221;</li>
<li>Indicate      an attachment&#8217;s presence and value: &#8220;I&#8217;ve attached slides that I need      you to review before our meeting; those slides identify total costs and      break down the budget.</li>
</ul>
<p style="text-align: justify;"><strong>7. Mashing everything together into bulky, imposing, inaccessible paragraphs. </strong>Length does not discourage reading; bulk does.</p>
<ul style="text-align: justify;">
<li>Keep your      paragraphs short, ideally no more than three to five lines of type.</li>
<li>Open each      paragraph with a bottom-line sentence.</li>
<li>Use      section headings (in all-caps) to facilitate skimming.</li>
</ul>
<ul style="text-align: justify;">
<li>Include      blank lines between paragraphs and section headings.</li>
<li>Avoid italics,      boldface and other typeface changes which do not reliably carry across      email systems.</li>
</ul>
<p style="text-align: justify;"><strong>8. Neglecting the human beings at the other end.</strong> Email travels between actual people, even though we don&#8217;t see or hear each other directly.</p>
<ul style="text-align: justify;">
<li>Praise,      precisely. &#8220;Great job&#8221; takes little time and space but can work      wonders. Quickly wishing someone a good weekend, at the end of an email,      might perk someone up without cluttering your message.</li>
<li>Avoid      conveying blame or delivering negative feedback over email. Talk to the      person instead.</li>
<li>Avoid      sarcasm, caustic wit, off-color humor and potentially inappropriate      remarks —all of these elements tend to confuse, disorient or fall flat      over email.</li>
</ul>
<ul style="text-align: justify;">
<li>Consider      using emoticons and exclamations (&#8220;!&#8221; but also &#8220;ha,      ha&#8221; or &#8220;just kidding&#8221;) when they convey useful emotional      context.</li>
</ul>
<ul style="text-align: justify;">
<li>Adjust      your style to suit your audience. For people who don&#8217;t know you, a terse      style might seem rude; a wordy style might seem unfocused.</li>
</ul>
<p style="text-align: justify;"><strong>9. Thinking email works best.</strong> Email is not always the best way to communicate.</p>
<ul style="text-align: justify;">
<li>Need a      quick answer from someone nearby? Stop by for a visit.</li>
<li>Want a      reply to several unanswered emails? Pick up the phone.</li>
<li>Looking      for more gravitas? Mail a letter.</li>
</ul>
<ul style="text-align: justify;">
<li>Need to      explain a complex or sensitive situation? Arrange a meeting.</li>
</ul>
<p style="text-align: justify;"><strong>10. Forgetting that email lasts forever.</strong> Most of us read, send and discard emails at lightning speeds. But don&#8217;t forget that emails remain on a server somewhere as easy-to-forward proof of any error, offense or obfuscation we made.</p>
<p style="text-align: justify;">
<a href='http://reddingbusinessandemploymentlawblog.com/2010/02/top-10-email-mistakes-made-by-management/' class='retweet vert' startCount = '0'>Top 10 email mistakes made by management</a>]]></content:encoded>
			<wfw:commentRss>http://reddingbusinessandemploymentlawblog.com/2010/02/top-10-email-mistakes-made-by-management/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

