Module 4

For the fourth module, I found the variety of task analysis approaches discussed very interesting. These methods are a way to make the job of documenting task flow much easier. When first approaching a large system or job function, task analysis can be a very daunting subject. Often, people can feel overwhelmed. These analysis methods work because they break everything down into bite sized chunks making them easier to work with. To me, it can be similar to evaluating a large programming project. The scope can sometimes seem impossible to tackle. Using methods like the object-oriented task analysis allows you to break everything down to a level that is understood.

Another method of analysis is through observation. In a programming environment, this is particularly useful. I usually use the cooperative analysis method when observing. To me, this is a lot more personal than the think-aloud approach. I find that talking with the user while they work helps them to relax and be more comfortable. They are more likely to volunteer useful information and small details on the process. This will usually include any exceptions. I find that this approach also helps me when it comes time to check your analysis or do any user testing.

On the topic of prototyping, I use it a little in the programming arena. When a programming change involves creating or modifying a user interface, I will often create a mock screen and walk through things with intended users. This is extremely useful because typically what the user says they want does not match what they really want or need. A prototype will help to reduce programming changes in the long run.

Norman 3 Course Blog Entry

Norman gives so many living examples that have made me stop and think about design when looking at everyday items and places. The example given about the cafeteria in a museum was interesting. I thought about the layouts of restaurants in high traffic areas like in a shopping mall or in an airport. They seem to always have uncomfortable seats and tend to be very small. I never thought about the fact that they may have been designed that way for a reason. The owners would not want people with long layovers at an airport to hang out comfortably in their restaurant after they eat when they are not spending more money. One the other side of this issue I know of a McDonald’s restaurant that has only two registers on the inside and usually only uses one even on busy days. Adding one more register and two more employees at the registers would allow for many more customers to be serviced in a shorter time. When I would walk in and see this situation I would walk right back out. Making the changes would greatly affect the number of potential customers and increase revenue.

Another area that Norman discussed a lot was again the topic of usability versus aesthetics. A saying that comes to mind is one that I have heard from my friends many times when we discuss the use of a new product. We would see many products that have very limited uses. We would say “but it looks cool.” This stresses the fact that the architects often put looks over use. The case study of the Federal Aviation Administration where they allowed architects to design one set of offices and then took input from users to design another helps to prove the point. The architects won awards for their design but the other offices experienced an increase in productivity from their employees. This also shows a breakdown in priorities between what is considered good design of an office environment between the user and the designer.

The discussion of the everyday used products of the bathroom I also found interesting. The different costs and benefits of different faucet designs shows that even for a simple product, design is important. It was interesting to me that the faucets with sensors discussed by Norman show the dating of the book since they are now very commonly found, especially in public restrooms. Norman talks about the fact that the visibility of its function is no longer there for a faucet if a sensor is used. In today’s world, we seem to have overcome this problem. What came to my mind is the use of the sensor toilets and urinals at least in many public men’s restrooms. This is the case where the users do not need to know how to use them since there is nothing they need to do. This actually works out, especially in bars or at sporting events in particular where alcohol is served. Many users of these restroom facilities often did not flush the traditional toilets or urinals anyway. The sensors would help to keep the restrooms much cleaner.

Module 3 Blog Assignment 8-1

In the third module, there are detailed discussions and concepts regarding the whole process of interviewing users and the process of creating good questions. This also includes those for the questionnaire. In our group, we have found that this process can be a difficult one to do correctly. The whole purpose of the questions needs to be kept in mind during the entire process. It is way too easy to get off on a tangent that will really result in no useful usability information. It is also easy to shift to a marketing type survey instead of the intended usability type questions. I do however think that there is some value to those types of questions as well to developers when they are looking to see what direction they need to go in.

The main thing to keep in mind is to make the interview very specific in purpose so that specific questions can be created and asked. This will ensure useful answers. Also, the profiles of the questioned users and the intended users need to cover as broad of a range as possible. This will give insight from all users groups as well as shed light on where improvements need to be made for those particular profiles.

Another observation is on the questionnaire possible answers. It is very important to give answers to chose from that will give a true picture of what is going on. For example, if you asked how many minutes did it took to get the software installed and working. If you only gave the choices of 5 min., 6 min., 7min., or more than 7min. , this may limit the useful results of the question. What if the average installation time was 20 min.? This is where the testing of the questions is important. These types of questions need to give a proper set of answers. Answers should be gathered by talking to users of various levels to give a proper range.

Assignment 7-2 Norman 2 blog post

In Norman’s book, chapter four is loaded with great examples dealing with object constraints. It is amazing the knowledge that we have obtained that many of us take for granted. The simple example of putting together a small Lego police motorcycle toy is loaded with constraints. When reading this section, I thought to myself, I wonder what it would be like to try putting the toy together after having your memory erased. I guess it would be similar to being a baby but with a fully developed body and brain.

