<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Rosenfeld, Louis</title>	<link>http://tc.eserver.org/authors/Rosenfeld,_Louis</link>
	<description>A bibliography of works by Rosenfeld, Louis 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>Rosenfeld, Louis</title>
		<link>http://tc.eserver.org/dir/Rosenfeld,_Louis</link>
	</image>
	<item>
		<title>Beyond Goals: Site Search Analytics from the Bottom Up</title>
		<link>http://tc.eserver.org/35163.html</link>
		<guid>http://tc.eserver.org/35163.html</guid>
		<description>While goal-driven analysis is wonderfully useful, we’ll explore a different, “bottom-up” approach that relies on pattern analysis and failure analysis to help you understand your users’ intent in qualitative ways that complement the top-down approach.</description>
	</item>
	<item>
		<title>80/20 Again: Critical Architectural Junctures</title>
		<link>http://tc.eserver.org/33351.html</link>
		<guid>http://tc.eserver.org/33351.html</guid>
		<description>Argues that we should focus our design and architectural efforts on the few options that provide the greatest benefit.</description>
	</item>
	<item>
		<title>Funding Enterprise Design Functions</title>
		<link>http://tc.eserver.org/33368.html</link>
		<guid>http://tc.eserver.org/33368.html</guid>
		<description>Enterprise design tasks are typically owned--if addressed at all--by a disjointed collection of business units concerned mostly with their own requirements and politics. The needs of the users of enterprise information and the managers concerned for those users often get left out. That&apos;s why I encourage placing enterprise design functions in the hands of a central, stand-alone team or business unit. Such a group has a broad perspective that counterbalances the localised goals of autonomous business units. But our new team will be a cost center; how do we pay for it?</description>
	</item>
	<item>
		<title>Critical Reviews of Corporate Websites</title>
		<link>http://tc.eserver.org/33174.html</link>
		<guid>http://tc.eserver.org/33174.html</guid>
		<description>Let&apos;s start with a single, seemingly simple premise: A website&apos;s main page should allow users to find the answers to basic questions. Amazingly, this fairly obvious rule is often ignored.</description>
	</item>
	<item>
		<title>Folksonomies? How about Metadata Ecologies?</title>
		<link>http://tc.eserver.org/33026.html</link>
		<guid>http://tc.eserver.org/33026.html</guid>
		<description>Folksonomies are clearly compelling, supporting a serendipitous form of browsing that can be quite useful. But they don&apos;t support searching and other types of browsing nearly as well as tags from controlled vocabularies applied by professionals.</description>
	</item>
	<item>
		<title>Revisiting Toys’R’Us</title>
		<link>http://tc.eserver.org/32925.html</link>
		<guid>http://tc.eserver.org/32925.html</guid>
		<description>How could an $11,000,000,000 company fail so miserably in its e-commerce efforts that it had to turn its storefront over to a relative newcomer? And what is the Big Lesson we can learn from Toys&apos;R&apos;Us&apos; difficulties?</description>
	</item>
	<item>
		<title>Brint.com: Why More is Not Better</title>
		<link>http://tc.eserver.org/32926.html</link>
		<guid>http://tc.eserver.org/32926.html</guid>
		<description>Information architect Lou Rosenfeld never thought he&apos;d criticize a website for being over-architected. Then he saw Brint.com and its 16 navigational systems.</description>
	</item>
	<item>
		<title>Everybody Hates the Cable Guy</title>
		<link>http://tc.eserver.org/32927.html</link>
		<guid>http://tc.eserver.org/32927.html</guid>
		<description>It&apos;s all too common for IT players to emphasize the technology and ignore the information that the technology exists to convey. Take my friendly local cable provider, MediaOne.</description>
	</item>
	<item>
		<title>Technical Support: (Yet Another) Holy Grail</title>
		<link>http://tc.eserver.org/32928.html</link>
		<guid>http://tc.eserver.org/32928.html</guid>
		<description>His own vendor conspiracy theories aside, Lou Rosenfeld knows of three main reason why technical &quot;support&quot; is often not support at all.</description>
	</item>
	<item>
		<title>Toys &apos;R&apos; Rushed: A Cautionary Tale</title>
		<link>http://tc.eserver.org/32929.html</link>
		<guid>http://tc.eserver.org/32929.html</guid>
		<description>Website critic Lou Rosenfeld is shopping for a baby present, but the website he&apos;s using is making his task tougher than it should be. Lou takes on www.toysrus.com.</description>
	</item>
	<item>
		<title>The Taxman Cometh but Merril Lynch Isn&apos;t Ready</title>
		<link>http://tc.eserver.org/32930.html</link>
		<guid>http://tc.eserver.org/32930.html</guid>
		<description>With April 15th approaching, Lou needed some basic tax information, but Merrill Lynch&apos;s labeling system made the easiest answers tough to find. </description>
	</item>
	<item>
		<title>Going Global the Centralized Way</title>
		<link>http://tc.eserver.org/32931.html</link>
		<guid>http://tc.eserver.org/32931.html</guid>
		<description>Creating a user interface that is consistent across a website isn&apos;t easy. But managers of sites that serve multilingual, multinational users are going to have to rise to the task, however daunting it may be. </description>
	</item>
	<item>
		<title>MSWeb: An Enterprise Intranet #1</title>
		<link>http://tc.eserver.org/23761.html</link>
		<guid>http://tc.eserver.org/23761.html</guid>
		<description>We&apos;re pleased to bring you the first of two excerpts from upcoming second editon of &apos;Information Architecture for the World Wide Web.&apos; The excerpts look at MSWeb, which the authors say provides a glimpse of what most intranets will be doing in three to five years.</description>
	</item>
	<item>
		<title>MSWeb: An Enterprise Intranet #2</title>
		<link>http://tc.eserver.org/23763.html</link>
		<guid>http://tc.eserver.org/23763.html</guid>
		<description>In our second excerpt from the newly-released second editon of &apos;Information Architecture for the World Wide Web.&apos; the authors look at how the MSWeb team succeeded at spreading its gospel through a huge organization like Microsoft when similar efforts at smaller companies often fail.</description>
	</item>
	<item>
		<title>Introduction to Information Architecture</title>
		<link>http://tc.eserver.org/21800.html</link>
		<guid>http://tc.eserver.org/21800.html</guid>
		<description>Information Architect: 1) the individual who organizes the patterns inherent in data, making the complex clear; 2) a person who creates the structure or map of information which allows others to find their personal paths to knowledge; 3) the emerging 21st century professional occupation addressing the needs of the age focused upon clarity, human understanding and the science of the organization of information.</description>
	</item>
	<item>
		<title>Search Systems</title>
		<link>http://tc.eserver.org/21756.html</link>
		<guid>http://tc.eserver.org/21756.html</guid>
		<description>This chapter often uses examples of search systems from sites that allow you to search the entire Web, as well as site-specific search engines. Although these web-wide tools tend to index a very broad collection of content, it is extremely useful to study them. Of all search systems, none has undergone the testing, usage, and investment that web-wide search tools have, so why not benefit from their research? Many of these tools are available for use on local sites as well.</description>
	</item>
	<item>
		<title>(Not) Defining the Damn Thing</title>
		<link>http://tc.eserver.org/21372.html</link>
		<guid>http://tc.eserver.org/21372.html</guid>
		<description>Discussions of how we should label ourselves and define our work are like flu epidemics. They break out from time to time, follow a fairly predictable course, and often make us want to barf.</description>
	</item>
	<item>
		<title>Seven Pitfalls to Avoid in Information Architecture</title>
		<link>http://tc.eserver.org/18707.html</link>
		<guid>http://tc.eserver.org/18707.html</guid>
		<description>Until recently, few people had heard of information architecture, which I define as the process of structuring and organizing information so that it’s easier for users to find and for owners to maintain. But go to any major job site today, and you’ll see many job openings for information architects. It’s not surprising: After five years of authoring and coding, many of us are stuck with Web sites and intranets that are huge, messy, unusable and impossible to maintain. With such a great demand for help, there are many inexperienced information architects repeatedly making the same mistakes. In the hope of fast-forwarding global information architecture literacy, here are some of the most common and avoidable errors I have learned from.</description>
	</item>
	<item>
		<title>The Untimely Death of Yahoo, or, How the Double-Whammy of Web Architecture and Information Retrieval Will Do Yahoo In</title>
		<link>http://tc.eserver.org/18708.html</link>
		<guid>http://tc.eserver.org/18708.html</guid>
		<description>Yahoo is truly one of the Best of the Net, as it has filled an enormous void in the areas of browsing and searching Internet-based information. So I hope you&apos;ll believe that I am truly sad as I predict the death of Yahoo. It seems inevitable, as Yahoo&apos;s organization, its information architecture, will collapse under the weight of the high volume of entries. And, unfortunately, searching won&apos;t solve the problem of volume.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Rosenfeld,_Louis.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>