<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Mandel, Theo</title>	<link>http://tc.eserver.org/authors/Mandel,_Theo</link>
	<description>A bibliography of works by Mandel, Theo 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>Mandel, Theo</title>
		<link>http://tc.eserver.org/dir/Mandel,_Theo</link>
	</image>
	<item>
		<title>Quality Technical Information: Paving the Way for Usable Print and Web Interface Design</title>
		<link>http://tc.eserver.org/22920.html</link>
		<guid>http://tc.eserver.org/22920.html</guid>
		<description>Principles of information style and design have been around for years. Look at the shelf life of Strunk and White&apos;s classic The Elements of Style, published in 1959 and still a bestseller. Producing Quality Technical Information is a gem of a book, whose precise, bullet-style list of seven requirements and a checklist is now even more insightful in the fast-paced world of online information and the World-Wide Web. As a writer, I&apos;m amazed how the IBM authors crystallized the essence of good information design in less than 100 pages. This commentary describes how the book&apos;s seven qualities and thirty individual requirements can easily and usefully be extrapolated to address key issues of interface design and usability for today&apos;s professional designers and developers.</description>
	</item>
	<item>
		<title>A Solid Intranet in Eight Steps</title>
		<link>http://tc.eserver.org/12998.html</link>
		<guid>http://tc.eserver.org/12998.html</guid>
		<description>Corporate intranets are old news—everyone has one. But have you ever stepped back and wondered whether your intranet is cost-effective? Or, whether it increases your company&apos;s productivity? Have you ever asked your corporate users if they like it? For that matter, do they even use it? Because intranets have become commonplace, it&apos;s easy to assume they&apos;re well designed and usable. Unfortunately, most intranets have grown undirected and unchecked, like weeds in a garden. To dispel the myth that good intranet design just happens, let&apos;s look at the rules that my colleagues and I follow when we design corporate intranets.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Mandel,_Theo.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>