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 'just do design.' 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 'dot.com fallout' 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 'traditional' work and were added to web teams. Still, there was something missing. The connection between 'the big picture' (business strategy, high-level user tasks, basic structural architecture) and the nitty-gritty (categorization, labeling, bottom-up information hierarchies) often wasn't being made. This is where information architects fit in.
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.
Card sorting is a way to involve users in grouping information for a Web site. Participants in a card sorting session are asked to organize the content from your Web site in a way that makes sense to them. Participants review items from your Web site and then group these items into categories. Participants may even help you label these groups. Card sorting helps you build the structure for your Web site, decide what to put on the home page, and label the home page categories. It also helps to ensure that you organize information on your site in a way that is logical to your users.
The words 'click here for...' and 'click here to...' serve no purpose within links. Unfortunately, many news sites still use them. According to Google, 'click here' is on about 8,970 pages at sptimes.com alone.
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.
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'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.
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.
Information, once rare and valuable, is now as plentiful as it is meaningless. The constant accessibility rendered by various 'networking' 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.
Most people who create site structures are not trained practitioners of information architecture. Our natural human capacity to organize and relate things gives many people who aren’t IA professionals basic, but useful site structuring skills. But don’t be fooled. Creating and maintaining a site structure can be highly complex. Since complexity tends to increase in an active domain, know when to call in an expert such as an information architect.
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.
Endless scrolling saves people from having to attend to the mechanics of pagination in browsing tasks, but is not a good choice for websites that support goal-oriented finding tasks.
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.
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.
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.
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.
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.
As web professionals, we all know that the concept of the page fold being an impenetrable barrier for users is a myth. Over the last 6 years we’ve watched over 800 user testing sessions between us and on only 3 occasions have we seen the page fold as a barrier to users getting to the content they want. In this article we’re going to break down the page fold myth and give some tips to ensure content below the fold gets seen.
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.
Peter Morville and Jeffery Callendar, two information architects, call faceted navigation “arguably the most significant search innovation of the past decade.” Because of its importance in content findability, one aspect I want to now explore further is a second-level faceted browsing system.
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.