<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Ladner, Sam</title>	<link>http://tc.eserver.org/authors/Ladner,_Sam</link>
	<description>A bibliography of works by Ladner, Sam 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>Ladner, Sam</title>
		<link>http://tc.eserver.org/dir/Ladner,_Sam</link>
	</image>
	<item>
		<title>Organizational Culture 101: A Practical How-To For Interaction Designers</title>
		<link>http://tc.eserver.org/35231.html</link>
		<guid>http://tc.eserver.org/35231.html</guid>
		<description>It’s happened to all of us. We walk into what we think is a Web redesign project, only to find we have unwittingly ignited the fires of WW III in our client’s organization. What begins as a simple design project descends – quickly – into an intra-organizational battle, with the unprepared interaction designer caught in the crossfire.&#xD;&#xD;What is it about design projects that seem to attract such power struggles? Contrary to what you might think, being stuck in the middle of an internecine battle is actually an opportunity to effect meaningful change on your client’s organization. But it requires a set of practical tools to negotiate these battles and a more sophisticated language and knowledge to exploit these events to create meaningful change.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Ladner,_Sam.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>