<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Design&gt;Information Design&gt;Usability</title>	<link>http://tc.eserver.org/dir/Design/Information-Design/Usability</link>
	<description>A listing of the most recently indexed works about Design and Information Design and Usability 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>Design&gt;Information Design&gt;Usability</title>
		<link>http://tc.eserver.org/dir/Design/Information-Design/Usability</link>
	</image>
	<item>
		<title>IAに起因するタスク失敗は相変わらず不利益</title>
		<link>http://tc.eserver.org/34904.html</link>
		<guid>http://tc.eserver.org/34904.html</guid>
		<description>タスク成功率は、2004 年のユーザビリティ統計と比べると大きく上昇した。しかしそれにもかかわらず、ユーザがタスクを完遂できないケースがあり、その原因の大半は情報アーキテクチャ(IA)の出来の悪さにある。 </description>
	</item>
	<item>
		<title>メガドロップダウン式のナビゲーションメニューは効果あり</title>
		<link>http://tc.eserver.org/34908.html</link>
		<guid>http://tc.eserver.org/34908.html</guid>
		<description>大きな二次元のドロップダウンパネルは、ナビゲーションの選択肢をグループ化することでスクロールの必要性を無くし、タイポグラフィやアイコン、ツールチップを使うことで、ユーザの選択できる内容をわかりやすく提示してくれる。</description>
	</item>
	<item>
		<title>Information Architecture Task Failures Remain Costly</title>
		<link>http://tc.eserver.org/34290.html</link>
		<guid>http://tc.eserver.org/34290.html</guid>
		<description>Task success is up substantially compared with usability statistics from 2004. Bad information architecture causes most of the remaining user failures.</description>
	</item>
	<item>
		<title>Mega Drop-Down Navigation Menus Work Well</title>
		<link>http://tc.eserver.org/34293.html</link>
		<guid>http://tc.eserver.org/34293.html</guid>
		<description>Given that regular drop-down menus are rife with usability problems, it takes a lot for me to recommend a new form of drop-down. But, as our testing videos show, mega drop-downs overcome the downsides of regular drop-downs. Thus, I can recommend one while warning against the other.</description>
	</item>
	<item>
		<title>User Experience Designer or ...? What You Call Yourself Matters</title>
		<link>http://tc.eserver.org/34046.html</link>
		<guid>http://tc.eserver.org/34046.html</guid>
		<description>Using a self-designation with a certain amount of specificity sacrifices practicality to accuracy. Individuals who have been hired as a single-function specialist may have the luxury of presenting as a “usability engineer” or “information architect”. For the independent consultant, this strategy can have definite negative consequences.</description>
	</item>
	<item>
		<title>Making the Right Constraints for Usable and Accessible User Interfaces</title>
		<link>http://tc.eserver.org/33840.html</link>
		<guid>http://tc.eserver.org/33840.html</guid>
		<description>This paper focuses on managing constraints in a way that enables developers to create an accessible and usable user interface (UI). The constraining processes presented in this paper comprise of a language to describe a logical web page in an application, a basic bottom-up repository management system and the processing required for compiling pages.</description>
	</item>
	<item>
		<title>Information Architecture is Not Usability</title>
		<link>http://tc.eserver.org/33449.html</link>
		<guid>http://tc.eserver.org/33449.html</guid>
		<description>The distinction between information architecture and usability may seem like semantics, but there are significant differences between the two disciplines. Though they are often discussed interchangeably, and practitioners are often well-versed in both, information architecture and usability differ in their scope and areas of focus.</description>
	</item>
	<item>
		<title>Usability and Maintainability: Navigable Information</title>
		<link>http://tc.eserver.org/33417.html</link>
		<guid>http://tc.eserver.org/33417.html</guid>
		<description>This post is part of a series on usability and maintainability. At first, meeting the needs of content consumers through usability can seem at odds with meeting needs of technical communicators through maintainability. My purpose in these posts is to discuss how technical communication best practices can satisfy both needs. I’ll use Gurak and Lannon’s usability criteria of users being able to “find what they need, understand the language, follow the instructions, and read the graphics.”</description>
	</item>
	<item>
		<title>&apos;Click Here&apos;: Needless Words</title>
		<link>http://tc.eserver.org/33199.html</link>
		<guid>http://tc.eserver.org/33199.html</guid>
		<description>The words &apos;click here for...&apos; and &apos;click here to...&apos; serve no purpose within links. Unfortunately, many news sites still use them. According to Google, &apos;click here&apos; is on about 8,970 pages at sptimes.com alone.</description>
	</item>
	<item>
		<title>Essential Navigation Checklists for Web Design</title>
		<link>http://tc.eserver.org/33200.html</link>
		<guid>http://tc.eserver.org/33200.html</guid>
		<description>These checklists pull together best practice in the disciplines of information design, usability and accessibility, into an easy to apply format. If you are already familiar with those topics, the checklists serve as a handy reminder that is easy to refer to and apply when planning navigation. If unfamiliar it&apos;s also a fast-track lesson - providing you with a head-start in getting it right and enables you to make better informed choices / compromises.</description>
	</item>
	<item>
		<title>How Google Manages its Home Page</title>
		<link>http://tc.eserver.org/33202.html</link>
		<guid>http://tc.eserver.org/33202.html</guid>
		<description>An average person can deal with only 7-10 choices on a web page, according to Google research. That&apos;s why it&apos;s so hard to get a link on the Google home page.</description>
	</item>
	<item>
		<title>Readability, Browsability, Searchability Plus Assistance</title>
		<link>http://tc.eserver.org/33115.html</link>
		<guid>http://tc.eserver.org/33115.html</guid>
		<description>Readability, browsability, and searchability do not have to be equally represented in every information system. As your collection of information increases, different aspects of these qualities take on greater significance. Thus, the amount of readability, browsability, and searchability your information system exhibits depends on the type and quality of your collected data, as well as the information needs of your clientele.</description>
	</item>
	<item>
		<title>Considering Product Usability Along with Information Usability</title>
		<link>http://tc.eserver.org/30414.html</link>
		<guid>http://tc.eserver.org/30414.html</guid>
		<description>In this progression we will examine ways that technical communicators can improve both information usability and product usability. The presentation will center around two major points.</description>
	</item>
	<item>
		<title>PDF Link Usability</title>
		<link>http://tc.eserver.org/30191.html</link>
		<guid>http://tc.eserver.org/30191.html</guid>
		<description>Das kennt man: ein ahnungsloser Klick und plötzlich öffnet sich eine mega-lange PDF-Datei. Seitengestalter sind deshalb angehalten Links auf PDF-Dateien zu kennzeichnen. Selbstverständlich macht das inzwischen auch (fast) jeder.</description>
	</item>
	<item>
		<title>PDF Usability: Debate and Reality</title>
		<link>http://tc.eserver.org/30190.html</link>
		<guid>http://tc.eserver.org/30190.html</guid>
		<description>This article examines the claims of those PDF critics and argues that usability complaints about PDF documents are misdirected, and further, highlights some of the key reasons why PDF is the preferred electronic document format.</description>
	</item>
	<item>
		<title>Effects of RSVP Display Design on Visual Performance in Accomplishing Dual Tasks with Small Screens</title>
		<link>http://tc.eserver.org/29821.html</link>
		<guid>http://tc.eserver.org/29821.html</guid>
		<description>Rapid serial visual presentation (RSVP) represents a mechanism for exhibiting temporal information instead of spatial information to overcome the limitations of small-screen devices. Previous studies examining this area focused only on information presented by RSVP displays and disregarded changes in the performance of accompanying tasks associated with such displays. Therefore, this investigation performed a dual-task experiment (a search task for static information and a reading task for RSVP display information) to examine the effects of presentation mode (character-by-character, word-by-word, and one-line format), speed (171, 260, 350, and 430 characters per minute, or cpm), and text-flow orientation (vertical and horizontal orientation) of RSVP display information on the visual performance of users during different stages of usage (whether current usage is the first, second, third, fourth, fifth, or eighth day of usage) for a small screen.</description>
	</item>
	<item>
		<title>In Search of Salience: A Response-Time and Eye-Movement Analysis of Bookmark Recognition</title>
		<link>http://tc.eserver.org/29355.html</link>
		<guid>http://tc.eserver.org/29355.html</guid>
		<description>Describes the effect of bookmark naming on bookmark recognition. The purpose is to provide empirically-determined guidelines for web producers on how to title pages in order to optimise the recognition of bookmarks by users, and increase the rate of revisitation to their websites.</description>
	</item>
	<item>
		<title>Issues of Saliency and Recognition in the Search for Web Page Bookmarks</title>
		<link>http://tc.eserver.org/29357.html</link>
		<guid>http://tc.eserver.org/29357.html</guid>
		<description>Describes the effect of bookmark naming on bookmark recognition. The purpose was to provide empirically-determined guidelines for web producers on how to title pages in order to optimise the recognition of bookmarks by users, and to increase the rate of revisitation as a result.</description>
	</item>
	<item>
		<title>Bridging the Gap: From Raw Usability Testing Data to Design Implementation</title>
		<link>http://tc.eserver.org/28267.html</link>
		<guid>http://tc.eserver.org/28267.html</guid>
		<description>Learn practical ways to influence members of your company’s product engineering group with usability testing data. Putting the authors’ tips into practice will help you improve the design of your company’s products.</description>
	</item>
	<item>
		<title>IA and Usability: When to Start</title>
		<link>http://tc.eserver.org/28217.html</link>
		<guid>http://tc.eserver.org/28217.html</guid>
		<description>Information design is supposed to be done from the very beginning, as it&apos;s not a cosmetic but a substantial discipline. You are much faster if you hire an information designer in the beginning.</description>
	</item>
	<item>
		<title>The Essentials of a Database Quality Process</title>
		<link>http://tc.eserver.org/27286.html</link>
		<guid>http://tc.eserver.org/27286.html</guid>
		<description>Many steps are involved in the process of turning an initial concept for a database into a finished product that meets the needs of its user community. In this paper, we describe those steps in the context of a four-phase process with particular emphasis on the quality-related issues that need to be addressed in each phase to ensure that the final product is a high quality database. The basic requirements for a successful database quality process are presented with specific examples drawn from experience gained in the Standard Reference Data Program at the National Institute of Standards and Technology.</description>
	</item>
	<item>
		<title>Jobs@OK/Cancel</title>
		<link>http://tc.eserver.org/27259.html</link>
		<guid>http://tc.eserver.org/27259.html</guid>
		<description>This site is a consolidation of publicly available and privately submitted job postings in HCI, Usability, User Experience, Interaction Design, Information Architecture and Ergonomics.</description>
	</item>
	<item>
		<title>From Data Drought to Factoid Flood: Reinforcing the Banks of the River of Communication</title>
		<link>http://tc.eserver.org/24206.html</link>
		<guid>http://tc.eserver.org/24206.html</guid>
		<description>Information, once rare and valuable, is now as plentiful as it is meaningless. The constant accessibility rendered by various &apos;networking&apos; technologies has led to a veritable glut of information. Deluged with data and flooded with facts, we are drowning in a river of communication with no clear direction or purpose. Media-mesmerized and stimuli-saturated, we are caught up in the murky current, making it increasingly more difficult to keep our heads above water. Whether we sink or swim will depend on how effective we are at controlling and managing the flow, how efficient we are at fishing for essence and meaning, and how adept we are at preserving the ecology between man and this digital morass.</description>
	</item>
	<item>
		<title>Don&apos;t Get Burned by Bad Mapping</title>
		<link>http://tc.eserver.org/23985.html</link>
		<guid>http://tc.eserver.org/23985.html</guid>
		<description>The term mapping describes the relationship between a control, the thing it affects, and the intended result. Poor mapping is evident when a control does not relate visually or symbolically with the object it affects, requiring the user to stop and think, &apos;what&apos;s going to happen when I turn this knob?&apos;</description>
	</item>
	<item>
		<title>Incorporating Navigation Research into a Design Method</title>
		<link>http://tc.eserver.org/23816.html</link>
		<guid>http://tc.eserver.org/23816.html</guid>
		<description>A presentation about whether an underlying spatial metaphor aids information design usability.</description>
	</item>
	<item>
		<title>Influence of Training and Exposure on the Usage of Breadcrumb Navigation</title>
		<link>http://tc.eserver.org/23301.html</link>
		<guid>http://tc.eserver.org/23301.html</guid>
		<description>Recent studies have shown that while the use of breadcrumb trails to navigate a website can be helpful, few users choose to utilize this method of navigation. This study investigates the effects of &apos;mere exposure&apos; and training on breadcrumb usage. Findings indicate that brief training on the benefits of breadcrumb usage resulted in more efficient search behavior.</description>
	</item>
	<item>
		<title>Web Page Design: Implications of Memory, Structure and Scent for Information Retrieval</title>
		<link>http://tc.eserver.org/23261.html</link>
		<guid>http://tc.eserver.org/23261.html</guid>
		<description>The authors describe an experiment to see if large breadth and decreased depth is preferable, both subjectively and via performance data, while attempting to design for optimal scent throughout different structures of a web site. This work is testing the theories of Miller in his classic &apos;The Magical Number Seven, Plus or Minus Two.&apos;</description>
	</item>
	<item>
		<title>Findability</title>
		<link>http://tc.eserver.org/23034.html</link>
		<guid>http://tc.eserver.org/23034.html</guid>
		<description>Findability refers to the quality of being locatable or navigable. At the item level, we can evaluate to what degree a particular object is easy to discover or locate. At the system level, we can analyze how well a physical or digital environment supports navigation and retrieval.&#xD;&#xD;This website is a selective, seriously incomplete, and perpetually evolving collection of links to people, software, organizations, and content related to findability.</description>
	</item>
	<item>
		<title>Information, Architecture, and Usability</title>
		<link>http://tc.eserver.org/23053.html</link>
		<guid>http://tc.eserver.org/23053.html</guid>
		<description>What is the relationship between information architecture design and usability engineering? This is a loaded question, and I wade into dangerous waters by addressing it, but the answer has significant implications for a variety of audiences.</description>
	</item>
	<item>
		<title>Cadius</title>
		<link>http://tc.eserver.org/22810.html</link>
		<guid>http://tc.eserver.org/22810.html</guid>
		<description>Cadius es una iniciativa al servicio de la comunidad de profesionales de la Arquitectura de Información y la Usabilidad.</description>
	</item>
	<item>
		<title>Information Specialists at the Intersection of Information Architecture and Usability</title>
		<link>http://tc.eserver.org/22672.html</link>
		<guid>http://tc.eserver.org/22672.html</guid>
		<description>Discusses the intersection of information architecture (IA) and usability.</description>
	</item>
	<item>
		<title>Get ROI from Design</title>
		<link>http://tc.eserver.org/21886.html</link>
		<guid>http://tc.eserver.org/21886.html</guid>
		<description>Explains that specific, measurable objectives and post-launch measurements are crucial for successfully achieving ROI (return on investment) goals. He also provides several examples aligning business and design initiatives, and prioritizing design projects relative to their ROI.</description>
	</item>
	<item>
		<title>Papers and Presentations from STC India Learning Sessions</title>
		<link>http://tc.eserver.org/21689.html</link>
		<guid>http://tc.eserver.org/21689.html</guid>
		<description>View and download papers presented at STC India&apos;s learning sessions.</description>
	</item>
	<item>
		<title>What an Information Architect Should Know About Prototypes for User Testing</title>
		<link>http://tc.eserver.org/21362.html</link>
		<guid>http://tc.eserver.org/21362.html</guid>
		<description>There are several important factors to consider when you are planning to do prototyping for user testing. You will want to make careful choices about fidelity, level of interactivity and the medium of your prototype. Chris Farnum offers descriptions and best use scenarios to help you make the best prototype decision for your tests.</description>
	</item>
	<item>
		<title>What&apos;s In A Name?</title>
		<link>http://tc.eserver.org/20927.html</link>
		<guid>http://tc.eserver.org/20927.html</guid>
		<description>In defining a field, each person seems to look at the world and place themselves in the center of the circle, giving their specialty top billing as the summation of all the others. What exactly is gained by this political one-upmanship? In the face of this inflation, I find myself pulling back to the simplest craft title I can find. Or avoiding titles altogether.</description>
	</item>
	<item>
		<title>Website Navigation is Useful</title>
		<link>http://tc.eserver.org/20870.html</link>
		<guid>http://tc.eserver.org/20870.html</guid>
		<description>Although users tend to navigate websites by search mechanisms or by links embedded in actual content, website navigation serves useful purposes.</description>
	</item>
	<item>
		<title>Information Engineering for the 21st Century</title>
		<link>http://tc.eserver.org/20543.html</link>
		<guid>http://tc.eserver.org/20543.html</guid>
		<description>Bowie urges technical communicators to spend less time creating documentation and more time designing products that people can use intuitively.</description>
	</item>
	<item>
		<title>Navigation: An Often Neglected Component of Web Authorship</title>
		<link>http://tc.eserver.org/19619.html</link>
		<guid>http://tc.eserver.org/19619.html</guid>
		<description>Web authors should follow web design conventions that account for the variety of ways users will try to navigate through their pages. While usability testing is the best way to ensure your site is really operating as you intend it to, this page offers a basic overview of basic navigation principles that most visitors will expect on most pages that they visit.</description>
	</item>
	<item>
		<title>Information Architecture Meets Usability</title>
		<link>http://tc.eserver.org/19437.html</link>
		<guid>http://tc.eserver.org/19437.html</guid>
		<description>A discussion of the common pitfalls of web usability and information architecture, and the state of the web industry today.</description>
	</item>
	<item>
		<title>Web Navigation: Resolving Conflicts between the Desktop and the Web</title>
		<link>http://tc.eserver.org/19339.html</link>
		<guid>http://tc.eserver.org/19339.html</guid>
		<description>This paper summarizes a workshop at CHI98 that focused on navigational problems caused by differences in navigational models between the desktop and the Web. The goal of this workshop was to identify usability problems encountered when users move from the &apos;traditional&apos; desktop to the Web and to identify ways to minimize transfer-learning problems between the two platforms.Workshop papers will soon be available online.</description>
	</item>
	<item>
		<title>How the Process and Organization Can Help or Hinder Adding Value</title>
		<link>http://tc.eserver.org/19126.html</link>
		<guid>http://tc.eserver.org/19126.html</guid>
		<description>Do better information products result when technical communicators are well integrated into product development teams?</description>
	</item>
	<item>
		<title>Navigating Isn&apos;t Fun</title>
		<link>http://tc.eserver.org/18661.html</link>
		<guid>http://tc.eserver.org/18661.html</guid>
		<description>The artless Websites created during the Web&apos;s infancy were of necessity built only with simple HTML tags, and were forced to divide up their functionality and content into a maze (a web?) of separate pages. This made a navigation scheme an unavoidable component of any Website design, and of course, a clear, visually arresting navigation scheme was better than an obscure or hidden one. But many Web designers have incorrectly deduced from this that users want navigation schemes. Actually, they&apos;d be happy if there were no navigation at all.</description>
	</item>
	<item>
		<title>Personas: Matching a Design to the Users&apos; Goals</title>
		<link>http://tc.eserver.org/14210.html</link>
		<guid>http://tc.eserver.org/14210.html</guid>
		<description>We hear all the time from designers that they&apos;re faced with the huge challenge of designing products and web sites for a large number of different users. Many designers tackle this problem by making the functionality of the web site or product as extensive as possible. To do this, they outline all of the goals of each user, identify any commonalities between these goals, and add all of the functionality needed to satisfy these common goals.</description>
	</item>
	<item>
		<title>The Psychology of Menu Selection: Designing Cognitive Control at the Human/Computer Interface</title>
		<link>http://tc.eserver.org/14153.html</link>
		<guid>http://tc.eserver.org/14153.html</guid>
		<description>Menu selection is emerging as an important mode of human/computer interaction. This book, the first entirely devoted to this important form of human/computer interaction, provides detailed theoretical and empirical information of interest to software designers and human/computer interaction specialists and researchers. A new theoretical approach to menu selection is taken by developing a psychological theory of cognitive control by the user. A comprehensive review of empirical research on menu selection is presented in an organized fashion to aid in the design and evaluation of systems. Finally, information is given on how to protype and evaluate menu selection systems using both performance data and user ratings.</description>
	</item>
	<item>
		<title>An Audience With Alan Cooper: Defining Interaction Design</title>
		<link>http://tc.eserver.org/13905.html</link>
		<guid>http://tc.eserver.org/13905.html</guid>
		<description>What was intended to be an Interview immediately became an audience with the master. It became difficult to slide in the questions as Cooper began to tear up the rulebook for the technology industry and throw it out. He discusses why Interaction Design is about complete systems architecture and he hits on what&apos;s wrong with relational databases; what&apos;s wrong with file systems; why Interaction Design is a lot more than Interface Design; and why he really doesn&apos;t like Usability much either.</description>
	</item>
	<item>
		<title>The Age of Information Architecture</title>
		<link>http://tc.eserver.org/13658.html</link>
		<guid>http://tc.eserver.org/13658.html</guid>
		<description>For the most part, information architects are communicators and strategists. While others merely tolerated the mishmash of responsibilities, they relished it. Designers often put up with having to write HTML but jumped at the chance to &apos;just do design.&apos; Programmers were forced to meet with clients and work on strategy, but all along probably wanted to just write code. When these two ends of the spectrum split off, the empty middle was a perfect place to be. At the same time, there was an increased (but still hidden) need for information architecture. As the average web project process matured, more problems arose. Formal documentation was needed, business objectives were taking on increased importance, and, as the size increased exponentially, information organization became a much more important role. (The fact that this evolution took place during the &apos;dot.com fallout&apos; is not insignificant, as this led to the placement of web projects under the same microscope as other business endeavors.) Some of these positions could be filled by existing disciplines; project managers, business analysts, and usability specialists transitioned from &apos;traditional&apos; work and were added to web teams. Still, there was something missing. The connection between &apos;the big picture&apos; (business strategy, high-level user tasks, basic structural architecture) and the nitty-gritty (categorization, labeling, bottom-up information hierarchies) often wasn&apos;t being made. This is where information architects fit in.</description>
	</item>
	<item>
		<title>Designing Web Ads Using Click-Through Data</title>
		<link>http://tc.eserver.org/13357.html</link>
		<guid>http://tc.eserver.org/13357.html</guid>
		<description>Search engine ads are one type of Web advertising that can actually work. To create the best ads, do quick experiments and redesign ads based on usability principles for online writing. Doing so helped us increase ad click-through by 55 to 310 percent.</description>
	</item>
	<item>
		<title>On Beyond Help: Meeting User Needs for Useful Online Information</title>
		<link>http://tc.eserver.org/10429.html</link>
		<guid>http://tc.eserver.org/10429.html</guid>
		<description>It is well accepted that understanding the users and a thorough analysis of their goals and tasks is a prerequisite for usability. To produce a document, online information, or knowledge base that is truly usable, the designer and writer must also consider different user approaches to the information to create it in a form that meets those needs. The underlying technology must also be considered, as it affects the presentation of the information as well as the functionality available to users. To meet user needs for useful online information, all these elements must be factored into the design—and technical communicators must master the skills necessary to make the right choices. </description>
	</item>
	<item>
		<title>A Study of the Effectiveness of Information Design Principles Applied to Clinical Research Questionnaires</title>
		<link>http://tc.eserver.org/10399.html</link>
		<guid>http://tc.eserver.org/10399.html</guid>
		<description>This study investigates the effectiveness of information design principles and feedback-based usability testing in the development of clinical questionnaires, with the goal of increasing the amount of data collected in the Breast Cancer Lymphatic Mapping Database at the H. Lee Moffitt Cancer Center and Research Institute. It finds that although both the Control and Study forms were generated using the same form design software, the Study form developed using information design principles collected significantly more data than the Control form developed by a systems analyst. The article observes that information designers face conflicts between the needs of users, general information design guidelines, constraints of the software, and misunderstandings by medical researchers and health professionals over the role of information designers. </description>
	</item>
	<item>
		<title>Learning from Games: Seven Principles of Effective Design</title>
		<link>http://tc.eserver.org/10352.html</link>
		<guid>http://tc.eserver.org/10352.html</guid>
		<description>Why do players of computer games seem to approach those applications without fear, eagerly exploring and learning as they go, while users of business applications will go out of their way to keep from using the tools? Why do business applications require volumes of documentation when the most complex games come with a brief tutorial and a strategy guide for exploration? Why can games teach pilots to fly multi-million-dollar jets better than books and classroom training? These questions have led us to ask another question: Why can’t business applications be more like games? In this article, we attempt to lay the ground work for future research by defining seven design principles found in games that we believe contribute to the creation of more usable applications. </description>
	</item>
	<item>
		<title>Designing for Advanced Users</title>
		<link>http://tc.eserver.org/10286.html</link>
		<guid>http://tc.eserver.org/10286.html</guid>
		<description>Much discussion in web usability in recent years has revolved around designing web sites which are intended to be easily accessible by even the least technologically advanced user. This attempt to attract the highest number of visitors is especially appropriate for promoting and selling goods and services. The inexperienced user unaccustomed to reading text displayed on monitors and unable to efficiently download multimedia files should not be alienated by highly detailed or stylized web writing or a lack of bandwidth. Yet, there are more-advanced users on the web that designers should consider when appropriate.</description>
	</item>
	<item>
		<title>Modeling Information for Three-Dimensional Space: Lessons Learned from Museum Exhibit Design</title>
		<link>http://tc.eserver.org/10262.html</link>
		<guid>http://tc.eserver.org/10262.html</guid>
		<description>Perhaps these concerns sound familiar: visitors complain that they cannot find information of interest. One observes, &apos;I know there&apos;s information about that type of robotics here, but darned if I can find it;&apos; visitors enter the site but don&apos;t stay particularly long. Some might even express an interest in the subject; let&apos;s say it&apos;s modern art. But they leave almost as quickly as they enter without paying much attention to the artwork that the designers painstakingly displayed; other visitors spend hours at the site but never seem to notice particular sections. For example, a visitor might be thoroughly familiar with the content on radios but oblivious to the section on industrial hardware. These observations could describe visitors to Web sites. Actually, these observations describe museum visitors. The connections between the two are discussed in this article.</description>
	</item>
	<item>
		<title>Prioritize: Good Content Bubbles to the Top</title>
		<link>http://tc.eserver.org/10257.html</link>
		<guid>http://tc.eserver.org/10257.html</guid>
		<description>If everything is equally prominent, then nothing is prominent. It is the job of the designer to advise the user and guide them to the most important or most promising choices (while ensuring their freedom to go anywhere they please). On today&apos;s Web, the most common mistake is to make everything too prominent: over-use of colors, animation, blinking, and graphics. Every element of the page screams &apos;look at me&apos; (while all the other design elements scream &apos;no, look at me&apos;). When everything is emphasized, nothing is emphasized.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Design/Information-Design/Usability.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>