<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>DonnaM</title>	<link>http://tc.eserver.org/publisher/DonnaM</link>
	<description>A listing of works published by DonnaM 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>DonnaM</title>
		<link>http://tc.eserver.org/dir/DonnaM</link>
	</image>
	<item>
		<title>Taking a Content Inventory</title>
		<link>http://tc.eserver.org/33272.html</link>
		<guid>http://tc.eserver.org/33272.html</guid>
		<description>You take a content inventory because, before redesigning a website or intranet, you need to know what you have. This is especially important if you will be migrating your content to a new structure or new CMS - at some point you need to know every single content element.</description>
	</item>
	<item>
		<title>Making Decisions About User Research</title>
		<link>http://tc.eserver.org/32940.html</link>
		<guid>http://tc.eserver.org/32940.html</guid>
		<description>We know that we should do user research for projects. All the user-centred design material says so, we talk about it at conferences, we put it in proposals. We just know that it is a good thing to do.&#xD;&#xD;But when I talk to people about their actual projects, I find that very few people actually do user research. There are many many reasons (no time, no money, already know what users need etc etc etc).&#xD;&#xD;I think that part of the reason it doesn’t happen is also that we don’t have good tools to tell us just how much research to do, and even when it isn’t necessary at all to do research.</description>
	</item>
	<item>
		<title>Yes, Information Architecture is Rocket Science</title>
		<link>http://tc.eserver.org/32941.html</link>
		<guid>http://tc.eserver.org/32941.html</guid>
		<description>Why do I think there is some complexity to creating a good IA for a website, when to others it appears simple?</description>
	</item>
	<item>
		<title>Card Sorting Tools: Final Summary</title>
		<link>http://tc.eserver.org/24755.html</link>
		<guid>http://tc.eserver.org/24755.html</guid>
		<description>A summary of how IBM&apos;s USort/EzCalc and CardZort worked for results entry and analysis.</description>
	</item>
	<atom:link href="http://tc.eserver.org/publisher/DonnaM.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>