<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Usability&gt;Audience Analysis</title>	<link>http://tc.eserver.org/dir/Articles/Usability/Audience-Analysis</link>
	<description>A listing of the most recently indexed works about Articles and Usability and Audience Analysis 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>Articles&gt;Usability&gt;Audience Analysis</title>
		<link>http://tc.eserver.org/dir/Articles/Usability/Audience-Analysis</link>
	</image>
	<item>
		<title>Twitter, Tweetdeck and Simplicity</title>
		<link>http://tc.eserver.org/33939.html</link>
		<guid>http://tc.eserver.org/33939.html</guid>
		<description>The usability of a website is relative to the audience that it was designed for. A website that is designed well for its primary audience will not necessarily provide a great user experience for everyone that tries to use it. It’s important to identify your target user if you’re going to make a site that works well for the right people.</description>
	</item>
	<item>
		<title>Audience Matters</title>
		<link>http://tc.eserver.org/31078.html</link>
		<guid>http://tc.eserver.org/31078.html</guid>
		<description>By incorporating usability techniques--more commonly used in product design--writers can better understand their audiences and the ways they use (or have problems using) the content. Read on for tips on how to incorporate usability techniques into your work.</description>
	</item>
	<item>
		<title>Some Stategies for Addressing the Changing Audience</title>
		<link>http://tc.eserver.org/30574.html</link>
		<guid>http://tc.eserver.org/30574.html</guid>
		<description>&apos;Know your user!&apos; is the first thing every aspiring technical communicator learns. Everyone agrees that understanding the technical skills and needs of your audience is essential to producing high quality technical documentation. However, knowing exactly who your audience is and what they need from documentation is no longer an easy task. The increase in international markets, multiculturalism in America, end the number of people using software products for the first time all mean that the audience you knew so well a short time ago may not be the same audience using your documentation today. As technical communicators, we can no longer assume that our users&apos; language and technical skills remain stable over a long period of time. How to assess and meet the needs of a changing audience is a challenge many technical communicators face today.</description>
	</item>
	<item>
		<title>Understanding the Customer&apos;s Business Context</title>
		<link>http://tc.eserver.org/30245.html</link>
		<guid>http://tc.eserver.org/30245.html</guid>
		<description>As an internal supplier of network and system management software, our organization faces significant challenges in assessing and enhancing the value of our products to customers. Traditionally, these types of products focus narrowly on meeting the technical needs of a single user constituency, without considering their impact on customers&apos; overall business. This paper describes an ongoing project to investigate how to increase the perceived and actual value of our products by considering customers&apos; business context. It describes how we got buy-in, what we learned about users and usability, and how we communicate our findings.</description>
	</item>
	<item>
		<title>Prescriptive Audience Analysis: Moving Beyond the Purely Descriptive</title>
		<link>http://tc.eserver.org/26125.html</link>
		<guid>http://tc.eserver.org/26125.html</guid>
		<description>Editing and writing both require an understanding of our audience, because without that knowledge, we can&apos;t shape our words to help them easily grasp difficult concepts. To understand our audience, we do what all writers and editors do, whether consciously or unconsciously: We create an image of our audience that guides our choice of words, images, and metaphors. This image is variously known as a &apos;stereotype&apos; (e.g., Schriver 1997) or a &apos;persona&apos; (e.g., Graham 2001). Keeping that image in mind as we work helps us satisfy the reader&apos;s needs, but if we&apos;re not careful, it can also cause us to waste valuable time collecting information that doesn&apos;t really help us communicate.</description>
	</item>
	<item>
		<title>User Research Abroad: Handle Logistics in Four Easy Steps</title>
		<link>http://tc.eserver.org/25706.html</link>
		<guid>http://tc.eserver.org/25706.html</guid>
		<description>In our industry, we are often asked to conduct non-directed interviews by telephone with audiences around the globe. This presents several logistical challenges.</description>
	</item>
	<item>
		<title>Uncovering True Motivation: The Whys and Wherefore</title>
		<link>http://tc.eserver.org/23868.html</link>
		<guid>http://tc.eserver.org/23868.html</guid>
		<description>As a designer of software systems, I believe that the child&apos;s spirit of &apos;why&apos; is something to retain and infuse  into our work when gathering requirements, interviewing users, and interviewing stakeholders.</description>
	</item>
	<item>
		<title>Audience Analysis: Looking Beyond the Superficial</title>
		<link>http://tc.eserver.org/19961.html</link>
		<guid>http://tc.eserver.org/19961.html</guid>
		<description>In performing an audience analysis, it’s easy to focus on simple, obvious issues such as the differences between men and women. In fact, men and women&#xD;have more similarities than differences when it comes&#xD;to most of the things that technical communicators&#xD;document. A discussion of some seemingly obvious&#xD;differences between men and women illustrates how&#xD;to look beyond superficial issues to find the truly&#xD;important differences.</description>
	</item>
	<item>
		<title>Cómo Leen Los Usuarios en la Web</title>
		<link>http://tc.eserver.org/18728.html</link>
		<guid>http://tc.eserver.org/18728.html</guid>
		<description>Los usuarios en la Web no leen, o por lo menos no lo hacen de la misma forma secuencial que cuando tienen entre manos un periódico, un libro, un artículo o un cómic. Los usuarios tienen necesidades y objetivos, metas que alcanzar, y saben que la forma de conseguir dichas metas no suele ser dedicando largos ratos a cada nodo web que visitan, leyendo de principio a fin sus contenidos y enlaces. El usuario, en una página, hará clic sobre el primer enlace que crea puede llevarle a lo que busca, necesita o pudiera interesar. Eso quiere decir que muchos de los contenidos y enlaces de ese nodo ni siquiera serán vistos por el usuario.</description>
	</item>
	<item>
		<title>How to Know Your Audience</title>
		<link>http://tc.eserver.org/14718.html</link>
		<guid>http://tc.eserver.org/14718.html</guid>
		<description>Lazzaro presents a method for conducting thorough user and audience analyses.</description>
	</item>
	<item>
		<title>Field Trials: Trials and Tribulations of a Field Visit</title>
		<link>http://tc.eserver.org/11822.html</link>
		<guid>http://tc.eserver.org/11822.html</guid>
		<description>I dutifully and eagerly prepared myself for the visit. I read books and STC articles on field visits and questionnaires. I was on a quest, and dangerously close to realizing a dream. At last, I would be able to define my audience, and gage the usability of the online help and hard copy manual. I would finally get the answers to my questions directly from a group of users. </description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Usability/Audience-Analysis.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>