<?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;Workplace</title>	<link>http://tc.eserver.org/dir/Articles/Usability/Workplace</link>
	<description>A listing of the most recently indexed works about Articles and Usability and Workplace 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;Workplace</title>
		<link>http://tc.eserver.org/dir/Articles/Usability/Workplace</link>
	</image>
	<item>
		<title>You Want to Do What? Convincing Your Management to Support Usability Studies</title>
		<link>http://tc.eserver.org/30623.html</link>
		<guid>http://tc.eserver.org/30623.html</guid>
		<description>It&apos;s a classic chicken-and-egg struggle. Many information developers wait for management go-ahead before conducting usability studies. Management, on the otherhand, is sometimes reluctant to support usability work.</description>
	</item>
	<item>
		<title>Practitioners as Students: What We Can Learn About Teaching Usability</title>
		<link>http://tc.eserver.org/29875.html</link>
		<guid>http://tc.eserver.org/29875.html</guid>
		<description>This paper presents the results of a study that contributes to our understanding of how to conduct and manage usability in the workplace. The study’s participants provided the dual perspective of practitioners working in industry and who are simultaneously enrolled in graduate studies. Recommendations for industry and academia are offered. The results have implications for helping technical communication professionals prepare for their expanding role in user-centered design.</description>
	</item>
	<item>
		<title>Selling Usability to Your Supervisor</title>
		<link>http://tc.eserver.org/28268.html</link>
		<guid>http://tc.eserver.org/28268.html</guid>
		<description>What&apos;s the best way to convince your supervisor to consider usability testing? Think about where your boss falls among the personality types described by the Myers-Briggs Type Indicator (MBTI).</description>
	</item>
	<item>
		<title>Corporate Usability Maturity: Stages 5-8</title>
		<link>http://tc.eserver.org/27317.html</link>
		<guid>http://tc.eserver.org/27317.html</guid>
		<description>An organization that reaches the managed usability stage still has far to go to reach usability nirvana. Attaining these higher maturity levels requires many years of effort.</description>
	</item>
	<item>
		<title>Corporate Usability Maturity: Stages 1-4</title>
		<link>http://tc.eserver.org/27166.html</link>
		<guid>http://tc.eserver.org/27166.html</guid>
		<description>As their usability approach matures, organizations typically progress through the same sequence of stages, from initial hostility to widespread reliance on user research.</description>
	</item>
	<item>
		<title>Enterprise Usability</title>
		<link>http://tc.eserver.org/26627.html</link>
		<guid>http://tc.eserver.org/26627.html</guid>
		<description>Usability goes beyond the level of individual users interacting with screens. It&apos;s also a question of how easy or cumbersome it is for the entire organization to use a system.</description>
	</item>
	<item>
		<title>Transforming Your Company to a Usability Culture</title>
		<link>http://tc.eserver.org/25139.html</link>
		<guid>http://tc.eserver.org/25139.html</guid>
		<description>Documentation is a finger in the eroding dam of an unusable product.</description>
	</item>
	<item>
		<title>Starting and Sustaining Usability Activities in a Company</title>
		<link>http://tc.eserver.org/24800.html</link>
		<guid>http://tc.eserver.org/24800.html</guid>
		<description>This panel presents our experience in starting and sustaining usability activities in different size companies. Some of these activities include educating others about usability, performing task analysis, testing prototypes of new user interfaces, writing usability specifications, and conducting both formal and informal usability tests. We will answer common questions about starting a usability program.</description>
	</item>
	<item>
		<title>Nip It in the NUB (Neo-Usability Bashing)</title>
		<link>http://tc.eserver.org/20649.html</link>
		<guid>http://tc.eserver.org/20649.html</guid>
		<description>Lately in some quarters it&apos;s cool to bash usability. This is a bit different from the &apos;Never heard of it and don&apos;t need it&apos; kind of opposition many of us have encountered in our careers. The Neo-Usability Bashing (NUB) argument goes something like this: Usability is so &apos;90s, so software-application centered. In this brave new networked world, usability&apos;s outlived its worth. On the Web, people aren&apos;t &apos;users&apos; as they were when they were using a spreadsheet or a word processing application, they&apos;re &apos;searchers,&apos; &apos;game-players,&apos; &apos;shoppers,&apos; etc.</description>
	</item>
	<item>
		<title>Changing the Process of Institutional Review Board Compliance</title>
		<link>http://tc.eserver.org/19935.html</link>
		<guid>http://tc.eserver.org/19935.html</guid>
		<description>In the past two years I have submitted proposals for the same study to eleven IRBs at colleges and universities across the country. While I strongly support the need for obtaining IRB approval, I believe as a discipline and as individuals we need to work to revise the IRB process. As it is now practiced at many institutions, the IRB process positions composition researchers and composition research in potentially problematic ways.</description>
	</item>
	<item>
		<title>Collecting Information: Qualitative Research Methods for Solving Workplace Problems</title>
		<link>http://tc.eserver.org/10386.html</link>
		<guid>http://tc.eserver.org/10386.html</guid>
		<description>There is evidence that technical communicators are not well prepared to collect information designed to answer workplace problems with systematic methods. Because mastering the use of qualitative collection methods such as observation, artifact searches, and interviews is often incorrectly assumed to require little expertise, my goal is to show how much thought has gone into the systematic use of such methods in the social sciences, including business. Thus, I focus on the basic considerations involved in collecting information using qualitative methods, especially (though not exclusively) targeted for technical communicators within industry. To that end, I cover two broad areas: (a) fundamental issues, such as formulating researchable questions and addressing credibility and practicality in workplace research, and (b) the details of collecting qualitative information and also determining the specifics of an information collection plan. The topic of analyzing information after it is collected is not covered </description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Usability/Workplace.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>