Utiliser les 5 E pour Comprendre les Utilisateurs
En matière d'amélioration de votre site web, produit ou logiciel, comment passer de la simple volonté à l'action? Que dites-vous de ceci pour commencer: si la réponse c'est l'utilisabilité, quelle peut bien être la question?
Quesenbery, Whitney. WQusability. (French) Articles>Usability>Methods
Virtual Communities: Weaving the Human Web 
Muses on the increasing importance of communities in the technical communication profession.
Quesenbery, Whitney. Intercom (2005). Articles>TC>Community Building>Social Networking
Voters Learn the Importance of Usability
It has been an exciting few months, what with the usability flaws in the 'butterfly ballot' in Florida possibly changing the course of history. The good news is that the controversy put usability into the public conversation with news articles, press releases, and even new research articles. It was an opportunity to explain 'what we do' to friends, relatives, and associates. Some of the lessons from the 2000 Presidential election are the basics of Usability 101.
Quesenbery, Whitney. Usability Interface (2001). Articles>Documentation>Help>Usability
Voting and Usability Project Update
It's been two-and-a-half years since we started the Voting and Usability Project. This project started as we all realized with some horror that usability problems in our voting systems could affect the results of an election--effectively disenfranching some voters through the design of the ballot, as Susan King Roth put it in the report on her research. Since then, our interest has expanded into a more general interest in the usability of voting systems and usability professionals can help make voting systems more usable for everyone.
Quesenbery, Whitney. Usability Professionals Association (2003). Articles>Usability>User Interface>Civic
It might be easy to dismiss the WAI as another mouthful of acronyms for yet another Web standard but that would be a mistake. Their goal is to, '…make Web content more available to all users, whatever user agent they are using (e.g., desktop browser, voice browser, mobile phone, automobile-based personal computer, etc.) or constraints they may be operating under (e.g., noisy surroundings, under- or over-illuminated rooms, in a hands-free environment, etc.).'
Quesenbery, Whitney. Usability Interface (1999). Articles>Web Design
Web Accessibility Initiative (WAI)
It might be easy to dismiss the WAI as another mouthful of acronyms for yet another Web standard but that would be a mistake. Their goal is to, '…make Web content more available to all users, whatever user agent they are using (e.g., desktop browser, voice browser, mobile phone, automobile-based personal computer, etc.) or constraints they may be operating under (e.g., noisy surroundings, under- or over-illuminated rooms, in a hands-free environment, etc.).' To meet this goal, the WAI identifies two primary principles for accessible design, which are totally in keeping with the basic principles of usability: 'Ensure graceful transformation' and 'Make content understandable and navigable.' There are fourteen guidelines that help authors understand and implement these principles. Each includes a description and rationale, along with links to other resources and a set of checkpoints. A related document shows detailed techniques for implementing accessible web pages. Even if you are not primarily concerned wi
Quesenbery, Whitney. STC Usability SIG (1999). Design>Accessibility
What Does Usability Mean: Looking Beyond ‘Ease of Use’ 
The definition of usability is sometimes reduced to 'easy to use,' but this over-simplifies the problem and provides little guidance for the user interface designer. A more precise definition can be used to understand user requirements, formulate usability goals and decide on the best techniques for usability evaluations. An understanding of the five characteristics of usability – effective, efficient, engaging, error tolerant, easy to learn – helps guide the user-centered design tasks to the goal of usable products.
Quesenbery, Whitney. STC Proceedings (2001). Articles>Usability>User Centered Design
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
When the Show Must Go On, It's Time to Collaborate Or Die
Lighting design has a utilitarian role: to put enough light on the stage so that the audience can see the actors. But the lighting also helps shape the performance by providing the color and overtones that add meaning and layers and depth. The same mix of art and technology, craft and discipline exists in user interface design.
Quesenbery, Whitney. Boxes and Arrows (2002). Design>Web Design>Collaboration
When the Show Must Go On, It’s Time to Collaborate Or Die
No one knew what to do. But there was a deadline, and the reviewers were coming. As a team, we walked through the schedule again and again until we had a plan. The next day, the video was edited, the shop finished the screens, and the production crew walked through the critical paths.
Quesenbery, Whitney. Boxes and Arrows (2002). Articles>Collaboration>Usability
Whitney Quesenbery on the Five E's of Usability
Quesenbery is one of the authors of Content and Complexity: Information Design in Technical Communication. Quesenbery explains the five E's -- a simple way to talk about product usability. The five E's are efficient, effective, engaging, error-tolerant, and easy to learn. She elaborates on what it means for a product to be engaging/satisfying. Quesenbery also explains the importance of personas, which she has written about in the Personas Lifecycle by Tamara Adline and John Pruit. She says stories are essential to personas.
Quesenbery, Whitney and Tom H. Johnson. Tech Writer Voices (2007). Articles>Interviews>Usability>Podcasts
Who is in Control?: The Logic Underlying the Intelligent Technologies Used in Performance Support

