You are previewing Inmates Are Running the Asylum, The: Why High-Tech Products Drive Us Crazy and How to Restore the Sanity.
O'Reilly logo
Inmates Are Running the Asylum, The: Why High-Tech Products Drive Us Crazy and How to Restore the Sanity

Book Description

Imagine, at a terrifyingly aggressive rate, everything you regularly use is being equipped with computer technology. Think about your phone, cameras, cars-everything-being automated and programmed by people who in their rush to accept the many benefits of the silicon chip, have abdicated their responsibility to make these products easy to use. The Inmates Are Running the Asylum argues that the business executives who make the decisions to develop these products are not the ones in control of the technology used to create them. Insightful and entertaining, The Inmates Are Running the Asylum uses the author's experiences in corporate America to illustrate how talented people continuously design bad software-based products and why we need technology to work the way average people think. Somewhere out there is a happy medium that makes these types of products both user and bottom-line friendly; this book discusses why we need to quickly find that medium.

Table of Contents

  1. Copyright
    1. Dedication
  2. Acknowledgments
  3. Introduction
  4. Foreword to the Original Edition
    1. The Business-Case Book
    2. Business-Savvy Technologist/Technology-Savvy Businessperson
  5. Foreword
  6. I. Computer Obliteracy
    1. 1. Riddles for the Information Age
      1. What Do You Get When You Cross a Computer with an Airplane?
      2. What Do You Get When You Cross a Computer with a Camera?
      3. What Do You Get When You Cross a Computer with an Alarm Clock?
      4. What Do You Get When You Cross a Computer with a Car?
      5. What Do You Get When You Cross a Computer with a Bank?
      6. Computers Make It Easy to Get into Trouble
      7. Commercial Software Suffers, Too
      8. What Do You Get When You Cross a Computer with a Warship?
      9. Techno-Rage
      10. An Industry in Denial
      11. The Origins of This Book
    2. 2. Cognitive Friction
      1. Behavior Unconnected to Physical Forces
      2. Design Is a Big Word
      3. The Relationship Between Programmers and Designers
      4. Most Software Is Designed by Accident
      5. “Interaction” Versus “Interface” Design
      6. Why Software-Based Products Are Different
      7. The Dancing Bear
      8. The Cost of Features
      9. Apologists and Survivors
      10. How We React to Cognitive Friction
      11. The Democratization of Consumer Power
      12. Blaming the User
      13. Software Apartheid
  7. II. It Costs You Big Time
    1. 3. Wasting Money
      1. Deadline Management
      2. What Does “Done” Look Like?
        1. Parkinson's Law
        2. The Product That Never Ships
      3. Shipping Late Doesn't Hurt
      4. Feature-List Bargaining
        1. Programmers Are in Control
      5. Features Are Not Necessarily Good
      6. Iteration and the Myth of the Unpredictable Market
      7. The Hidden Costs of Bad Software
        1. The Only Thing More Expensive Than Writing Software Is Writing Bad Software
        2. Opportunity Cost
      8. The Cost of Prototyping
    2. 4. The Dancing Bear
      1. If It Were a Problem, Wouldn't It Have Been Solved by Now?
      2. Consumer Electronics Victim
      3. How Email Programs Fail
      4. How Scheduling Programs Fail
      5. How Calendar Software Fails
      6. Mass Web Hysteria
      7. What's Wrong with Software?
        1. Software Forgets
        2. Software Is Lazy
        3. Software Is Parsimonious with Information
        4. Software Is Inflexible
        5. Software Blames Users
        6. Software Won't Take Responsibility
    3. 5. Customer Disloyalty
      1. Desirability
      2. A Comparison
      3. Time to Market
  8. III. Eating Soup with a Fork
    1. 6. The Inmates Are Running the Asylum
      1. Driving from the Backseat
      2. Hatching a Catastrophe
      3. Computers Versus Humans
      4. Teaching Dogs to Be Cats
    2. 7. Homo Logicus
      1. The Jetway Test
      2. The Psychology of Computer Programmers
      3. Programmers Trade Simplicity for Control
      4. Programmers Exchange Success for Understanding
      5. Programmers Focus on What Is Possible to the Exclusion of What Is Probable
      6. Programmers Act Like Jocks
    3. 8. An Obsolete Culture
      1. The Culture of Programming
      2. Reusing Code
      3. The Common Culture
        1. Programming Culture at Microsoft
      4. Cultural Isolation
      5. Skin in the Game
        1. Scarcity Thinking
      6. The Process Is Dehumanizing, Not the Technology
  9. IV. Interaction Design Is Good Business
    1. 9. Designing for Pleasure
      1. Personas
      2. Design for Just One Person
        1. The Roll-Aboard Suitcase and Sticky Notes
      3. The Elastic User
      4. Be Specific
      5. Hypothetical
      6. Precision, Not Accuracy
      7. A Realistic Look at Skill Levels
      8. Personas End Feature Debates
        1. Both Designers and Programmers Need Personas
      9. It's a User Persona, Not a Buyer Persona
      10. The Cast of Characters
      11. Primary Personas
      12. Case Study: Sony Trans Com's P@ssport
        1. The Conventional Solution
        2. Personas
        3. Designing for Clevis
    2. 10. Designing for Power
      1. Goals Are the Reason Why We Perform Tasks
      2. Tasks Are Not Goals
        1. Programmers Do Task-Directed Design
      3. Goal-Directed Design
        1. Goal-Directed Television News
        2. Goal-Directed Classroom Management
      4. Personal and Practical Goals
        1. The Principle of Commensurate Effort
      5. Personal Goals
      6. Corporate Goals
      7. Practical Goals
      8. False Goals
      9. Computers Are Human, Too
      10. Designing for Politeness
        1. What Is Polite?
      11. What Makes Software Polite?
        1. Polite Software Is Interested in Me
        2. Polite Software Is Deferential to Me
        3. Polite Software Is Forthcoming
        4. Polite Software Has Common Sense
        5. Polite Software Anticipates My Needs
        6. Polite Software Is Responsive
        7. Polite Software Is Taciturn About Its Personal Problems
        8. Polite Software Is Well Informed
        9. Polite Software Is Perceptive
        10. Polite Software Is Self-Confident
        11. Polite Software Stays Focused
        12. Polite Software Is Fudgable
        13. Polite Software Gives Instant Gratification
        14. Polite Software Is Trustworthy
      12. Case Study: Elemental Drumbeat
        1. The Investigation
        2. Who Serves Whom
        3. The Design
        4. Pushback
        5. Other Issues
    3. 11. Designing for People
      1. Scenarios
      2. Daily-Use Scenarios
      3. Necessary-Use Scenarios
      4. Edge-Case Scenario
      5. Inflecting the Interface
      6. Perpetual Intermediates
        1. “Pretend It's Magic”
      7. Vocabulary
        1. Breaking Through with Language
      8. Reality Bats Last
      9. Case Study: Logitech ScanMan
        1. Malcolm, the Web-Warrior
        2. Chad Marchetti, Boy
        3. Magnum, DPI
        4. Playing “Pretend It's Magic”
        5. World-Class Cropping
        6. World-Class Image Resize
        7. World-Class Image Reorient
        8. World-Class Results
      10. Bridging Hardware and Software
      11. Less Is More
  10. V. Getting Back into the Driver's Seat
    1. 12. Desperately Seeking Usability
      1. The Timing
      2. User Testing
        1. User Testing Before Programming
        2. Fitting Usability Testing into the Process
      3. Multidisciplinary Teams
      4. Programmers Designing
      5. How Do You Know?
      6. Style Guides
        1. Conflict of Interest
      7. Focus Groups
      8. Visual Design
      9. Industrial Design
      10. Cool New Technology
      11. Iteration
    2. 13. A Managed Process
      1. Who Really Has the Most Influence?
        1. The Customer-Driven Death Spiral
        2. Conceptual Integrity Is a Core Competence
        3. A Faustian Bargain
        4. Taking a Longer View
        5. Taking Responsibility
        6. Taking Time
        7. Taking Control
      2. Finding Bedrock
        1. Knowing Where to Cut
      3. Making Movies
      4. The Deal
        1. Document Design to Get It Built
        2. Design Affects the Code
        3. Design Documents Benefit Programmers
        4. Design Documents Benefit Marketing
        5. Design Documents Help Documenters and Tech Support
        6. Design Documents Help Managers
        7. Design Documents Benefit the Whole Company
      5. Who Owns Product Quality?
      6. Creating a Design-Friendly Process
        1. Where Interaction Designers Come From
        2. Building Design Teams
    3. 14. Power and Pleasure
      1. An Example of a Well-Run Project
      2. A Companywide Awareness of Design
      3. Benefits of Change
      4. Let Them Eat Cake
        1. Changing the Process
  11. Alan Cooper