Designing with the Mind in Mind: Simple Guide to Understanding User Interface Design Rules (Anglais) Broché – 20 mai 2010
|Neuf à partir de||Occasion à partir de|
Il y a une édition plus récente de cet article:
Les clients ayant acheté cet article ont également acheté
Descriptions du produit
Revue de presse
"Take fundamental principles of psychology. Illustrate. Combine with Fundamental Principles of Design. Stir gently until fully blended. Read daily until finished. Caution: The mixture is addictive"--Don Norman, Nielsen Norman group, Author of Design of Future Things.
"This book is a primer to understand the why of the larger human action principles at work―a sort of cognitive science for designers in a hurry. Above all, this is a book of profound insight into the human mind for practical people who want to get something done."-- Stuart Card, Senior Research Fellow and the manager of the User Interface Research group at the Palo Alto Research Centerfrom the foreword
"If you want to know why design rules work, Jeff Johnson provides fresh insight into the psychological rationale for user-interface design rules that pervade discussions in the world of software product and service development."--Aaron Marcus, President, Aaron Marcus and Associates, Inc.
"As anyone who has taken a course in human-computer interaction (HCI) will attest, cognitive science textbooks tend towards the drier end of the literary spectrum. The achievement of this book in making the material easily accessible is therefore nothing short of magnificent. It discusses the relevant scientific findings without any lack of scholarship, but always with an eye to how those findings can be put to practical use."--BCS, British Computer Society Online, November 2010
"Rather than simply presenting another list of rules, it discusses the cognitive psychology research findings which underpin the principles identified previously by the author and others. In other words, this is a book about people, and what we know about them as users of interactive systems."--BCS, The British Computer Society Online
"Anyone who designs or implements software user interfaces will benefit greatly from this book. Whether you create desktop software, websites, or mobile apps, this book will improve the quality of your work. Johnson makes the psychology and physiology understandable and seamlessly combines it with software engineering… Designing with the Mind in Mind is informative, fascinating, easy to read, and, most importantly, highly practical."-- ACM SIGSOFT Software Engineering
Présentation de l'éditeur
Early user interface (UI) practitioners were trained in cognitive psychology, from which UI design rules were based. But as the field evolves, designers enter the field from many disciplines. Practitioners today have enough experience in UI design that they have been exposed to design rules, but it is essential that they understand the psychology behind the rules in order to effectively apply them. In Designing with the Mind in Mind, Jeff Johnson, author of the best selling GUI Bloopers, provides designers with just enough background in perceptual and cognitive psychology that UI design guidelines make intuitive sense rather than being just a list of rules to follow.
* The first practical, all-in-one source for practitioners on user interface design rules and why, when and how to apply them.
* Provides just enough background into the reasoning behind interface design rules that practitioners can make informed decisions in every project.
* Gives practitioners the insight they need to make educated design decisions when confronted with tradeoffs, including competing design rules, time constrictions, or limited resources.
Aucun appareil Kindle n'est requis. Téléchargez l'une des applis Kindle gratuites et commencez à lire les livres Kindle sur votre smartphone, tablette ou ordinateur.
Pour obtenir l'appli gratuite, saisissez votre numéro de téléphone mobile.
Détails sur le produit
Commentaires en ligne
Commentaires client les plus utiles sur Amazon.com (beta)
Jeff Johnson's earlier books are more comprehensive on the design side (GUI Bloopers 2.0; Web Bloopers), but the present volume offers the reader deeper insight into the implications of a more modest sub-set of design principles. He uses bite-sized chapters and clear language to provide the psychological and biological background, often including fascinating research results. The examples he uses to illustrate his points are both compelling and accessible. (And politically correct: both Apple and Microsoft get some thumbs-down ratings.) The sections where he translates psychological observations into "computer jargon" are useful for engineers.
The droll headings and examples keep things lively. "Reading Is Unnatural;" "Our Attention Is Limited; Our Memory Is Imperfect": this sums up how I feel sometimes. I learned that the gap between what a user wants and what a user gets is called the "gulf of execution." And the usability test participant's comment, "I'm in a hurry, so I'll do it the long way." is priceless, as is the explanation: "Avoiding thought when using computers is important." (The participant suspected there might be a faster way to perform a task, but didn't want to take the time and effort to figure it out.)
Readers who implement user interfaces but don't have a background in cognitive psychology, or who have that background but might not know how to apply it to the world of user interface design, will get a lot out of this volume. Those who exist with one foot in each world will also enjoy it.
Topics covered include:
How our visual perceptions are biased by experience, the current context, and user's intentions/goals;
How our vision is optimized to see structure; Gestalt principles of proximity, continuity, closure, symmetry, figure/ground separation and then how they are combined;
How structure enhances people's ability to scan long numbers; how visual hierarchy enables readers to focus on the most relevant information;
A discussion of psychological theory that indicates than we're "wired for language, but not for reading" and the design implications of these findings;
Limitations of our color vision and implications for how color is presented in user interfaces; the fact that user's peripheral vision is poor and common methods used to makes messages more visible (e.g. pop-ups, sound, and flash/motion);
Design implications regarding our limited short term and long term memory; how recognition and learning from experience for readers is typically easy while problem solving and recall is hard;
And, a discussion of time requirements for systems designers to consider.
Written in an easy-to-understand narrative, lecture-format with dozens of illustrations in each chapter, readers will find this book to be a delightful and welcome primer detailing the fundamental psychological principles behind effective design rules.
Highly recommended for college and university library collections as well as graphic designers and psychologists interested in human/machine interface design.
R. Neil Scott
Middle Tennessee State University
Whenever one specifies a guideline or rule of thumb, or announces a policy that is about to be adopted and enforced, it is wise to explain the reasoning behind it, even if one has the power to enforce its adoption. Detailing the reasons, in tandem with examples of good and bad practice, makes the rule more memorable, and more likely to be reconstructed by someone trying to recall what the rule is. The reasoning, if valid, will also undercut the natural tendency to ignore or actively subvert rules that appear arbitrary, with no better basis than the whim of some over-controlling personality.
An incredible thing about "Designing with the mind in mind" is that most of its guidelines are ultimately easy to remember and, equally important, "easy to swallow", that is, made as palatable as possible by the reasons and examples provided. Because the basis for each guideline is so well explained, the guidelines all make intuitive sense.
The reasons provided for the design guidelines are primarily drawn from cognitive psychology, and secondarily from neuroscience. Therefore, the title appropriately reads "with the mind in mind" and not "with the brain in mind". In a compact book (around 200 pages) that can be read in two sessions, it would have been a mistake to try to ground all the guidelines in neural constraints. Far better is the strategy followed by Johnson, who roots the guidelines in "hard" cognitive psychological constraints that, in turn, one could explain in terms of brain circuitry -- but only if given a budget of another 200 pages. In a few cases, Johnson does sketch neural explanations, in order to exemplify how each mental constraint could be related to a handful of pertinent neural constraints. But, just as one of his interface design principles is to avoid forcing the user to learn geek-speak that is irrelevant to the user's goals, Johnson makes no attempt to give more than short glimpses of the arcane objects and vocabularies found in modern neuroscience.
Another welcome aspect of the book is the way that each chapter builds on the main themes of earlier chapters. For that reason, but also for the overarching perspectives they offer, the last two chapters are the best. One explains how design can maximize the ease with which users explore and learn to deploy the full range of nifty functions made possible by a software-intensive, multi-function tool. The other explains how the time scales of tool operations (such as feedback that a mouse click has been received) must mesh with the time scales of the mind's operations. Poor temporal meshing between these two contributors to the person-machine "conversation" (Johnson's apt term) leads to many gratuitous frustrations and annoyances, which will drive users to abandon the offending product X in favor of a product Y that meshes better with the time scales of mental operations. This will happen even if X outperforms Y on many other, "objective", benchmarks.
Many of the topics treated in the book have been treated elsewhere, notably in prior design books by authors familiar with cognitive psychology, but the approach taken here is remarkable for its elegance and conciseness. Anyone in the business of designing a software product that is complex enough to have an associated "learning curve" will find here many good ideas for minimizing the curve's steepness. The book's own learning curve is very gentle, despite the wealth of ideas.
Again, this can't be done without *any* design consideration, and it shouldn't be done with only *intuitive* design schemes.
Enter Designing with the Mind in Mind: Simple Guide to Understanding User Interface Design Rules! This book presents a set of tools for designers--a set of rules based on psychological studies. Like any other set of tools or rules, you might not agree 100% with all of the rules, but using a set of rules as your starting point always leads to a higher quality end result.
Whether your role is in HFE or you are the developer writing the code, this book is a great place to begin--before you start your project.
If you've ever wondered why some applications just feel easier and more enjoyable to use than others and chalked it up to some UI guru's intuitive grasp of "eye appeal" or "artistic flair", Johnson's book may surprise and reassure you that there is in fact a quantifiable, cognitive basis behind many aspects of why one particular design "just looks and feels better" than another.
Don't expect a heavy dose of psychology here either: The author presents just enough background to keep things interesting and satisfy those who happily never outgrew their "But why?" phase. This is a cleanly written and practical book whose well-chosen examples cover a wide range of applications and system interfaces illustrating just how broadly these ideas can be applied.
If you've never read a book on UI design the concepts covered here are fairly standard to the genre: Gestalt principles of grouping visual information by proximity, similarity, closure, and symmetry are presented with straightforward examples. The chapter on reading text (so prevalent in software interfaces yet quite unnatural to our brains ) and the ramifications of communicating ideas with text is fascinating and alone worth reading the book for. If you've ever created or encountered a "dialog from hell" stuffed to the gills with ill-placed and over-described controls, you'll find this material particularly interesting.
I'd not read previously in a design book the impact our short and longer term memory has (or should have) on the amount, complexity, and sequencing of information presented to users. While Johnson's book is primarily concerned with visual interfaces, memory also strongly influences our perception of sound and music and there are ramifications here for designs incorporating these elements. A terrific book on the subject for those with an interest in music is "Music and Memory" by Bob Snyder (MIT Press).
Johnson rounds out the book with well-illustrated chapters on color perception, theories of learning, our capacity for dealing with complexity and how that influences our experience following various interface narratives. It sounds much heavier than it reads. The author really strikes an effective and readable tone that respects the reader's intelligence while avoiding the use of gratuitous jargon meant to show off his authority on the subject.
At "K&R length", "Designing with the Mind in Mind" is the kind of book I think busy developers will find time for and keep close at hand for reference and inspiration. Even if you're not involved in front-end work for a commercial product, I've found throughout my 20+ plus years in the field there are plenty of opportunities to create UIs for tools, in-house utilities, one-off conversion programs, intranet support pages - you name it. We all use them and we'll use them more often and more effectively if they're designed well.
"Designing with the Mind in Mind" may just leave you looking at the software world (and the non-software world) with a fresh pair of eyes. A Warning though: the folks over in the client group may not be so thrilled when you start complaining about the "counter-Gestalt" flaws in their GUI!