Product 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.

Product Details

• Amazon Sales Rank: #10707 in Books
• Published on: 2004-03-05
• Original language: English
• Number of items: 1
• Binding: Paperback
• 288 pages

Amazon.com
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.

Download 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, despite appearances, business executives are simply not the ones in control of the high-tech industry. They have inadvertently put programmers and engineers in charge, leading to products and processes that waste money, squander customer loyalty, and erode competitive advantage. Business executives have let the inmates run the asylum! In his book The Inmates Are Running the Asylum Alan Cooper calls for revolution - we need technology to work in the same way average people think - we need to restore the sanity. He offers a provocative, insightful and entertaining explanation of how talented people continuously design bad software-based products. More importantly, he uses his own work with companies big and small to show how to harness those talents to create products that will both thrill their users and grow the bottom line.

From the Back Cover
The Inmates are Running the Asylum argues that, despite appearances, business executives are simply not the ones in control of the high-tech industry. They have inadvertently put programmers and engineers in charge, leading to products and processes that waste huge amounts of money, squander customer loyalty, and erode competitive advantage. They have let the inmates run the asylum. Alan Cooper offers a provocative, insightful and entertaining explanation of how talented people continuously design bad software-based products. More importantly, he uses his own work with companies big and small to show how to harness those talents to create products that will both thrill their users and grow the bottom line.

Customer Reviews

To be taken with a large grain of salt
The Inmates Are Running The Asylum starts off pretty well. It begins with some very good examples of poor design that lead to a bad user experience, as well as just how downright dysfunctional the software development process can be. There is also the beginnings of a thesis on how to solve these problems. From there however, the quality of The Inmates takes a steep nosedive. The deeper into The Inmates you go, the lower the signal-to-noise ratio becomes. Cooper's message gets buried progressively deeper under a heap of sand-kicking diatribes about software engineers, armchair quarterbacking of the designs of others, and thinly veiled plugs for Cooper's particular brand of interaction design consulting.

There are some good ideas in The Inmates, though nothing truly groundbreaking at this point in time. Cooper champions things such as goal oriented design, personae, and primacy of user friendliness. All of which are good things, but none of which are exactly new concepts in 2008. However, the actual useful information comprises maybe 75 pages of the 250ish pages in the book, and is reduced to little more than nuggets of useful information scattered throughout a sea of whining and self aggrandizement.

Cooper's armchair quarterbacking of certain technologies as 'dancing bearware' is particularly annoying. Cooper continually brings up example after example of software and technology that is breaking new ground, acknowledges the fact that the technology even exists as an amazing achievement, and then turns around and lambasts it for not magically coming equipped with the precise amount of polish and feature sets that he wants. The 20/20 hindsight through which Cooper views many technologies belies the fact that Cooper is just as blinkered when it comes to the 'big picture' issues of software engineering as the managers and programmers that he continually needles.

Cooper tries to keep the tone light, and his unique brand of humor kept me reading even as the tone of the book slid gradually into that of a polemic against all things Alan Cooper doesn't like. This book can be downright dangerous if taken as holy writ. Cooper continually takes shots at programmers, and in fact spends an entire chapter reducing them to a set of stereotypes and providing an 'animal handling' guide for the backwards, egotistical, smelly bullies otherwise known as 'programmers'. Taking Cooper's stereotypes to heart is pretty much guaranteed to cause rifts between design and engineering teams, as Cooper goes to great length to explain exactly how far beneath contempt programmers are, how they are not to be trusted, etc. The Inmates espouses a philosophy of design in which non-designer stakeholders are to be marginalized or even totally cut out of the design process. The concepts of business or technical needs influencing design are constantly sidelined, as business and technical concerns are never legitimate, but rather the result of inept managers or lazy programmers. This book should be subtitled 'How to have your design, business, and engineering teams at each others' throats in 3 easy steps'.

Overall I think that the book has some useful information, but much like Cooper does with his case studies, the reader must cherry-pick it to obtain any useful information. Coopers ideas are good (if dated), but they could have been presented in a far more concise fasion, and could have done without the extra 175 pages of masturbatory ego stroking, ranting, and poorly disguised plugs for his consulting firm.

A Must Read Classic, Albeit with Some Dated Ideas
This a classic book that anyone who build computer systems should read. Some of the specific examples are dated, though many caused me to nod in acknowledgment, especially his observations about alarm clocks and TV remotes, Inmates describes goal directed design, the concept of Pesonas, ideas which, whether they make sense for your project are not, are ones that you should be aware of. This book also explains what "polite software" is and emphasizes the market advantages to good interaction design. Even if this book doesn't change the way you work, it will help you think about the relationship between interaction design and programming. Among the interesting points Cooper makes are Customer Driven isn't aways the best model (customer influenced is better), and neither is Engineering Driven; software designers should go beyond customers say they want and help them to understand what they need. There were a few things towards the end of the book that struck me as just wrong. For example Cooper says that most developers don't believe that they are the best people to test their code. Most Agile software developers would challenge that point. Agile developers would also challenge the recurring theme that the engineering team can't make the leap to understanding the customer enough to build good interaction design. He ignores the value of a specializing generalist, which is an important concept in today's projects. It's for these points that I gave this 4 rather than 5 stars. Regardless, this is a book that anyone building software systems should read, if only to understand the concepts underlying interaction design.

No Cognitive Friction Here..
Alan Cooper gives the reader insight into why so many of today's technological products frustrate and confuse users. Yet he goes past this to discuss a methodology for keeping it simple and designing for the user i.e. avoiding cognitive friction. This book has changed the way I will develop products and should be a must read for product managers of application developers. Just learning Mr. Cooper's vocabulary is worth the read. The ideas such as personas, keywords, and designing for an individual push the book way above average. This is an easy read that should be done in your spare time if you want to avoid cognitive friction with your users. It has changed the way I view technology and brought a new awareness to thoughtless technology implementation which often cause failure or misuse. The only reason I gave this book a 4 out of 5 as I feel it could have been reduced a little bit more, certain points I felt like the author was rambling about personal fustrations.