<?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;Collaboration&gt;Technical Writing</title>	<link>http://tc.eserver.org/dir/Articles/Documentation/Collaboration/Technical-Writing</link>
	<description>A listing of the most recently indexed works about Articles and Documentation and Collaboration 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;Collaboration&gt;Technical Writing</title>
		<link>http://tc.eserver.org/dir/Articles/Documentation/Collaboration/Technical-Writing</link>
	</image>
	<item>
		<title>Collaborative Walkthrough Video</title>
		<link>http://tc.eserver.org/32161.html</link>
		<guid>http://tc.eserver.org/32161.html</guid>
		<description>Collaborative walkthroughs are a technique that my team used while rewriting our Help and adopting DITA. We believe that we were able to improve the user experience by improving the collaborative experience.</description>
	</item>
	<item>
		<title>Strategies for Winning Recognition: Building a Visible, Viable, and Valuable Documentation Team</title>
		<link>http://tc.eserver.org/23752.html</link>
		<guid>http://tc.eserver.org/23752.html</guid>
		<description>Technical writing teams can improve their standing within their organizations. The purpose of this presentation is to share our experiences at Mirant where&#xD;we&apos;ve achieved recognition and respect as a vital&#xD;internal service to the IT department and, increasingly,&#xD;to the rest of the company.</description>
	</item>
	<item>
		<title>The Team Approach to Writing Policies and Procedures</title>
		<link>http://tc.eserver.org/23154.html</link>
		<guid>http://tc.eserver.org/23154.html</guid>
		<description>Although many companies claim to have working teams within their corporate structure, it may be difficult to use the same approach for writing documentation. With the&#xD;demands for controlled documentation to meet quality&#xD;standards, involvement in policy/procedure writing is an&#xD;important factor in developing a sense of ownership and&#xD;commitment to maintaining a document control system.&#xD;A team approach to writing procedures may involve&#xD;more time, but the results are operations consensus,&#xD;improved writing skills, and a boost of professional&#xD;confidence.</description>
	</item>
	<item>
		<title>The Issue of Quality in Professional Documentation: How Can Academia Make More of a Difference?</title>
		<link>http://tc.eserver.org/13920.html</link>
		<guid>http://tc.eserver.org/13920.html</guid>
		<description>This article recommends strategies academics can use to contribute to an issue of great interest in industry: how best to define, measure, and achieve quality documentation.  These strategies include contextualizing quality definitions, advocating the use of multiple quality measures, conducting research to identify specific heuristics for defining and measuring quality in particular workplace contexts, and partnering with industry to educate upper management about those heuristics and the benefits of promoting technical communicators to the strategic role of organizational “gatekeepers of quality.”</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Documentation/Collaboration/Technical-Writing.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>