<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Hotz, Glenn</title>	<link>http://tc.eserver.org/authors/Hotz,_Glenn</link>
	<description>A bibliography of works by Hotz, Glenn 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>Hotz, Glenn</title>
		<link>http://tc.eserver.org/dir/Hotz,_Glenn</link>
	</image>
	<item>
		<title>Technical Writers and Trainers as Facilitators of Change</title>
		<link>http://tc.eserver.org/19082.html</link>
		<guid>http://tc.eserver.org/19082.html</guid>
		<description>Effective technical writing/training in my organization involves a model of performance that goes beyond traditional ideas about documentation and passive training methods. It involves a practice which, in a single word, I would call facilitating. Documents are part of it and new or changed behaviors by people in the organization are part of it, but a traditional writer or a traditional trainer, whether alone or working together, will not be able to achieve what we ask of them in our organization. Essentially, the model we have found successful and that we expect our technical writer/trainers to be able to implement involves the following.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Hotz,_Glenn.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>