<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Lester, Susan M.J.</title>	<link>http://tc.eserver.org/authors/Lester,_Susan_M.J.</link>
	<description>A bibliography of works by Lester, Susan M.J. in the field of technical communication.</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>Lester, Susan M.J.</title>
		<link>http://tc.eserver.org/dir/Lester,_Susan_M.J.</link>
	</image>
	<item>
		<title>Using a Survey to Help Plan and Develop Your Document</title>
		<link>http://tc.eserver.org/20132.html</link>
		<guid>http://tc.eserver.org/20132.html</guid>
		<description>Surveys can be valuable tools for developing your document. We used our survey to answer many of our&#xD;user and task analysis questions before planning&#xD;content for different service manuals. When creating&#xD;and using a survey, identify what information you need&#xD;to know about your users, consider your options for&#xD;mailing the surveys, plan a smooth processor&#xD;gathering, tallying, and analyzing the data, and then&#xD;remember to report back to your respondents.&#xD;Ultimately, your findings can be incorporated into a&#xD;recommendation report for your clients, as well as&#xD;help you plan the content and layout for your&#xD;document.</description>
	</item>
	<item>
		<title>Applying Minimalist Principles, Strategies, and Techniques</title>
		<link>http://tc.eserver.org/19839.html</link>
		<guid>http://tc.eserver.org/19839.html</guid>
		<description>People use documentation differently from what we might expect. They don’t like to read; instead they jump to a&#xD;task with prior knowledge, and sometimes don’t realize&#xD;they’ve made an error. Understanding how users learn&#xD;and applying John Carroll’s minimalist principles will&#xD;help provide solutions to this problem.&#xD;Documentation that has been successfully planned and&#xD;designed for minimalism may take longer to create than&#xD;other manuals, but reaps the benefits of making users&#xD;more productive and happy, while reducing support calls,&#xD;maintenance, translation, and publishing costs. The key&#xD;factors to a successful minimalist approach (or any good&#xD;documentation design) are a keen understanding of your&#xD;users, prototypes designed to match tasks relevant to&#xD;users, and iterative testing to improve each draft.</description>
	</item>
	<item>
		<title>Conducting Usability Tests to Upgrade Your Web Sites</title>
		<link>http://tc.eserver.org/13685.html</link>
		<guid>http://tc.eserver.org/13685.html</guid>
		<description>Usability testing can be planned and executed at various levels of complexity to enhance your Web site throughout stages of development. Include usability testing in the&#xD;front-end planning and set Web site usability goals. Test&#xD;early prototypes and then test again to quantify&#xD;improvements. Assemble a team to plan the testing even if&#xD;it is just two people. If you follow a planning and testing&#xD;checklist, you should be rewarded with valuable data to&#xD;analyze and upgrade your Web site.&#xD;The process and outcome can enhance your company¶s&#xD;reputation or improve your credibility as an information&#xD;designer or developer.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Lester,_Susan_M.J..xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>