<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Millman, Barry</title>	<link>http://tc.eserver.org/authors/Millman,_Barry</link>
	<description>A bibliography of works by Millman, Barry in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-10 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>Millman, Barry</title>
		<link>http://tc.eserver.org/dir/Millman,_Barry</link>
	</image>
	<item>
		<title>How Poor In-House User Documents Cost You Twice</title>
		<link>http://tc.eserver.org/35546.html</link>
		<guid>http://tc.eserver.org/35546.html</guid>
		<description>Many organizations produce in-house tools or modify commercially-available tools for their own use. These tools should get documented so they are of use to others in the organization. If this documentation is not created or is poorly written, it costs you twice.</description>
	</item>
	<item>
		<title>New Technical Writer: Use the Persona to Create the Most Useful Section of Your User Document</title>
		<link>http://tc.eserver.org/29998.html</link>
		<guid>http://tc.eserver.org/29998.html</guid>
		<description>A good User Document includes sections on how to set up, use, and care for the product. However, to create a great User Document, the technical writer should use the Persona, generated in the analysis of the User/Reader, to create the topics for the most useful section of the User Document. This article describes this procedure.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Millman,_Barry.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>