The section discussing doors and then the design of switch panels seem to be concepts to me that should be obvious. The whole switch design issue is one that has always annoyed. I have very rarely seen a good light switch design when multiple switches are used. I guess the notion that visual aesthetics are more important than function shows that the designers may be more artistic in thinking than they are in analyzing how a useful design should function. This is probably due to the fact that many people, when buying objects, seem to lean towards the pretty versus the practical. An example is that when selling a house, you are always told that you want it to be visually appealing. A little money spent on landscaping can make thousands of dollars of a difference in the price of a house.

In chapter five, the examples of mental slips bring to mind many of the same past experiences. Many times I remember going into a room while having a conversation with someone and forgetting what I went in to look for. I then would go back only to remember a few minutes later. Another common one for me is forgetting what I was going to talk about. This usually happens when there is a sudden interruption by someone or something that draws your attention for a few seconds. Afterwards, it seems that the harder you try to remember, the more blank your mind becomes. For me, I usually get something unrelated that keeps popping into my head repeatedly when I try to remember.

Another part of chapter five that I find very interesting is the discussion of brain function and activity. The section on the connectionist approach is particularly thought provoking. It is amazing to me that at this day and age that we still know so little about the true functioning of the brain. It is strange to think that it is made up of millions of simple cells whose functions and behaviors are anything but simple.

Assignment 5-1 blog entry

In module two, the topics deal largely with a project’s lifecycle and how HCI can affect the process. In my personal experience at my current company, I have seen many different project outcomes. Typically though my company will wait to the last minute to get the IT department involved. An example would be our opening of a new plant which involved using data from a totally different system from an Italian company. The data was to then be implemented into our system and used to begin production at a new plant in Africa. To start out, the IT department was not even asked for a quick estimate for a project. After the project was already in the works and deals were signed, our department was asked for a budget to get the new plant up and running and to get the Italian system integrated with ours (to be done in an hour.) The budget was then taken by the executives and reduced by a certain percent to make it more to their liking. Since there was no proper planning, of course the project has gone way over budget and they are still struggling to make things work.

Another thing that I have learned over the years is that user resistance to change can be a large hindrance to a project. If you do not have the support of the upper management (the user’s bosses), getting a project implemented can be an uphill battle. One of my counter parts has seen a year’s worth of his work be flushed because he was not able to get the proper buy-in from the users. Unless and even when their bosses feel strongly about and enforces a project, it still may not be successful. An interesting side note to this is that I have noticed that this does seem to vary differently among cultures. In our Mexican plant, even with the language barrier, we have a much easier time putting projects into place. The managers there say it will be done and it is done.

In regards to dealing with other cultures for projects, another interesting issue that we have had deals with how people react with time lines differently. In our dealings with the Italian companies and their employees, it has sometimes been frustrating in that at least in our experiences, they have different views and priorities when it comes to time. Many times we were told that certain things would be done and information would be given and we would sometimes get nothing at all. I know this happens everywhere but in my experiences it has been much more prevalent in our dealings with several Italian companies and their employees.

Still another issue I have seen in different ways is the “Yes it will be done tomorrow!” issue. Tomorrow comes and again it is “Yes it will be done tomorrow!” In projects, people involved need to all be included in the plan and they need to all agree that it is a do-able plan. They then need to not be afraid to give the bad news when things are not going as they should be. If companies could find a way to always hear the truth, they would be much better off in the long run.

Assignment 4-1 Norman 1 Course Blog Entry

Norman’s book begins by giving all sorts of examples of bad designs. He makes note of a complicated phone system that had buttons that no one knew what they were for. It made me start thinking about all the issues I have had in the past with getting items to do as they should. Being in computer science, getting computers to do what I want has often been a challenge. I stopped and thought about the reasons why this happens so often. I think that in the field of technology, many people are intimidated by devices they cannot get to work in the first minute they use it. I also think that many engineers are very intelligent and capable of getting a product to do something but often fail to relate to the end user. They sometimes seem to be on a different plane of thought.

Norman also talks about the topic of natural mapping. Keeping buttons next to what they operate may seem like a simple and obvious idea but it is one that is frequently overlooked. Proper labeling and the use of pictures help keep things simple and more obvious to more people. The marking of the stove burners is one that would always get me. I still usually need to read their labels. Good design can allow people from different language speaking countries and of many levels of intelligence to be able to easily use a product.

Under the topic of memory, I particularly found coin examples interesting since I collected them a lot as a kid. I was always excited when I would get a Susan B. Anthony dollar in my change instead of a quarter. The exercise to pick out the correct Lincoln penny was also tougher than I thought and I looked at thousands of pennies as a kid. It just shows that people take a lot of things for granted. There are many details of design that will be missed and many that will be misunderstood.