<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Writing&gt;Rhetoric&gt;White Papers</title>	<link>http://tc.eserver.org/dir/Articles/Writing/Rhetoric/White-Papers</link>
	<description>A listing of the most recently indexed works about Articles and Writing and Rhetoric and White Papers in the field of technical communication (and technical writing).</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Articles&gt;Writing&gt;Rhetoric&gt;White Papers</title>
		<link>http://tc.eserver.org/dir/Articles/Writing/Rhetoric/White-Papers</link>
	</image>
	<item>
		<title>The Abstract Trap: Why Abstracts Are Bad for Persuasive White Papers</title>
		<link>http://tc.eserver.org/27779.html</link>
		<guid>http://tc.eserver.org/27779.html</guid>
		<description>Abstracts, also known as executive summaries, are bad. As a matter of fact, they are really bad, and I stand nearly alone in my opinion. Abstracts are those summaries that typically stand in front of the core content of a white paper. They tend to include the key points about the white paper.</description>
	</item>
	<item>
		<title>Eleven Tips on Terrific Titles</title>
		<link>http://tc.eserver.org/27789.html</link>
		<guid>http://tc.eserver.org/27789.html</guid>
		<description>Honestly, which white paper would YOU sooner read: &apos;Implications of Business Intelligence Methodologies on Operational Efficiencies: A Retrospective Study&apos; or &apos;Six Things You Must Know about Data Warehousing&apos;? This article offers eleven tips on putting together compelling titles for white papers.</description>
	</item>
	<item>
		<title>Getting Off the Starting Block: Practical Tips to Starting a White Paper</title>
		<link>http://tc.eserver.org/27790.html</link>
		<guid>http://tc.eserver.org/27790.html</guid>
		<description>Why are white papers so hard to write? Simply put, they require effort. Effort makes us sweat. Just the thought of working hard causes some people&apos;s blood to percolate.</description>
	</item>
	<item>
		<title>Seven Steps to Writing White Papers More Efficiently</title>
		<link>http://tc.eserver.org/27784.html</link>
		<guid>http://tc.eserver.org/27784.html</guid>
		<description>Read about a seven-step process used when writing write white papers and other complex documents.</description>
	</item>
	<item>
		<title>The Top Five Writing Mistakes in White Papers</title>
		<link>http://tc.eserver.org/27776.html</link>
		<guid>http://tc.eserver.org/27776.html</guid>
		<description>A compelling topic and an attractive design will initially draw readers to a white paper. But those readers may lose interest if the paper contains any of five common writing mistakes.</description>
	</item>
	<item>
		<title>Why a Good Title Makes a White Paper</title>
		<link>http://tc.eserver.org/27775.html</link>
		<guid>http://tc.eserver.org/27775.html</guid>
		<description>The title is your white paper&apos;s absolute first impression. In it rests success or failure for the words that lie beyond, waiting for a reader. If the title does not encourage someone to read further, the ink that coats your white paper will never be seen.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Writing/Rhetoric/White-Papers.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>