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.