<?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: 10 Days to a Better White Paper &#8211; Day 8: Writing for both the Quick Read and Close Read</title>
	<atom:link href="http://www.whitepapersolution.com/10-days-to-a-better-white-paper-day-8-writing-for-both-the-quick-read-and-close-read/feed" rel="self" type="application/rss+xml" />
	<link>http://www.whitepapersolution.com/10-days-to-a-better-white-paper-day-8-writing-for-both-the-quick-read-and-close-read</link>
	<description>Providing White Papers, Information Marketing and Powerful Copywriting</description>
	<lastBuildDate>Fri, 30 Jul 2010 04:42:50 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jim Lodico</title>
		<link>http://www.whitepapersolution.com/10-days-to-a-better-white-paper-day-8-writing-for-both-the-quick-read-and-close-read/comment-page-1#comment-121</link>
		<dc:creator>Jim Lodico</dc:creator>
		<pubDate>Thu, 02 Jul 2009 12:18:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.whitepapersolution.com/?p=255#comment-121</guid>
		<description>I think the summary or abstract partially depends on the paper and how it will be used. Considerations such as target audience, distribution methods can all come into play. 

At this point, I prefer to explain the pros and cons to the client and work together to determine a solution that works best for their specific situation.

They key thing is that if you do use an executive summary/abstract, it needs to be direct, to the point and most important of all, engaging. The last thing you want the reader to do is read the summary and stop.</description>
		<content:encoded><![CDATA[<p>I think the summary or abstract partially depends on the paper and how it will be used. Considerations such as target audience, distribution methods can all come into play. </p>
<p>At this point, I prefer to explain the pros and cons to the client and work together to determine a solution that works best for their specific situation.</p>
<p>They key thing is that if you do use an executive summary/abstract, it needs to be direct, to the point and most important of all, engaging. The last thing you want the reader to do is read the summary and stop.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John White</title>
		<link>http://www.whitepapersolution.com/10-days-to-a-better-white-paper-day-8-writing-for-both-the-quick-read-and-close-read/comment-page-1#comment-120</link>
		<dc:creator>John White</dc:creator>
		<pubDate>Wed, 01 Jul 2009 21:31:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.whitepapersolution.com/?p=255#comment-120</guid>
		<description>I favor a Summary at the beginning of the paper, but I&#039;ve stopped calling it &quot;Executive Summary.&quot; Just seemed silly, the more I looked at it.</description>
		<content:encoded><![CDATA[<p>I favor a Summary at the beginning of the paper, but I&#8217;ve stopped calling it &#8220;Executive Summary.&#8221; Just seemed silly, the more I looked at it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
