<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Argus Center</title>	<link>http://tc.eserver.org/publisher/Argus_Center</link>
	<description>A listing of works published by Argus Center 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>Argus Center</title>
		<link>http://tc.eserver.org/dir/Argus_Center</link>
	</image>
	<item>
		<title>Salaries and Benefits for Information Architects</title>
		<link>http://tc.eserver.org/33252.html</link>
		<guid>http://tc.eserver.org/33252.html</guid>
		<description>The Argus Center for Information Architects received 229 responses to this survey, which ran from January 3 through January 10, 2001.</description>
	</item>
	<item>
		<title>Information Architecture and Personalization</title>
		<link>http://tc.eserver.org/33172.html</link>
		<guid>http://tc.eserver.org/33172.html</guid>
		<description>This white paper demonstrates the use of information architecture components as a foundation for thinking about personalization. After defining the information architecture components, it describes a model that combines the components into a complete personalization system. This model could be used to guide your personalization system development methodology, evaluate a set of personalization systems, or merely to give you the terminology to help you communicate about personalization.</description>
	</item>
	<item>
		<title>Retail Ecologies, E-Commerce, and Information Architecture</title>
		<link>http://tc.eserver.org/33173.html</link>
		<guid>http://tc.eserver.org/33173.html</guid>
		<description>This white paper discusses information architecture in terms of retail ecology theory and how it translates to e-commerce. It begins by defining what a retail ecology is, and then discusses how the information architecture of e-commerce sites can change for four different types of retail ecologies.</description>
	</item>
	<item>
		<title>Information Architecture Glossary</title>
		<link>http://tc.eserver.org/23185.html</link>
		<guid>http://tc.eserver.org/23185.html</guid>
		<description>This glossary is intended to foster development of a shared vocabulary within the new and rapidly evolving field of information architecture. It should serve as a valuable reference for anyone involved with or interested in the design of information architectures for web sites, intranets and other information systems.</description>
	</item>
	<item>
		<title>Information Architecture of the Shopping Cart</title>
		<link>http://tc.eserver.org/23186.html</link>
		<guid>http://tc.eserver.org/23186.html</guid>
		<description>This white paper explores the principles of design for process-oriented information architectures by illustrating the best practices in the design of e-commerce ordering systems commonly referred to as &apos;shopping carts.&apos;</description>
	</item>
	<item>
		<title>Evaluating Information Architecture</title>
		<link>http://tc.eserver.org/23096.html</link>
		<guid>http://tc.eserver.org/23096.html</guid>
		<description>This white paper explores the why&apos;s, what&apos;s, and how&apos;s of evaluating a web site&apos;s information architecture. It aims to raise consciousness about the evaluation of IA and to provide:&#xD;1) Web site owners and other decision-makers with an understanding of evaluation issues; and &#xD;2) Information architects with a synthesis of evaluation techniques.</description>
	</item>
	<item>
		<title>An Ecological Approach to Design</title>
		<link>http://tc.eserver.org/22707.html</link>
		<guid>http://tc.eserver.org/22707.html</guid>
		<description>This talk will explain how to use ecological design, which is an expansion of ethnography, to leverage both the rich local information from case studies, and a wider sociological perspective to take account of global realities.</description>
	</item>
	<item>
		<title>Defining Information Architecture</title>
		<link>http://tc.eserver.org/21736.html</link>
		<guid>http://tc.eserver.org/21736.html</guid>
		<description>What is information architecture? Is it a nascent field or a flash in the pan? What does an information architect do? Are you an information architect? Am I? Is that the right label for our discipline? Do labels and definitions matter?</description>
	</item>
	<item>
		<title>Educating the Information Architect</title>
		<link>http://tc.eserver.org/21733.html</link>
		<guid>http://tc.eserver.org/21733.html</guid>
		<description>The good news is that the job market for information architects is exploding. Searches on sites like Monster.com regularly turn up 200 to 300 postings for &quot;information architects.&quot; From consulting firms like Argus and Scient to e-businesses like LookSmart to Fortune 500&apos;s like Cisco, everyone is desperately seeking information architects.&#xD;&#xD;The bad news is that there&apos;s no established educational degree program geared specifically to meet the needs of aspiring information architects.</description>
	</item>
	<item>
		<title>Information Architecture and Business Strategy</title>
		<link>http://tc.eserver.org/21732.html</link>
		<guid>http://tc.eserver.org/21732.html</guid>
		<description>Information architects need a good understanding of business strategy and its relationship to information architecture.</description>
	</item>
	<item>
		<title>Information Architecture and Ulcers</title>
		<link>http://tc.eserver.org/21735.html</link>
		<guid>http://tc.eserver.org/21735.html</guid>
		<description>Being an information architect can be stressful. There are certain points in the design process that are more stress-inducing than others.</description>
	</item>
	<item>
		<title>Lessons Learned from the Dot.Com Crash: A Passenger&apos;s Story</title>
		<link>http://tc.eserver.org/21731.html</link>
		<guid>http://tc.eserver.org/21731.html</guid>
		<description>Describes the inner workings of the dot.coms during the high-speed transition from irrational exuberance to outright panic.</description>
	</item>
	<item>
		<title>Little Blue Folders</title>
		<link>http://tc.eserver.org/21734.html</link>
		<guid>http://tc.eserver.org/21734.html</guid>
		<description>The Web is big. A billion pages big, according to a recent study by Inktomi and the NEC Research Institute. It&apos;s the ultimate testing ground for information retrieval technologies.&#xD;&#xD;If your search engine can automatically bring order to this overwhelming global mess of stuff, just think what it can do for a single web site or intranet.</description>
	</item>
	<item>
		<title>Big Architect, Little Architect</title>
		<link>http://tc.eserver.org/21727.html</link>
		<guid>http://tc.eserver.org/21727.html</guid>
		<description>First came the primordial soup. Thousands of relatively simple single-celled web sites appeared on the scene, and each one was quickly claimed by a multi-functional organism called a &quot;webmaster.&quot;&#xD;&#xD;A symbiotic relationship quickly became apparent. Webmaster fed web site. Web site got bigger and more important. So did the role of the webmaster. Life was good.&#xD;&#xD;Then, bad things started to happen. The size and complexity and importance of the web sites began to spiral out of control. Mutations started cropping up.&#xD;&#xD;Strange new organisms with names like interaction designer, usability engineer, customer experience analyst, and information architect began competing with the webmaster and each other for responsibilities and rewards. Equilibrium had been punctuated and we entered the current era of rapid speciation and specialization.</description>
	</item>
	<item>
		<title>An Information Architect&apos;s Manifesto</title>
		<link>http://tc.eserver.org/21725.html</link>
		<guid>http://tc.eserver.org/21725.html</guid>
		<description>Information architects of the world, unite! The environment has changed. Now, so must we!</description>
	</item>
	<item>
		<title>Software for Information Architects</title>
		<link>http://tc.eserver.org/21726.html</link>
		<guid>http://tc.eserver.org/21726.html</guid>
		<description>Information professionals have a love-hate relationship with technology. We love IT because it has made our jobs necessary by enabling the creation and connection of tremendous volumes of content, applications and processes. We hate IT because it constantly threatens to replace the need for us.</description>
	</item>
	<item>
		<title>Analyzing the Analysts</title>
		<link>http://tc.eserver.org/18432.html</link>
		<guid>http://tc.eserver.org/18432.html</guid>
		<description>An information architecture analysis of top business analysts&apos; web sites.</description>
	</item>
	<item>
		<title>Argus Center for Information Architecture</title>
		<link>http://tc.eserver.org/18431.html</link>
		<guid>http://tc.eserver.org/18431.html</guid>
		<description>The Argus Center for Information Architecture works to define and advance the evolving discipline of information architecture. The Argus Center serves as a focal point for learning about the theory and practice of information architecture. Towards this goal, we: manage a selective collection of links to the most remarkable content, events, and people in our field; produce original articles, white papers, conferences, and seminars that draw from the experience and expertise of the Argus team; conduct research, independently and through partnerships, focused on improving our collective understanding of information architecture.</description>
	</item>
	<item>
		<title>The Ethics of Information Architecture</title>
		<link>http://tc.eserver.org/18434.html</link>
		<guid>http://tc.eserver.org/18434.html</guid>
		<description>Are you aware that the practice of information architecture is riddled with powerful moral dilemmas? Do you realize that decisions about labeling and granularity can save or destroy lives? Have you been designing ethical information architectures?</description>
	</item>
	<atom:link href="http://tc.eserver.org/publisher/Argus_Center.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>