<?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: Follow up and document!</title>
	<atom:link href="http://www.semi-blog.com/2010/03/follow-up-and-document/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.semi-blog.com/2010/03/follow-up-and-document/</link>
	<description>From Full Time to Me Time</description>
	<lastBuildDate>Mon, 30 Aug 2010 02:46:30 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: seb</title>
		<link>http://www.semi-blog.com/2010/03/follow-up-and-document/comment-page-1/#comment-301</link>
		<dc:creator>seb</dc:creator>
		<pubDate>Sat, 13 Mar 2010 00:31:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.semi-blog.com/?p=457#comment-301</guid>
		<description>That&#039;s some awesome advice there and you&#039;re absolutely correct - writing for your audience is crucial for your document to be useful.  I did try to tease that out, but you&#039;ve hit the nail on the head.</description>
		<content:encoded><![CDATA[<p>That&#8217;s some awesome advice there and you&#8217;re absolutely correct &#8211; writing for your audience is crucial for your document to be useful.  I did try to tease that out, but you&#8217;ve hit the nail on the head.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fev10</title>
		<link>http://www.semi-blog.com/2010/03/follow-up-and-document/comment-page-1/#comment-284</link>
		<dc:creator>fev10</dc:creator>
		<pubDate>Wed, 10 Mar 2010 19:45:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.semi-blog.com/?p=457#comment-284</guid>
		<description>It can be quite frustrating drafting a PAR! 

As the veteran of many, the biggest bit of advice I can offer is know who the intended audience is, and write to it, especially if you&#039;re not the end user of the document. 

Information or data that you think is important from your own perspective, may easily be flicked away with a stroke of the red pen (followed by the word &#039;resubmit&#039;). 

If writing a PAR, or indeed any document, for someone else, it&#039;s vital to get inside their head, writing it as if they were doing it themselves. It&#039;s also a central tenet of managing &#039;up&#039;... you hit on a lot of good points previously under &#039;Influencing Others&#039;.</description>
		<content:encoded><![CDATA[<p>It can be quite frustrating drafting a PAR! </p>
<p>As the veteran of many, the biggest bit of advice I can offer is know who the intended audience is, and write to it, especially if you&#8217;re not the end user of the document. </p>
<p>Information or data that you think is important from your own perspective, may easily be flicked away with a stroke of the red pen (followed by the word &#8216;resubmit&#8217;). </p>
<p>If writing a PAR, or indeed any document, for someone else, it&#8217;s vital to get inside their head, writing it as if they were doing it themselves. It&#8217;s also a central tenet of managing &#8216;up&#8217;&#8230; you hit on a lot of good points previously under &#8216;Influencing Others&#8217;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

