<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Documentation&gt;User Centered Design&gt;Technical Writing</title>	<link>http://tc.eserver.org/dir/Articles/Documentation/User-Centered-Design/Technical-Writing</link>
	<description>A listing of the most recently indexed works about Articles and Documentation and User Centered Design and Technical Writing 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;Documentation&gt;User Centered Design&gt;Technical Writing</title>
		<link>http://tc.eserver.org/dir/Articles/Documentation/User-Centered-Design/Technical-Writing</link>
	</image>
	<item>
		<title>User Paradox with Not Reading User Manuals</title>
		<link>http://tc.eserver.org/34378.html</link>
		<guid>http://tc.eserver.org/34378.html</guid>
		<description>Users would save time by reading the manual, but instead they try to figure the application out themselves and then get lost/frustrated as they end up spending even more time getting up to speed with the application.</description>
	</item>
	<item>
		<title>Has Anyone Used Your Product</title>
		<link>http://tc.eserver.org/32824.html</link>
		<guid>http://tc.eserver.org/32824.html</guid>
		<description>Before you release a product,  have some people use it.  From these &quot;test users&quot; get solutions to problems, tips and knowledge that would help your real-life Users.  Put that information in your User Documentation, and on your product support website.</description>
	</item>
	<item>
		<title>Are We Giving Readers What They Want, in the Way They Want and Need It?  </title>
		<link>http://tc.eserver.org/31780.html</link>
		<guid>http://tc.eserver.org/31780.html</guid>
		<description>With all the talk about Web 2.0 and the attendant technologies, are readers actually being better served by documentation now than they were in the past?</description>
	</item>
	<item>
		<title>Getting to Expert</title>
		<link>http://tc.eserver.org/31748.html</link>
		<guid>http://tc.eserver.org/31748.html</guid>
		<description>The gaps in your documentation aren’t there because you haven’t consider a particular level of user; the gaps in your documentation are there because you haven’t considered how one level of user becomes another. How DO you get from Beginner to Expert?</description>
	</item>
	<item>
		<title>Technical Writing in Everyday Life: One User&apos;s Experience</title>
		<link>http://tc.eserver.org/23698.html</link>
		<guid>http://tc.eserver.org/23698.html</guid>
		<description>The experience of setting up a new home theater system also sharply reminded me of what it is like to look at something as a new user: staring at a bunch of knobs and holes for the first time, holding a tassel of wire in one hand and a manual in the other, and really just wanting the darn piece of ?%^%! to do what it&apos;s supposed to do.</description>
	</item>
	<item>
		<title>IBM User-Centered Design for the Documentation Designer</title>
		<link>http://tc.eserver.org/20552.html</link>
		<guid>http://tc.eserver.org/20552.html</guid>
		<description>The user-centered design of documentation is an aspect of product design that has often been under-emphasized.&#xD;Difficulties inherent in documentation design include&#xD;obtaining user, feedback to high-level design objectives;&#xD;extracting user. feedback specific to a product’s documentation.&#xD;rather than to the product as a whole; and&#xD;managing the various resource constraints inherent in&#xD;product development. IBM User-Centered Design&#xD;offers a solution to these difficulties by employing a set&#xD;of user feedback methodologies from which the documentation&#xD;designer, a member of a multidisciplinary&#xD;design team, extracts pertinent data to set design&#xD;objectives and follow through to low-level designs.</description>
	</item>
	<item>
		<title>Creating User-Friendly Documentation</title>
		<link>http://tc.eserver.org/19743.html</link>
		<guid>http://tc.eserver.org/19743.html</guid>
		<description>We often hear that users do not read documents. To lure readers into reading our documents, we must make documents user-friendly.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Documentation/User-Centered-Design/Technical-Writing.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>