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.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment