Designing From Both Sides of the Screen
Table of Contents
THE GOAL
-
Chapter 1 - On Being a Butler
-
Chapter 2 - Don't Impose: Respect Physical Effort
- Treat Clicks as Sacred
- Some Examples
- "Do You Really Mean It?" Pop-Ups
- Remember Where They Put Things
- Remember What They Told You
- Stick with a Mode
-
Chapter 3 - Don't Impose: Respect Mental Effort
- Use Visual Elements Sparingly
- Make Common Tasks Visible; Hide Infrequent Tasks
- Give Feedback; Show Signs of Progress
- Keep Preferences to a Minimum; Give Smart Defaults
- Follow Conventions (Even If They're Not Your Ideal Design)
- Look for "Widgetless Features"
-
Chapter 4 - Be Helpful
- Offer Sufficient Information Early and in Context; Prevent Errors
- Solve Problems; Don't Complain or Pass the Buck
- Be Predictable
- Request and Offer Only Relevant Information; Don't Mislead
- Explain in Plain Language
- Avoid Jargon
- Don't Blame the User
- Indicate the Consequences of Options
- Use Common Sense
THE PROCESS
-
Chapter 5 - Setting Up: Understanding Users' Needs
- The Components of User-Centered Design
- The Role of Hubbub
- Understanding Users' Needs
- Specifying the Functional Requirements
- Prioritizing the Functional Requirements
- Designing the User Interface First
- A View from Engineering
- A Word on Schedules
- Getting into the UI Designer Role
-
Chapter 6 - Structuring the User Interface
- The User Interface Spec
- Start with Tasks
- Map Priorities to Design
- Example: "Reverse Designing" Priorities
- Organize the Tasks into Display Units
- Create a Task Flow Diagram
-
Chapter 7 - Laying Out the User Interface
- Communicating Visually
- Example 1: Focusing on Frequent by Many Features
- Example 2: Following Platform Conventions
- Example 3: Designing for Multiple Platforms
- Example 4: Handling Differences in Platform Conventions
- Providing the Ability to Mute
- Providing Status Information
- Distinguishing Participants' Messages
- Example 5: Removing a Feature
- Walk Through the Tasks
-
Chapter 8 - Architecting with the UI in Mind
- Network Architecture
- UI Drives Architecture
- Architecture Drives UI
- Multiplatform Architecture
- Palm Client Architecture
- The Feature List
- Work in Priority Order
- Estimate a Schedule Based on Detailed Feature Descriptions
- Plan Time to Polish Each Feature
-
Chapter 9 - Initial Development
- Issues Resolved on Engineering Grounds
- Example: Edge Cases Versus Common Cases
- Example: Implementation Effort Versus Usability Value
- Example: Implementation Time Versus Usability Value
- Example: Expediency Versus Ideal User Experience
- Issues Resolved on UI Grounds
- Example: Tedious Work Versus Polish
- Example: More Tedious Work Versus Completeness
- Unanticipated UI Issues and Adjustments
- Example: Designing a Case Not Covered in the UI Spec
- Example: Handling Small Issues as They Arise
- Example: Assessing the Impact of a New Design
- Example: Revising a Design After Implementation
- Hidden UI Implications
- Example: Thinking Through Multiple Scenarios When Fixing a Bug
- Example: Anticipating and Gracefully Handling Any Eventuality
- Unanticipated Requirements
- Example: Collaborating with Management
- Designer Activity
- Quick-and-Dirty Usability Testing
- Changes Based on Development Issues
-
Chapter 10 - Iterative Development: Observing Use
- Using Your Own Technology
- Fixing Ease-of-Use Problems
- Polishing Features
- Changes Based on Our Use
- Observing Others Using Your Technology
- Comparing Usability Testing with Usage Studies
- Running a Usage Study
- Finding Usage Study Participants
- Preparing the Technology
- Installing the Technology
- Collecting and Interpreting the Data
- Changes Based on the Usage Study
- Deciding When You're Done
- The Effect of Iterative Design
-
Chapter 11 - Conclusion
- Example 1: Forum
- Understanding the Task
- Designing the UI
- Running a Usage Study
- Example 2: Shopping Web Site
- Understanding the Task
- Designing the UI
- Doing Usability Testing
- Taking a Step Back
APPENDIXES
INDEX
Copyright Pearson Education and
Created: January 3, 2002
Revised: January 3, 2002
URL: http://webreference.com/authoring/design/usability/bothsides/toc.html
