<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Bachmann, Karen L</title>	<link>http://tc.eserver.org/authors/Bachmann,_Karen_L</link>
	<description>A bibliography of works by Bachmann, Karen L 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>Bachmann, Karen L</title>
		<link>http://tc.eserver.org/dir/Bachmann,_Karen_L</link>
	</image>
	<item>
		<title>Documenting User-Centered Design Best Practices</title>
		<link>http://tc.eserver.org/32540.html</link>
		<guid>http://tc.eserver.org/32540.html</guid>
		<description>When initiating or expanding the role of user-centered design (UCD) in an organization, consider documenting UCD best practices as they fit within existing processes and the best practice of other areas. Such documentation communicates the role and value of UCD throughout the organization in terms familiar to your organization. Because what best practices means varies from company to company, there is no single way to do this. Here are some questions to consider.</description>
	</item>
	<item>
		<title>Usability Requirements: Making User Satisfaction a Measure of Product Success</title>
		<link>http://tc.eserver.org/29905.html</link>
		<guid>http://tc.eserver.org/29905.html</guid>
		<description>Defining usability requirements at the beginning of the project increases the chances that the end product will meet the users&apos; goals and create a satisfying user experience. Unfortunately, such requirements are often not considered with the same priority as functional or other technical requirements. This presentation defines usability requirements, proposes guidelines for creating measurable requirements, and elaborates the components of a well-constructed usability requirement.</description>
	</item>
	<item>
		<title>Understanding Principles of Usability, Part 1</title>
		<link>http://tc.eserver.org/28797.html</link>
		<guid>http://tc.eserver.org/28797.html</guid>
		<description>In this podcast, Karen Bachmann, manager of the Usability and User Experience SIG, provides an overview of the user-centered design process. This is part one of a two part series.</description>
	</item>
	<item>
		<title>Understanding Principles of Usability, Part 2</title>
		<link>http://tc.eserver.org/28796.html</link>
		<guid>http://tc.eserver.org/28796.html</guid>
		<description>This is part two of Karen Bachmann&apos;s presentation on Usability. In this part of her presentation, Karen gets more in depth with principles and methods for usability.</description>
	</item>
	<item>
		<title>The Power of Storytelling</title>
		<link>http://tc.eserver.org/28588.html</link>
		<guid>http://tc.eserver.org/28588.html</guid>
		<description>How Community Manager Karen Bachmann has learned about the power and importance of storytelling, and some of the many stories that have deeply affected her.</description>
	</item>
	<item>
		<title>Let&apos;s Get It Started!</title>
		<link>http://tc.eserver.org/28498.html</link>
		<guid>http://tc.eserver.org/28498.html</guid>
		<description>STC communities have moved from trying to figure out how they will work in the new model to starting to make the kinds of fundamental changes and undertake initiatives that will build value for members. We are starting to understand how to &apos;play&apos; within and succeed with our new rules. For UUX to undertake new initiatives, we need more members to volunteer.</description>
	</item>
	<item>
		<title>Epiphany in the Trenches</title>
		<link>http://tc.eserver.org/27812.html</link>
		<guid>http://tc.eserver.org/27812.html</guid>
		<description>Recognize the many paths to success and be prepared to forge your own if needed. You may find at the end of your &apos;wrong way&apos; happy clients, satisfied users, and a successful and delivered system.</description>
	</item>
	<item>
		<title>A Question of Process</title>
		<link>http://tc.eserver.org/26406.html</link>
		<guid>http://tc.eserver.org/26406.html</guid>
		<description>When we consider the right questions to ask in usability, we first think of the questions we should ask our users and stakeholders. This line of questioning is a necessary part of our jobs. However, I have seen few articles outside of the ROI of usability discussions where usability professionals ask questions about the usability of our own processes and approaches.</description>
	</item>
	<item>
		<title>The Pulse of the Usability Community: Transformation and UUX</title>
		<link>http://tc.eserver.org/25389.html</link>
		<guid>http://tc.eserver.org/25389.html</guid>
		<description>When you renew your STC membership, be sure to select STC Usability and User Experience (UUX) as one of your communities.</description>
	</item>
	<item>
		<title>Usability, User Experience, Or Both?</title>
		<link>http://tc.eserver.org/24920.html</link>
		<guid>http://tc.eserver.org/24920.html</guid>
		<description>Explains how the new name of the former STC Usability SIG better serves the growing number of technical communicators whose work encompasses the overall product--not just usability or documentation.</description>
	</item>
	<item>
		<title>Electronic Voting: Usability, Communication, Trust</title>
		<link>http://tc.eserver.org/23873.html</link>
		<guid>http://tc.eserver.org/23873.html</guid>
		<description>Beyond just the undeniable importance of a usable  form and voting mechanism, is the need to consider the comfort and  satisfaction of voters dealing with sometimes radically changed voting  systems, especially when the move is from paper-based voting systems to  electronic systems.</description>
	</item>
	<item>
		<title>The Search for Well-Defined Usability Discipline</title>
		<link>http://tc.eserver.org/23881.html</link>
		<guid>http://tc.eserver.org/23881.html</guid>
		<description>The message about usability is reaching general audiences. However, sometimes the message is garbled and sometimes it is  overlooked entirely.</description>
	</item>
	<item>
		<title>Communities of Practice: Dealing with the Changes in the Technical Communication Field</title>
		<link>http://tc.eserver.org/23855.html</link>
		<guid>http://tc.eserver.org/23855.html</guid>
		<description>STC has been challenged by the changing  economy and the evolving nature of our work and career development. These  challenges have required Society leaders to look carefully into how the  STC should change to better serve a diverse and global membership.</description>
	</item>
	<item>
		<title>Looking Forward to A New Year in Usability</title>
		<link>http://tc.eserver.org/23863.html</link>
		<guid>http://tc.eserver.org/23863.html</guid>
		<description>A common theme in most stories is that introducing usability into a  company, or even just into your own technical communication work, is often a long-term effort. In my own experience, my first effort to introduce  usability at my then employer took almost two years to move from a few  isolated activities and providing occasional design advice to interface  developers into a fully recognized user interface design role.</description>
	</item>
	<item>
		<title>Prototyping and Usability Testing with Visio</title>
		<link>http://tc.eserver.org/20930.html</link>
		<guid>http://tc.eserver.org/20930.html</guid>
		<description>An overview of prototyping: uses, functions and types of prototypes.</description>
	</item>
	<item>
		<title>Applying Computer Analysis and Design Techniques to Document Component-Based Software</title>
		<link>http://tc.eserver.org/20275.html</link>
		<guid>http://tc.eserver.org/20275.html</guid>
		<description>Facing the challenges involved in developing documentation for component-based software (for example, object-oriented technology, intelligent agents, and distributed computing) requires a documentation&#xD;strategy based on the same processes and methodologies&#xD;used by such technologies. These strategies need to be&#xD;adapted to meet documentation, rather than coding&#xD;needs. Developing this strategy now, as component-based&#xD;technology is still maturing, will help technical&#xD;communicators keep pace.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Bachmann,_Karen_L.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>