<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Kowalski, Lee Anne, Andrea Ames, Michelle Corbin and David McCaleb</title>	<link>http://tc.eserver.org/authors/Kowalski,_Lee_Anne,_Andrea_Ames,_Michelle_Corbin_and_David_McCaleb</link>
	<description>A bibliography of works by Kowalski, Lee Anne, Andrea Ames, Michelle Corbin and David McCaleb 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>Kowalski, Lee Anne, Andrea Ames, Michelle Corbin and David McCaleb</title>
		<link>http://tc.eserver.org/dir/Kowalski,_Lee_Anne,_Andrea_Ames,_Michelle_Corbin_and_David_McCaleb</link>
	</image>
	<item>
		<title>Integrating Information Architecture into Your Information Development Processes</title>
		<link>http://tc.eserver.org/29784.html</link>
		<guid>http://tc.eserver.org/29784.html</guid>
		<description>The most critical and time-consuming aspect of your decision to adopt information architecture as a backbone of your information development process might not be the adoption of new guidelines or tools, but moving the mindset and culture of the organization so that it can operate effectively in the new paradigm. Using examples from real experiences, the authors of this paper describe the organizational &apos;culture shock&apos; that can occur when a team or organization moves to an information-architected model for content delivery--the likely pitfalls and some ways to overcome them.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Kowalski,_Lee_Anne,_Andrea_Ames,_Michelle_Corbin_and_David_McCaleb.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>