Performance support (also called EPSS, for electronic performance support system) emerged from the instructional design and training communities because corporate enterprise systems were difficult for people to use, and the training needed to make them productive was expensive and time consuming. A good definition is that 'EPSS (Electronic Performance Support Systems) are systems that provide employees with the information, advice and learning experiences they need to get up to speed as quickly as possible and with the minimum of support from other people' (Raybould 1996). One of the issues in designing performance support is managing information overload. Two approaches are the use of agents and the presentation of information in visual form (called information visualization). The former looks for ways that computer programs can do work for users, sorting through data on their behalf; the latter looks for ways to present information so that users can directly access it through direct manipulation. You can do both, but the selection of each has an impact on the interaction style and the degree to which users can directly control the system. It is therefore an issue that any performance support system designer should consider carefully. This is a logical extension of the goal of easy-to-use programs, adding the requirement that the user interface be actively informative and helpful.
Quesenbery, Whitney. Technical Communication Online (2002). Articles>Content Management>Workflow>EPSS
I view a user experience as a conversation between people separated over the distance of time. At one end of that conversation are those who create the product; at the other, the people who use it. In between is the product itself--with a design that either helps or hinders; creates a barrier-free interaction or shouts in an unfamiliar language. Because this conversation does not happen in real time, we are not there to smooth over the rough spots and make sure that we have spoken clearly. Instead, we have to build our understanding of those users into every aspect of the design, by putting people--users--at the center of the design process.
Quesenbery, Whitney. UXmatters (2005). Articles>User Experience>Communication>User Centered Design
Why Technical Communicators and Usability?
Why technical communicators and usability? Both writers and software development managers have asked me that question. In both cases, it springs from a narrow view of communicators as 'just writers.' It is a point of view that fails to see the many activities, from learning the subject matter to organizing the information or creating good document design, that are hidden behind that final task of writing the words.
Quesenbery, Whitney. STC Usability SIG (2000). Articles>TC>Document Design>Usability
你有没有怀疑过你的同事或者客户是否真的理解“可用性”?在我们和同事的在商务、技术和设计讨论中谈论‘可用性’是什么时,经常充斥着一些标准和指导方针替代品。在本文中,我们通过了解可用性的五个维度,我们便能够围绕可用性目标达成一致的看法,并开始以这个可用性的定义为基础,来计划用户中心设计的工作。
Quesenbery, Whitney. uiGarden (2006). (Chinese) Articles>Usability>User Centered Design
Usable Accessibility: Making Web Sites Work Well for People with Disabilities
When people talk about both usability and accessibility, it is often to point out how they differ. Accessibility often gets pigeon-holed as simply making sure there are no barriers to access for screen readers or other assistive technology, without regard to usability, while usability usually targets everyone who uses a site or product, without considering people who have disabilities. In fact, the concept of usability often seems to exclude people with disabilities, as though just access is all they are entitled to. What about creating a good user experience for people with disabilities—going beyond making a Web site merely accessible to make it truly usable for them?
Quesenbery, Whitney. UXmatters (2009). Articles>Web Design>Accessibility>Usability
There are 10 readers currently online: 1 registered user and 9 guests. Register.

![]()
![]()


![]()
![]()
![]()