Designing today; A compare and contrast of Don Norman’s Principles of Design and where they stand today


Joey Sisti
IST 600
2/5/18
Assignment #2 Design Principles

“Designing today; A compare and contrast of Don Norman’s Principles of Design and where they stand today”

            User Experience Design is one of the fastest growing information technology fields around the world. The increased demand for UX designers has resulted from companies placing an increased emphasis on user feedback, user interface design and a variety of other design features. However, I believe there is a misconception about the most important rules and principles user experience professionals must follow. The most important design principles that user experience professionals should follow are those that have existed before design had a role in the digital landscape. These design principles derive from Don Norman’s famous book, The design of everyday things, which examines the relationship between an object and user. The concept of User-center design along with its key principles such as affordance, feedback, mapping and visibility coupled with ergonomics should still play a role in designing today. Despite being created thirty something years ago, these principles should still be the foundation of design because they are applicable to digital interfaces, are user focused and apply to lean processes.  
            “User-center design derives from ergonomics which entails comfort design, functional, systems or processes to take proper account of the interaction between them and the people who use them.” (Thesaurus Ergonomics, 1) Essentially, ergonomics examines the way a user interacts with a given system and how satisfied they are at the end of their experience. Ergonomics comes in many different forms. It can be physical, cognitive or organizational. Physical ergonomics looks at the human interaction and the physical activity users have with the product or service. It examines things such as eye contact, physical comfort, etc aiming to ensure the user has an enjoyable experience with the product. Cognitive ergonomics focuses primarily on the mental processes during the user’s journey. (Ergonomics in safety, 1) This relates to things such as reasoning, journey tracking and other cognitive measures the user experiences they have while using the product. Finally, organization ergonomics looks at the virtual organizations, teamwork, work design and communication. Overall these three principles provide support and work in cohesion with user-center design principles.
            The first design principle that I believe every user-experience designer should use is user-centered design. User-center design involves simplifying the structure of tasks, making things visible, mappings information correctly, designing for error and affordances in products. It also places a higher emphasis on user satisfaction in regards to the product’s safety and performance rather than its aesthetic pleasure. User-centered design focuses on developing the understanding of a user’s needs through a variety of measures. “UX teams will use a mixture of investigative and generative methods and tools” (Interaction Design.org, 1) The investigative measures come in the form of focus groups or interviews that allow for a design to better understand the needs, demographics and other key information about their users. “The generative models focus primarily on brainstorming ideas for products or services that could be best used by the intended audience.” (Norman, 20) Knowing the user or audience for a product, good or service is important because these are the individuals who will be using it most. Should the product, good or service fall short in the eyes of user, then the project should be deemed a failure. Though I don’t consider the following “design” principles, they are still an aid to the importance of user-centered design. A/B testing and user personas help the design team better understand the people for whom they are creating products for.
            The first user-centered design principle that I believe is important is visibility. Visibility in design entails everything that the user of a product or service can see. According to Norman, this could be anything pertaining to the system, actions, results of actions and the impending feedback. (Norman, p. 42) Having proper visibility in a design will let the user see their own path through the use of a product or service. Good visibility in design helps eliminate doubts or questions the user might have as they go through their experience. Seeing results and feedback also confirm to the user that they are either doing what they want to be doing or not. Demonstrating the results of actions and feedback for the user helps prevent confusion. From personal experience I feel a lot more comfort when websites have a loading bar on them. There have been times where I sat on a website waiting for it to load only to have it return a search error. A loading bar would have given me an ease of mind when it came to the load time of the web page. Although it still would not have worked, I would have been more inclined to stay on the website for longer.
            Visibility can also allow for more natural interaction between the user and their system. Natural design is design that requires no conscious thought. Often unsuccessful websites, products, applications, etc have bad visibility when certain features of their user experience are hidden. These hidden experiences are seldom found by users and as a result take away from their experience when visiting. The less confused a user is, the more likely they are to have a positive experience with a product or service. Visibility is an integrate user-centered design principle the design teams should implement to give their user a better experience.
            Another user-center design principle that is important in design is affordance. “Affordance is the design aspect of an object which suggests how the object should be used; a visual clue to its function and use.” (Interaction-design.org, 1) Essentially, affordance of a product gives the user an idea of what it can and cannot do. It also integrates second-nature interaction features as well. Affordance will allow a user to know what to do with the product as soon as they see it. “Balls are for throwing or bounce. Knobs are for turning, slots are for inserting things into.” (Norman, p.9) These actions are performed by the user without a picture, label or additional instructions. It’s a combination of both actual and perceived properties. Norman gives the example of a ball in his book The Design of Everyday Things. He says that the ball is round and bouncy which demonstrates its actual physical properties to the user. Meanwhile, the ball also has perceived properties such as the suggestion to throw or bounce the object based on its physical properties. (Norman, p. 20) The affordance of the ball is the relationship between the actual object and the actions a user of the object can take. In regards to design, I think it is important to understand the affordance of a product or service because designers want to make it clear to a user what they are able to do. This concept is similar to visibility because a user should be able to tell what a product can afford to do based on its physical and perceived properties. The immediate understanding and specific scope of affordances a product has will always reign supreme in the eyes of consumer ease no matter how it looks aesthetically. 
            A third user-center design term that I believe is imperative in design today is feedback. Feedback shows the user exactly what action is being done and what has been accomplished by doing so. Feedback can exist in the form of audio, visual, interaction and more. I mentioned earlier in the paper about the website loading example and how real time feedback would have left me less frustrated during my experience. Loading bars are a good way to show feedback because they can update the user exactly where they are during their digital journey. With so much information being transpired in real time I believe it is imperative to show the user the result of their action every step of the way. Feedback can also be used throughout every stage of an application. It can be used to help eliminate errors users make on products such as e-commerce apps. A user could accidentally add products to their shopping cart. If a user didn’t want the product they just added, they could easily remove it or not confirm adding it based on feedback from the app. Immediate feedback on applications can also put the users mind at ease in case these errors occur. “Feedback has to be planned. All actions need to be confirmed, but in a manner that is unobtrusive” (Norman, 35) Norman goes on to discuss the importance of major emergencies and how the signals from them have to clear and effective. Obviously giving effective messages in times of error is imperative because it puts the user’s mind at more ease.
            The fourth and final principle I believe still plays a role in design today is mapping. According to Norman, “mapping is a technical term, borrowed from mathematics, meaning the relationship between the elements of two sets of things.” (Norman, 20) Mapping uses spatial clues to help show the user what they should be doing. We know that by turning a faucet one direction it will give us one temperature while turning it in the other direction will yield the opposite temperature. Successful mapping will also help the user avoid careless errors during their experience. Mapping considers pairing things together that make sense. Through a group of principles that derive from Gestalt psychology these related controls are grouped together and are close to items which they control. Mapping is still very important in design today given how confusing some technologies can be for new users. Proper mapping can help ease a new user into an experience whether it be a digital experience or a newly launched product. Cohesion between certain controls and their proximity to actions remains very important in design today.
             A practical example of how Don Norman’s principles were not implemented in a design is the Hawaii missile crisis that occurred last month. At first many thought that the improper action was caused by negligence on the part of the worker. However, after photos were released regarding the mix up it became clear that this was a failure of design, not the user. Below is a photo of the board the worker was using. As you can see in the image the alarm system for both testing and an actual emergency are on the same drop-down menu. Based on Norman’s principles this violates many design rules. The first being mapping. In this instance mapping is used improperly because there is no use of Gestalt principles in way the menu is laid out. The options for both testing and actual emergency are near one another. This makes no sense and caused a lot of confusion for the user. A second principle that is violated here is feedback. The user clicked the wrong button and had no idea they had done so until minutes later. With no immediate feedback to the user there was no confirmation or disproval of the action that took place. Overall this design is not user friendly and as a result cost a worker their job. If I were to redesign this page I would start with the mapping of features. Every task exists in a single drop-down menu which can cause much confusion for a user. If there were three separate categories which separated the design into “actual emergency”, “test” and “false alarm” then the user would have an easier time understanding which one to pick given the circumstance. This confirms Norman’s principle of mapping by grouping similar things together. The second way I would fix this design is by providing feedback to the user based on the actions they perform. There could still be room for error even if the options are all properly spaced. However, immediate feedback will let the user know exactly what action they have just performed. In this specific example the person who accidentally hit the button would have known right away and could have sent the false alarm message after sending the initial wrong message. Feedback would have caused a lot more ease in the minds of the people receiving the message and would have also properly saved the person’s job.
