<?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>Strategically Eloquent &#187; executive communication</title>
	<atom:link href="http://www.eloquor.com/blog/index.php/tag/executive-communication/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.eloquor.com/blog</link>
	<description>Internal Communication et al.</description>
	<lastBuildDate>Thu, 26 Jan 2012 20:23:23 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Blogging is not for every leader</title>
		<link>http://www.eloquor.com/blog/index.php/2009/01/05/blogging-leader/</link>
		<comments>http://www.eloquor.com/blog/index.php/2009/01/05/blogging-leader/#comments</comments>
		<pubDate>Mon, 05 Jan 2009 19:42:22 +0000</pubDate>
		<dc:creator>swilson</dc:creator>
				<category><![CDATA[Intranet and Portal]]></category>
		<category><![CDATA[Leader communication]]></category>
		<category><![CDATA[social technology]]></category>
		<category><![CDATA[blog]]></category>
		<category><![CDATA[employee]]></category>
		<category><![CDATA[executive communication]]></category>
		<category><![CDATA[internal communication]]></category>

		<guid isPermaLink="false">http://www.eloquor.com/blog/?p=32</guid>
		<description><![CDATA[An article posted today on www.Ragan.com almost challenges communicators to get their CEOs to blog. The information about Bill Marriott is charming – his style is very conducive to blogging – and I especially like the note that his posts are edited by the communication team. A necessity with some executive bloggers. What I think [...]]]></description>
		<wfw:commentRss>http://www.eloquor.com/blog/index.php/2009/01/05/blogging-leader/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Be succinct for success</title>
		<link>http://www.eloquor.com/blog/index.php/2008/12/15/be-succinct-for-success/</link>
		<comments>http://www.eloquor.com/blog/index.php/2008/12/15/be-succinct-for-success/#comments</comments>
		<pubDate>Mon, 15 Dec 2008 19:39:27 +0000</pubDate>
		<dc:creator>swilson</dc:creator>
				<category><![CDATA[Leader communication]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[Writing]]></category>
		<category><![CDATA[consultant]]></category>
		<category><![CDATA[executive communication]]></category>
		<category><![CDATA[long]]></category>
		<category><![CDATA[succinct]]></category>

		<guid isPermaLink="false">http://www.eloquor.com/blog/?p=30</guid>
		<description><![CDATA[Why are we compelled to write too much? I am sometimes accused of writing too little – assuming my readers know what I am thinking and omitting valuable insights. But the vast majority out there write too much. I had a blog entry submitted from a client for review recently – it was 1,500 words [...]]]></description>
		<wfw:commentRss>http://www.eloquor.com/blog/index.php/2008/12/15/be-succinct-for-success/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

