http://tc.eserver.org/dir/Presentations/User-Centered-Design/Usability A listing of the most recently indexed works about Presentations and User Centered Design and Usability in the field of technical communication. en-us Copyright (c) 2005-08 by the EServer. All rights reserved. tclib-editorial@eserver.org (TC Library Editorial Board) webmaster@eserver.org (Geoffrey Sauer) http://tc.eserver.org/images/newlogo.gif http://tc.eserver.org/dir/Presentations/User-Centered-Design/Usability http://tc.eserver.org/28824.html http://tc.eserver.org/28824.html How do you review a product for usability, but make that review user-centered? http://tc.eserver.org/28809.html http://tc.eserver.org/28809.html What are hazards and why do we need them? Best practices for key elements of hazards. http://tc.eserver.org/28797.html http://tc.eserver.org/28797.html In this podcast, Karen Bachmann, manager of the Usability and User Experience SIG, provides an overview of the user-centered design process. This is part one of a two part series. http://tc.eserver.org/27387.html http://tc.eserver.org/27387.html Discusses how Anthem attained the training, standards, and resources they needed to create a sustained usability effort. http://tc.eserver.org/18226.html http://tc.eserver.org/18226.html The need for user-centered design in this era of rapid technological change is reviewed, and key ingredients of a user-centered design process are described: (1) involvement of users, structured by rigorous user input and feedback methodologies, (2) multidisciplinary teamwork, from developing the initial concepts and approach to evaluating and refining the product after its introduction in the marketplace, and (3) focus on competitiveness, on state-of-theart user interfaces and technology. Data supporting the economic value of user-centered design processes is also reviewed. http://tc.eserver.org/14519.html http://tc.eserver.org/14519.html Testing documents for usability is critical, but we don’t always get to do it. Even when we do, too often, it’s too little, too late. What we really want are documents that we are fine-tuning in usability testing because they already meet users’ needs, match our users’ mental models, and fit with the way that our users work. http://tc.eserver.org/14343.html http://tc.eserver.org/14343.html The success of an organization that publishes product information depends on customer satisfaction. IBM Product Announcement Support representatives share their experiences in achieving very high levels of customer satisfaction. * How we conducted our surveys and feedback sessions: – Actual approaches – Sample surveys and feedback * How we used this feedback to: – Change the content and format of our deliverable dramatically – Offer our customers additional ways to access product information As writers in IBM Product Announcement Support, our mission is to produce high-quality, effective offering information worldwide. Simply put, we publish IBM product announcements on the full range of IBM hardware, software, and services. http://tc.eserver.org/14346.html http://tc.eserver.org/14346.html Prototyping has long been a part of the sofiware development process, but is still an underutilized aspect of documentation design, particularly for online design. Developing a detailed approach to prototyping lets writers design and confirm document usability early in the development cycle. Implementing detailed prototyping in an iterative design cycle ultimately leads to the best possible document for the audience. http://tc.eserver.org/13940.html http://tc.eserver.org/13940.html People have a limited amount of cognitive resources. Coping with the increasing amount of information presented via a software interface strains a user’s cognitive resources. If a person has to use documentation, whether on-line or paper, additional cognitive resources are consumed, often overloading the user. Using several windows or multi-media elements can compound the problem. Unfortunately, as Wickens (1992) states, humans are unable to manage excessive cognitive strain and they respond by getting frustrated, committing errors, shedding tasks, or reverting to known methods. http://tc.eserver.org/13939.html http://tc.eserver.org/13939.html The conventional techniques for task analysis derive the basic tasks that make up user actions. However, in the complex-problem solving environment, attempts to describe step-by-step actions break down because no single route to a solution exists. Although individual tasks can be defined, task-analysis normally results in the tasks being divorced from context. However, to support complex problem-solving, the design must place the information within the situation context and allow users to develop and maintain situation awareness. http://tc.eserver.org/13945.html http://tc.eserver.org/13945.html Design of information used for technical communication of complex products should consider how learnable that information is, and strive to deliver materials that are inherently learnable.The speed of information interchange and the demands of the workplace and school curricula require increasingly minimalist approaches to the material that is made available. People are frustrated by long learning times, and new users of software tools demand rapid absorption of tool capabilities. In addition, many readers of technical information are people for whom English is not their native language.Methods and practices that worked in the period when people were willing to commit to hours of study to understand a topic, or days of practice to master a tool, no longer work in a world based on ?internet time.? To assist our understanding of these trends in learning, this paper addresses three key areas related to learnability: proposing a definition of learnability, showing where learnability and usability intersect, and providing a basis for learnability based on some attributes of human beings. http://tc.eserver.org/13101.html http://tc.eserver.org/13101.html In the discipline of software and information development, minimalist design is not just doing with less (less features, words, widgets). It is selectively choosing what to include or eliminate with the purpose of making it easier for the user to quickly learn about a product in a natural and painless way and to start using it to do real work. User centered design fits well with minimalist theory because it incorporates user feedback throughout the development cycle. It is the best way to find out what customers actually do with your product and learn first-hand how you can help them with their goals. My team applied both these theories to our task of designing and building a set of samples for a Web development product. This paper shares our struggles and successes.