TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: White Papers From:"Dick Margulis " <margulis -at- mail -dot- fiam -dot- net> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 15 Feb 2002 13:43:22 -0500
This is a question that has been asked and answered many times before, and if you check the archives you will find numerous links to good resources. But I'm too lazy to do that myself, so I'll just wing it:
A white paper is an analytic discussion of a topic. It might discuss an industry trend, or the state of a technological art, or a new approach to an old problem, for example. Think in terms of an article that might be published in a professional or trade journal that seeks to inform the reader.
Now, in practice, at least in commercial practice, white papers tend be ghostwritten (by you, of course) and carry the byline of a CEO or CTO of a company that has an economic interest in the industry or technology in question; and the white paper tends to have a decided slant in favor of adopting that company's solution or product.
<cynical aside>The goal is to persuade the reader that your position is correct, while feigning a detached neutrality.</cynical aside>
Typical sections include introduction, background, [body], and conclusion, where the body may consist of one or more sections, depending on what it is you are trying to convey and how long the paper is.
Edwyn Kumar wrote:
>What classifies a document as a White Paper as opposed to a standard manual
>or reference doc?
>Are there any specific points that need to be in a White Paper, and if so,
Did you know you can get RoboHelp certified?
To learn how, visit http://www.ehelp.com/techwr. Be sure to also check out
our special pricing offers and promotions for RoboHelp 2002.
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.