<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Civilisation will come to an end because no one will understand what anybody else is saying</title><link>http://blogs.technet.com/jamesone/archive/2006/03/28/423362.aspx</link><description>In yesterday's post I said "I’ve got an interest in how we communicate – and how sometimes we say a lot without getting a message across" . Recently I was asked to review someone else's document: it was full of jargon, which I didn't think the target</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>How not to be read...</title><link>http://blogs.technet.com/jamesone/archive/2006/03/28/423362.aspx#1574982</link><pubDate>Sat, 21 Jul 2007 18:39:30 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:1574982</guid><dc:creator>James O'Neill's blog </dc:creator><description>&lt;p&gt;Eileen asks &amp;quot; So how do I get my team to read my emails ? &amp;quot; Actually, she overlooks something very simple&lt;/p&gt;
</description></item></channel></rss>