To the left is an example I made to better show how the Hawaii missile crisis could have been avoided.  This example follows several Gestalt principles by group together similar objects. I decided to pair all the Pacom alerts together and all the amber alerts together so the user can better understand which button gives the alert. A lot of the confusion on the original design occurred because everything option was on the same drop down menu. The labels were also all named differently. I thought it was strange that certain systems had their tests labeled test while others were labeled drill. Based on Gestalt principles it would make more sense to give the same labels across the different systems and have the actions paired with their impending action of a group (Pacom/Amber Alert).

          An example of good design that follows Norman’s principles is the Starbucks app. The Application groups similar things together and provides good mapping for its users. Each different category is based a certain type of food that the company offers. This helps the user better understand where they can find certain things on the application. The app also uses a favorite menus feature which helps remembers users’ previous orders. These favorite meal suggestions start at the beginning of the app when the user first opens it so it can give them a more user friendly journey on the application. This way users don’t have to go searching for their favorite food over and over. The application also has feedback for the user every step of the way. Every time the user selects an item it asks them to confirm whether or not they want to add the item to the bag. This is an example of good feedback because it tells the user what they’re adding to the bag as soon as they perform the action. This accounts for any potential error on the side of the user. The app also uses visibility very well. All of the options the user could select are on the first page of the menu. Having all the options on the
front page of the app helps the user stay on track for their entire experience. Sometimes when options, especially on food apps, are hidden within certain menus users can become confused if they can’t find what they want. Lastly, the app has good affordance because it allows the user to order food and order food only. There’s no confusion as to what the application can afford to do. Overall the app is very good in the way it uses the design principles Norman created thirty years ago.
The biggest takeaway from doing research on design principles is that the most important and consistent ones are independent from actual graphic design content. Prior to taking this course, IST 523 (Web Design) and IST 649 (HCI) I thought that a lot of human
computer interaction, ux design and ui design focused primarily on the aesthetic pleasure of goods and services. However, after reading the works of Don Norman and other design experts who have been working with HCI and design principles before the inception of digital interfaces its clear that the ergonomic and user-centered design principles are the most meaningful when it comes to product design. Though the surfaces for which products are being designed for are changing, the principles that support their effectiveness should still be seen as the most effective measures for creating successful experiences. The perfect combination of principles will allow for better user experience, comfort and support throughout their use of the product or service. Showing a user exactly what they can do on an app, website, good, or service is best done through effected user-centered design principles, namely, affordance, visibility, feedback and mapping.

Comments