<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Jarrett, Caroline</title>	<link>http://tc.eserver.org/authors/Jarrett,_Caroline</link>
	<description>A bibliography of works by Jarrett, Caroline 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>Jarrett, Caroline</title>
		<link>http://tc.eserver.org/dir/Jarrett,_Caroline</link>
	</image>
	<item>
		<title>Writing Questions That Are Easy to Answer</title>
		<link>http://tc.eserver.org/34508.html</link>
		<guid>http://tc.eserver.org/34508.html</guid>
		<description>Have you ever found it difficult to fill out a seemingly simple form? Jarrett explains how to create questions that are easy to understand and accessible by all, focusing on details, the difference between prompts and fully formed questions, questions that need more explanation, and other aspects.</description>
	</item>
	<item>
		<title>How to Write Good FAQs</title>
		<link>http://tc.eserver.org/33337.html</link>
		<guid>http://tc.eserver.org/33337.html</guid>
		<description>FAQs don’t have that great a reputation, but recently, I’ve been working on FAQs for a client. Their computer help desk was annoyed about answering the same things again and again. Why not divert potential callers to a FAQ instead?</description>
	</item>
	<item>
		<title>Problems and Joys of Reading Research Papers for Practitioner Purposes</title>
		<link>http://tc.eserver.org/30437.html</link>
		<guid>http://tc.eserver.org/30437.html</guid>
		<description>Discusses reasons that practitioners read research papers and the obstacles that they face when reading research papers. Jarrett provides several examples and suggestions for improving the accessibility of research papers for practitioners. Her suggestions include writing clear titles, ensuring that the abstract states the study population and limitations of the study, and ensuring that the conclusions are written clearly. She also discusses her criteria for determining whether or not a research paper is relevant to her work.</description>
	</item>
	<item>
		<title>Usability Testing Then, Now and Tomorrow</title>
		<link>http://tc.eserver.org/29702.html</link>
		<guid>http://tc.eserver.org/29702.html</guid>
		<description>What is current practice in usability testing? How has it changed? What is essential for a good test and what is optional? We compare typical usability testing practice in the past (10+ years ago) with what we find is typical today. Then we look forward to predict what may happen in the future. We predict trends towards testing as a purchasable commodity, more remote testing, as technology makes it easier to ‘observe’ users over the Internet and more ‘mass market’ testing as businesses like Amazon try out their design ideas by micro-launching variants of their web site to see which one plays best with their customers.</description>
	</item>
	<item>
		<title>Caroline Jarrett on User Interface Design</title>
		<link>http://tc.eserver.org/28784.html</link>
		<guid>http://tc.eserver.org/28784.html</guid>
		<description>Jarrett is one of the authors of User Interface Design and Evaluation, a beginning text for technical communicators moving into user interface design. Jarrett says this book is a perfect start for users looking to add usability basics to their toolbox. She also talks about forms, and how the best forms are ones you barely notice.</description>
	</item>
	<item>
		<title>&amp;#35774;&amp;#35745;&amp;#21487;&amp;#29992;&amp;#30340;&amp;#34920;&amp;#21333;&amp;#65306;&amp;#34920;&amp;#21333;&amp;#30340;&amp;#19977;&amp;#23618;&amp;#27169;&amp;#22411;</title>
		<link>http://tc.eserver.org/26956.html</link>
		<guid>http://tc.eserver.org/26956.html</guid>
		<description>&amp;#22312;‘&amp;#19977;&amp;#23618;&amp;#27169;&amp;#22411;’&amp;#20013;&amp;#65292;&amp;#19968;&amp;#20010;&amp;#34920;&amp;#21333;&amp;#26377;&amp;#19977;&amp;#31181;&amp;#23646;&amp;#24615;&amp;#65306;&amp;#24863;&amp;#30693;&amp;#65288;&amp;#24067;&amp;#23616;&amp;#65289;&amp;#12289;&amp;#23545;&amp;#35805;&amp;#65288;&amp;#38382;&amp;#39064;&amp;#21644;&amp;#22238;&amp;#31572;&amp;#65289;&amp;#12289;&amp;#21644;&amp;#20851;&amp;#31995;&amp;#65288;&amp;#20219;&amp;#21153;&amp;#30340;&amp;#32467;&amp;#26500;&amp;#65289;&amp;#12290;</description>
	</item>
	<item>
		<title>Better Reports: How to Communicate the Results of Usability Testing</title>
		<link>http://tc.eserver.org/26537.html</link>
		<guid>http://tc.eserver.org/26537.html</guid>
		<description>You&apos;ve spent several days setting up a usability test, recruiting the participants and running it. Then you&apos;ve pored over the data. What next? If you are doing usability testing as part of user-centred design within a business setting, then there are many ways that you can communicate the results. This paper looks at reports and then considers presentation and observation as alternatives to reports.</description>
	</item>
	<item>
		<title>Designing Usable Forms: The Three-Layer Model of the Form</title>
		<link>http://tc.eserver.org/26396.html</link>
		<guid>http://tc.eserver.org/26396.html</guid>
		<description>Why do people say &apos;I’m not good with forms&apos; or &apos;I don’t like forms&apos; when a form is only a piece of paper, or a screen, with some printing on it? There must be something special about forms that inspires these comments.</description>
	</item>
	<item>
		<title>Editing That Works</title>
		<link>http://tc.eserver.org/26119.html</link>
		<guid>http://tc.eserver.org/26119.html</guid>
		<description>Collection of principles that can also form a process for editing web content to make it usable.</description>
	</item>
	<item>
		<title>Hooray, I&apos;m Doing the Forms!</title>
		<link>http://tc.eserver.org/24872.html</link>
		<guid>http://tc.eserver.org/24872.html</guid>
		<description>Everyone hates forms--users hate filling them out, and writers hate creating them. But forms offer writers a unique opportunity for rewarding work. Jarrett suggests ways to improve forms--and, possibly, users&apos; lives.</description>
	</item>
	<item>
		<title>Sneak Preview of the Usability and Information Design Stem at the 51st Annual STC Conference</title>
		<link>http://tc.eserver.org/23857.html</link>
		<guid>http://tc.eserver.org/23857.html</guid>
		<description>Here is a preview of the Usability and Information Design (UID) stem of the 2004 STC International Conference. You can also find the full stem in a spreadsheet that you can download (Excel format).</description>
	</item>
	<item>
		<title>Usability Testing: Don&apos;t Let the Myths Put You Off</title>
		<link>http://tc.eserver.org/21030.html</link>
		<guid>http://tc.eserver.org/21030.html</guid>
		<description>Jarrett dispels several myths about usability testing that may dissuade technical communicators from applying valuable usability techniques.</description>
	</item>
	<item>
		<title>Designing Usable Forms: The Three-Layer Model of the Form</title>
		<link>http://tc.eserver.org/19850.html</link>
		<guid>http://tc.eserver.org/19850.html</guid>
		<description>Why do people say &apos;I’m not good with forms&apos; or &apos;I don’t&#xD;like forms&apos; when a form is only a piece of paper, or a&#xD;screen, with some printing on it? There must be&#xD;something special about forms that inspires these&#xD;comments.&#xD;The &apos;three-layer model” considers forms from three&#xD;points of view: perceptual (layout), conversational&#xD;(questions and answers) and relationship (the structure of&#xD;the task).&#xD;Analysing a form using the three layers helps to un-pick&#xD;its problems, and to suggest ways of making it more&#xD;usable.</description>
	</item>
	<item>
		<title>We&apos;ll Never Get This Past Legal</title>
		<link>http://tc.eserver.org/19602.html</link>
		<guid>http://tc.eserver.org/19602.html</guid>
		<description>Looks at usable writing, and convincing the legal department to adopt the tenets of clear writing.</description>
	</item>
	<item>
		<title>Usability Means User-Centred Design</title>
		<link>http://tc.eserver.org/13195.html</link>
		<guid>http://tc.eserver.org/13195.html</guid>
		<description>To create usable products you must be user-centred throughout your development process: from setting goals to installation. Two case studies illustrate why this is important. User-centred design is about actively involving users and understanding their requirements. It is necessarily iterative and multi-disciplinary. User-centred design requires commitment from your organisation or your client and yourself. Choosing your activities to match the level of acceptance of usability in your audience will help to create that commitment.</description>
	</item>
	<item>
		<title>Market Research and Usability</title>
		<link>http://tc.eserver.org/11782.html</link>
		<guid>http://tc.eserver.org/11782.html</guid>
		<description>I am a usability consultant and I believe, and find in practice, that usability evaluation is the best way to find out whether a document works for its users. However, I have frequently been in a position where my clients have decided to &apos;do market research&apos; because they believe that they have a problem document and they think &apos;we’ll ask our customers about it.&apos; Usability evaluation is one type of market research but it is not the most frequently used technique. In this article, I introduce some of the more common techniques and what you might expect to learn about a document by using them. I’ll use the example of a car owner’s manual–the small book that comes with a car, and explains things like how to change the oil and what the switches mean.</description>
	</item>
	<item>
		<title>Why Users Don&apos;t Complain About Unusable Forms</title>
		<link>http://tc.eserver.org/11753.html</link>
		<guid>http://tc.eserver.org/11753.html</guid>
		<description>The email lists have been abuzz with discussions of the usability issues in the Florida ballot. A common question asked was why a ballot design with so many obvious ways of failing its users attracted no attention before the recent U.S. Presidential election.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Jarrett,_Caroline.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>