<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Business Communication&gt;Policies and Procedures&gt;Case Studies</title>	<link>http://tc.eserver.org/dir/Articles/Business-Communication/Policies-and-Procedures/Case-Studies</link>
	<description>A listing of the most recently indexed works about Articles and Business Communication and Policies and Procedures and Case Studies 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;Business Communication&gt;Policies and Procedures&gt;Case Studies</title>
		<link>http://tc.eserver.org/dir/Articles/Business-Communication/Policies-and-Procedures/Case-Studies</link>
	</image>
	<item>
		<title>Developing Internal Procedures Online: The HowWe Manuals Project at Suncorp</title>
		<link>http://tc.eserver.org/24840.html</link>
		<guid>http://tc.eserver.org/24840.html</guid>
		<description>The process of implementing on-line documentation for the first time is always a daunting task, particularly if the target company has had little exposure to PC based systems. This is the challenge we faced at SUNCORP. Many people doubted the value of having reference material on-line (particularly those in the IT areas). Just as many doubted whether it was possible to do at all. Throughout the project we came across many obstacles, some man made, others system made; however the end result shows our resolve and determination has paid off for the staff of SUNCORP.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Business-Communication/Policies-and-Procedures/Case-Studies.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>