The Age of Information Architecture

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.

Lash, Jeff. Digital Web Magazine (2002). Articles>Information Design>Usability

Bridging the Gap: From Raw Usability Testing Data to Design Implementation  

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.

Leritz-Higgins, Sarah E. and Catherine J. Yaspo. Intercom (2006). Articles>Usability>Information Design

Considering Product Usability Along with Information Usability  

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.

Grice, Roger A. STC Proceedings (1993). Articles>Usability>Information Design

The Essentials of a Database Quality Process    

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.

Blakeslee, Dorothy M. and John Rumble, Jr. Data Science Journal (2003). Articles>Information Design>Databases>Usability

From Data Drought to Factoid Flood: Reinforcing the Banks of the River of Communication    

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.

Dahm, Rea Etta M. STC Proceedings (1999). Articles>Information Design>Usability

In Search of Salience: A Response-Time and Eye-Movement Analysis of Bookmark Recognition

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.

Poole, Alex. Alex Poole (2005). Articles>Information Design>Usability>Web Browsers

Information, Architecture, and Usability

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.

Morville, Peter. Semantic Studios (1999). Articles>Information Design>Usability

Information Engineering for the 21st Century  

Bowie urges technical communicators to spend less time creating documentation and more time designing products that people can use intuitively.

Bowie, John S. Intercom (2003). Articles>Information Design>User Centered Design>Usability

Information Specialists at the Intersection of Information Architecture and Usability

Discusses the intersection of information architecture (IA) and usability.

Head, Alison J. Florida State University (2001). Articles>Information Design>Usability

Learning from Games: Seven Principles of Effective Design    

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.

Houser, Rob and Scott Deloach. Technical Communication Online (1998). Articles>Usability>Information Design

On Beyond Help: Meeting User Needs for Useful Online Information    

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.

Quesenbery, Whitney. Technical Communication Online (2001). Articles>Usability>Information Design

PDF Link Usability

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.

Lennartz, Sven. Dr. Web (2007). (German) Articles>Usability>Information Design>Adobe Acrobat

PDF Usability: Debate and Reality

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.

Johnson, Duff. Adobe (2006). Articles>Usability>Information Design>Adobe Acrobat

Personas: Matching a Design to the Users' Goals

We hear all the time from designers that they'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.

Perfetti, Christine. User Interface Engineering (2001). Articles>Information Design>Usability

Prioritize: Good Content Bubbles to the Top

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'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 'look at me' (while all the other design elements scream 'no, look at me'). When everything is emphasized, nothing is emphasized.

Nielsen, Jakob. Alertbox (1999). Articles>Usability>Information Design

A Study of the Effectiveness of Information Design Principles Applied to Clinical Research Questionnaires    

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.

Zimmerman, Beverly B. and Jessica R. Schultz. Technical Communication Online (2000). Articles>Information Design>Usability

What an Information Architect Should Know About Prototypes for User Testing

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.

Farnum, Chris. Boxes and Arrows (2002). Articles>Information Design>Usability

What's In A Name?

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.

Quesenbery, Whitney. WQusability (2001). Articles>Information Design>Professionalism>Usability