- Paperback: 288 pages
- Publisher: Sams - Pearson Education; 1 edition (March 5, 2004)
- Language: English
- ISBN-10: 0672326140
- ISBN-13: 978-0672326141
- Product Dimensions: 6.1 x 0.7 x 9.1 inches
- Shipping Weight: 9.9 ounces (View shipping rates and policies)
- Average Customer Review: 191 customer reviews
- Amazon Best Sellers Rank: #54,350 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
The Inmates Are Running the Asylum: Why High Tech Products Drive Us Crazy and How to Restore the Sanity 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
The Amazon Book Review
Author interviews, book reviews, editors picks, and more. Read it now
Frequently bought together
Customers who bought this item also bought
The recurring metaphor in The Inmates are Running the Asylum is that of the dancing bear--the circus bear that shuffles clumsily for the amusement of the audience. Such bears, says author Alan Cooper, don't dance well, as everyone at the circus can see. What amazes the crowd is that the bear dances at all. Cooper argues that technology (videocassette recorders, car alarms, most software applications for personal computers) consists largely of dancing bears--pieces that work, but not at all well. He goes on to say that this is more often than not the fault of poorly designed user interfaces, and he makes a good argument that way too many devices (perhaps as a result of the designers' subconscious wish to bully the people who tormented them as children) ask too much of their users. Too many systems (like the famous unprogrammable VCR) make their users feel stupid when they can't get the job done.
Cooper, who designed Visual Basic (the programming environment Microsoft promotes for the purpose of creating good user interfaces), indulges in too much name-dropping and self-congratulation (Cooper attributes the quote, "How did you do that?" to Microsoft chairman Bill Gates, upon looking at one of Cooper's creations)--but this appears to be de rigueur in books about the software industry. But those asides are minor. More valuable is the discourse about software design and implementation ("[O]bject orientation divides the 1000-brick tower into 10 100-brick towers."). Read this book for an idea of what's wrong with UI design. --David Wall
Topics covered: User interfaces--good ones and bad ones--and where they come from. Also, how to improve the ones you create.
From the Back Cover
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.
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
These shortcomings are not solved by adding a layer of another design person partially disconnected from the user, or making the screen prettier. It is by adapting the Extreme Programming/Agile programming methods of including the user in everything from design to testing, so the software reflects how the user does business.
I still liked the book, just not clear on the message.
Somewhere along the line, Cooper switches gears from talking about the problems of software to talking about the problems of people. This is a logical step, but Cooper proceeds to advocate a strict hierarchy where programmers are isolated from the big picture because they, frankly, think like computers and are therefore potentially hazardous to users.
This would make sense if we lived in a world where you can assume all black people are lazy because you saw one sleeping in a hammock. Cooper's generalizations stretch to the point where he claims a developer cannot be a good designer because of the way they think. Speaking as both a designer and developer, Cooper is simply wrong about this.
What makes Cooper's book forgettable is that he is not advocating for better technology through educating the public. Rather, he is advocating better technology by pushing social roles onto people with preconceived overgeneralizations of how people think. Cooper would say to you "You are the kind of person that should... [BLANK]"
The title of my review sums up the categories of people Cooper makes up. Interaction designers and business people are good because they care about the end users, who are clueless to what the bad ol' developers are trying to do to them. While Cooper's dream for better products is noble and just, he feels that the ends justify the means.
The problems in Cooper's book are not products of developers running the world (as he insinuates), it's about communication. Managing developers and communicating user needs to different departments is a difficult, context-centric task with no set formula.
But Cooper offers a formula for how people should behave, and that is why I can't take him seriously.
Hear, hear -- but good luck. As long as software companies continue to be profitable with programmers doing interaction design, it's not likely to stop.
Unfortunately, Cooper limits his book to the business case for interaction design. This omits the action step: how to effect that cultural change within a software company.
I produce software systems and have to work with a lot of other people's software. In many instances, I know DESIGN WAS NOT PART OF THE DEVELOPMENT CYCLE.
This is a keeper!